DigitalMANIPULATIVE

Nagging

What it is

Repeating a request the user has already declined — turn on notifications, upgrade now, install the app, rate us, switch browsers — at intervals and without a “never” option, until compliance becomes cheaper than refusal.

How it works

A single prompt is a question. A prompt that returns after every refusal is a cost imposed on refusal. Gray and colleagues defined nagging in 2018 as a redirection of expected functionality that persists over one or more interactions; the EDPB's deceptive-design guidelines call the same thing “continuous prompting” and place it under overloading. The mechanism is attrition. Each appearance interrupts a task, and the interruption cost is paid whether the user says yes or no; but “yes” ends the sequence and “no” only defers it, so over enough repetitions the rational move is to give in. The options offered make the asymmetry explicit — “Not now” and “Remind me later”, never “Never” — because the design needs the loop to stay open. Nagging also erodes the meaning of the earlier refusal: after the fifth prompt people doubt whether they really declined, and the platform can record the eventual click as consent. Microsoft's “Get Windows 10” campaign in 2015-2016, which re-prompted users for months and at one point treated closing the window as acceptance, is the reference case; social apps asking again and again for notification access, and browsers pushing users to switch back, are its everyday form.

Real-world examples

  • Microsoft's “Get Windows 10” prompts (2015-2016): a system-tray app that re-prompted users to upgrade for months, escalated to scheduled installs, and at one point interpreted closing the dialog as consent; independent tools such as GWX Control Panel appeared solely to stop it.
  • Instagram's repeated “Turn on notifications” interstitial with “Not now” as the only alternative, cited by Gray et al. (2018) as an example of nagging.
  • Operating-system and browser prompts to switch default browser, sign in to a cloud account, or “finish setting up”, returning on a schedule after each dismissal.
  • In-app rating requests and “upgrade to premium” overlays that appear at fixed intervals or on every launch; Apple's App Store guidelines now require the system rating prompt, which is limited to three appearances a year, for that reason.

Ethical guidelines

  • Offer “No” and “Never” with the same weight as “Yes”, and honor them; a refusal means the prompt does not return unless the user goes looking for it.
  • If a request must recur (a security update, a legal notice), state why and cap the frequency; anything promotional appears once.
  • A click extracted by repetition is not consent and should not be logged as such; the EDPB treats continuous prompting as a pattern that undermines freely given consent.
  • Measure the cost: track how many prompts precede each “yes” and treat a high number as a failure of the request, not a success of the design.

How to defend against it

  • Look for the smallest option first — “Don't ask again”, “Never”, “Turn off suggestions” — and take it; if it is absent, note that the vendor has designed the loop to stay open and adjust your trust accordingly.
  • Remove the channel rather than answering the prompt: disable the app's notifications at the operating-system level, or set the browser default and the cloud-account setting once so the prompt has nothing to ask.
  • Count the nags and say the count aloud: “this is the fourth time”. Naming the tactic is the Persuasion Knowledge Model defense, and the count converts irritation into evidence.
  • Do not let the fifth prompt overturn the first decision: decide once, in writing if it matters, and treat any later click as a slip to be reversed in settings, not a change of mind.
  • Report continuous prompting on consent or privacy choices to your data-protection authority (EU/UK) and under DSA Article 25; in the US, note it in FTC complaints as a “nagging” design element the 2022 staff report names.

From the Defense Playbook

Every playbook entry states how strong its evidence is and when not to use it. Browse the full playbook.

References

  1. Gray, C. M., Kou, Y., Battles, B., Hoggatt, J., & Toombs, A. L. (2018). The Dark (Patterns) Side of UX Design. Proceedings of the 2018 CHI Conference on Human Factors in Computing Systems · link
    The definition of nagging as a dark-pattern strategy and the Instagram notification-prompt example.
  2. European Data Protection Board (2023). Guidelines 03/2022 on deceptive design patterns in social media platform interfaces: how to recognise and avoid them (Version 2.0). EDPB, adopted February 2023
    The “continuous prompting” pattern under the overloading category, and its effect on freely given consent.
  3. Federal Trade Commission (2022). Bringing Dark Patterns to Light. FTC Staff Report, September 2022 · link
    The listing of nagging among design elements that induce false beliefs or impede free choice.
Last reviewed
Suggest a correction

Detect Nagging in any text

Paste any message, email, or article into our free Manipulation Detector to see if Nagging or other techniques are being used on you.

Related Articles