The Banner That Asks Twice: Reprompt Rules After a Cookie Clear
A visitor clears their cookies, visits your site, and the banner asks again. That is the system working. The consent record lived in a cookie, the cookie is gone, and the site has no choice on file, so it asks. The problem is not the re-ask. The problem is the two sites on either side of it: the one that asks again on every visit, and the one that never asks again at all.
The every-visit banner has a cause, and it is usually a short cookie expiry. Some consent platforms set the consent cookie to expire in days or weeks, and when it expires the visitor gets asked again. A short expiry is not a bug in itself, but a consent cookie that expires every 30 days means a regular visitor gets asked twelve times a year, and by the third time they click accept just to make the banner go away. That is not consent. That is fatigue, and a regulator reading the log will see an accept rate that climbs with the number of asks, which is evidence of the design rather than of choice.
The never-asks-again problem is worse
The other side is worse. A site that never re-asks after a cookie clear is usually a site that stored the choice somewhere the clear did not reach, or a site that defaults to accept when no record exists. The first case is a fingerprint by another name: the site recognized the visitor without a cookie and restored a choice the visitor believed was deleted. The second case is a site that treats the absence of a record as consent, which is the exact inversion of the rule. No record means no consent, and the banner has to appear.
The correct behavior is boring. The consent cookie lasts as long as the policy says it lasts, usually six to twelve months, and when it expires or is cleared, the banner appears once, the visitor chooses, and the record is written again. The banner copy should not change between asks, because a visitor who rejected last time and gets a differently worded banner this time is being tested, not asked.
What to check this week
Clear your cookies, visit the site, and count the asks. One ask is correct. Zero asks is a failure. Then check the consent cookie expiry in the browser: if it is under 30 days, the team should be able to explain why. Then check what the site does with a rejection after a clear: the rejection has to be written to a fresh record, with a fresh timestamp, and the tags have to respect it from the first page load, not from the second.
Reprompting is where the consent system meets the visitor most often, and it is where the system's honesty is most visible. A banner that asks once, remembers the answer, and asks again only when the record is genuinely gone is a system that works. Anything else is a banner that trains visitors to click accept, or a site that never really asked at all.
Keep reading: Consent Records: What to Keep When a Visitor Says No, The Banner After a Redesign: Why a New Layout Means a New Consent Decision, and The Thank-You Page: Post-Purchase Tracking and the Consent It Forgot cover the nearby cases in this series.
Frequently asked questions
Why does the banner ask again after I clear cookies?
Because the consent record lived in a cookie, and the cookie is gone. With no choice on file, the site has to ask again. That is the system working.
How long should a consent cookie last?
Usually six to twelve months, as stated in the policy. A cookie that expires in under 30 days means regular visitors get asked constantly, and that trains them to click accept just to dismiss the banner.
What if the banner never asks again after I clear cookies?
That is a failure. Either the site recognized you without a cookie and restored a choice you believed was deleted, or it treats the absence of a record as consent. No record means no consent.
Should the banner copy change between asks?
No. A visitor who rejected last time and gets differently worded banner this time is being tested, not asked. The copy should stay the same.