How Often Should a Consent Banner Ask Again?
Re prompting too often trains visitors to click anything. Asking never leaves consent stale. Setting a sensible re prompt policy by trigger rather than by habit.
Every consent banner has a re prompt policy, whether anyone chose one or not. The defaults of the platform, plus a few campaign edits, decide when a visitor who already chose is asked again, and the combined result is usually either nagging or never.
Good re prompt policy is trigger based. This guide covers the events that justify asking again, the intervals that do not, and how to treat visitors whose stored consent can no longer be read.
Ask again when something material changed
New categories, new purposes, a materially new set of tools, or a change in who data is shared with are legitimate triggers: the old choice did not cover the new reality, and proceeding as if it did is worse than asking.
Cosmetic banner changes are not triggers. A redesign that re prompts the entire audience teaches visitors that the banner is weather, not a decision, and click through honesty drops for the changes that matter.
Use age as a backstop, not the main rule
Many organisations set a renewal age, commonly six to twelve months, after which consent is refreshed. As a backstop against indefinite staleness that is reasonable. As the only rule it both under asks after big changes and over asks in quiet periods.
Where law or guidance in your markets sets expectations, those govern. Where it does not, write the chosen age and the triggers into the consent documentation so the policy is a decision someone can defend, not a platform default nobody remembers setting.
Handle unreadable consent without a pile up
Stored consent goes unreadable when visitors clear storage, switch devices, or when the consent platform changes its format. Each case looks like a new visitor, and the banner correctly asks. The pile up happens when the same visitor is asked every session because storage is being blocked or wiped by the site itself.
If support or analytics suggest repeat prompting, investigate storage first: overly short consent cookie lifetimes set by the site are a self inflicted cause that looks, in the data, exactly like visitor behaviour.
Measure dismissal quality, not just rate
A re prompt that works produces considered choices: a similar accept and reject mix to first prompts, and low instant dismissal. A re prompt that produces ninety percent fastest possible clicks is producing noise recorded as consent, which is a legal asset of doubtful value.
Review re prompt performance after any trigger change. Rising instant accept rates after a policy tightening usually mean the audience has been trained by over asking, and the remedy is fewer, more meaningful prompts, not clearer buttons.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: Cookiebot Alternatives Compared Side by Side, Checking Consent Banners After Theme Updates, and Consent Rollout Plans for Multi Region Stores.
Frequently asked questions
When should a banner legitimately ask again?
When something material changed: new categories, new purposes, new recipients of data, or when consent reaches the renewal age the organisation set. Cosmetic redesigns do not justify re prompting everyone.
What renewal age is typical?
Six to twelve months is common as a backstop where no specific rule governs. It should sit alongside change based triggers, and the choice should be documented rather than inherited from platform defaults.
Why do some visitors get asked every visit?
Usually because their stored consent is not surviving: cleared storage, a new device, or the sites own short consent cookie lifetime. Repeat prompting at scale is often a storage bug, not visitor behaviour.
Can asking too often harm consent quality?
Yes. Over asked visitors click the fastest option to dismiss, which produces records that look like consent but reflect dismissal. Fewer, well timed prompts produce choices with more evidential weight.