Journal · Cookie banners
How to raise cookie consent accept rates without dark patterns
You raise cookie consent accept rates with clarity, not pressure. Write the first layer in plain language, give accept and reject equal weight, offer categories instead of all or nothing, and make the banner render instantly. Then measure choices against banners shown, before and after, region by region, so the improvement is a number rather than a feeling.
What counts as a dark pattern in a cookie banner?
The phrase dark pattern gets thrown around loosely, but in a cookie banner the line is clearer than most vendors pretend. European regulators keep flagging the same handful of designs: a reject that hides behind a settings screen while accept sits one click away, categories that arrive pre ticked, guilt copy on the decline button, contrast so low the refusal is barely readable, and banners that come back on every page after a no. What these share is intent. They manufacture consent rather than ask for it, and manufactured consent is not valid consent under the GDPR. The accept rate it produces is borrowed, not earned, and it can be voided in an audit.
None of that outlaws design. You may make accept the filled button and reject the outlined one, as long as both sit in the same layer at the same size and both stay readable. You may write copy that gives the visitor a reason to say yes. You may show your logo, choose your colours and pick your moment. Persuasion is legal; concealment is not. Every step below lives on the right side of that line.
Persuasion is legal. Concealment is not.
What crosses the line
- Reject hidden behind settings
- Pre ticked categories
- Guilt copy on the decline
- Repeat prompts after a refusal
Consent a regulator can void.
What lifts the rate
- Plain language first layer
- Accept and reject at equal weight
- Granular categories
- Renders with the first paint
Consent that holds.
How do you calculate a cookie consent accept rate?
The accept rate is accepts divided by banners shown, not by all sessions. A returning visitor whose choice is still stored never sees the banner, so dividing by every session drags the rate down, and it then moves whenever your share of returning traffic moves. That is a reporting artefact, not a design result.
Count four outcomes, not two:
- Accept all: every category granted.
- Partial: some categories granted, usually analytics without advertising. Report it on its own line, because it keeps measurement that a flat reject loses.
- Reject all: only strictly necessary storage.
- No choice: the visitor reads on or leaves without clicking. Where the law requires opt in, that visitor stays denied, because nothing runs until someone says yes.
Then split every bucket by region. An opt in region and an opt out region are different experiments: in the EU a visitor who never clicks stays denied, while in the US the default can usually run until the visitor opts out. A blended global rate averages the two and describes neither.
How to raise the rate, step by step
Measure your current accept rate first
Before touching the design, establish the baseline with the four outcomes above. Your CMP dashboard should report consent choices; if yours does not, count consent update events in Tag Manager preview mode. The
gcsparameter on your tags’ requests shows granted or denied, but it cannot tell a reject from no choice, since both read as denied. Note the rate over at least a week, split by device and region, so the change you make has a number to beat.Rewrite the first layer in plain language
Two sentences. What you collect, and what the visitor gets: “We use cookies to measure traffic and improve your experience. You choose what to allow.” People agree more readily when a purpose comes with a reason, so say why. If a sentence reads like a privacy notice, rewrite it.
Give accept and reject equal weight
Same layer, same size, both one click. A filled accept next to an outlined reject is fine while both stay clearly readable. Burying reject behind a settings screen is the classic dark pattern, and the design regulators keep flagging. We made the full case in the one click reject post.
Offer categories, not all or nothing
Separate analytics from advertising. A visitor who refuses ad tracking will often still allow measurement when given the choice, and a partial accept preserves more of your data than a flat reject. Label each category by what it does for the visitor, not by its legal name.
Make the banner render instantly
A banner that lags behind the page gets decided by impatience, not preference: visitors dismiss whatever interrupts them mid read. Serve it from the edge, keep the script small, and let it appear with the first paint, before anyone has started scrolling.
Measure again against the same baseline
Give the change at least two weeks on the same traffic mix, then compare with step 1 by region and device. Judge the redesign on the accept rate and your reported conversions together, not on gut feel. If the rate moved but the data did not, the wiring is the problem, not the banner.
The maths that makes dark patterns pointless
There is a quieter reason to skip the tricks, and it is arithmetic rather than ethics. A rejection does not have to be a blank. With Consent Mode v2 wired correctly, a declined visit still sends a cookieless ping, stripped of identifiers. When your property meets Google’s eligibility thresholds, Google can model part of the conversions the missing cookies would have carried. We walk through the four signals in the plain English guide to Consent Mode v2 and the full order of work in the conversions and consent post.
Put the two levers side by side. Some share of your sessions sits behind the banner, and its size varies with region, audience and banner design; your consent tool’s accept rate tells you yours. Design decides part of that: a clearer first layer turns silent dismissals into real choices, in both directions. Wiring decides what Google receives from the rest, because a rejection that still sends a stripped ping gives modelling something to work with. A dark pattern squeezes out accepts that regulators can void and visitors resent. Correct wiring works on the same traffic with nothing to void and nobody deceived.
That is the trade in plain terms. The manipulated banner buys consents that evaporate the day someone looks closely; the honest banner plus correct wiring buys signal that holds. Velo ships the second path as one layer: the banner, the regional defaults and the Consent Mode v2 signal are configured together. A reject reaches Google’s tags as a clear denied signal instead of leaving a hole in your reports.
Common questions
How do I increase cookie consent accept rates without dark patterns?
Rewrite the first layer in plain language with a reason to say yes, put accept and reject in the same layer at the same size, offer granular categories instead of all or nothing, and make the banner render with the first paint. Measure your accept rate before and after the change so the improvement is a number, not a feeling.
What counts as a dark pattern in a cookie banner?
The designs European regulators keep flagging: a reject option hidden behind a settings screen while accept sits one click away, categories that arrive pre ticked, guilt copy on the decline button, contrast so low the reject is barely readable, and banners that return on every page after a refusal. Consent obtained this way is not valid consent under the GDPR.
Is a filled accept button next to an outlined reject button a dark pattern?
Generally no. Visual hierarchy is allowed as long as both buttons sit in the same layer, at the same size, and both stay clearly readable. The line is concealment: hiding, shrinking or delaying one of the two choices. Persuasion is legal; making the refusal harder than the acceptance is not.
How do you calculate a cookie consent accept rate?
Divide accepts by the number of times the banner was shown, not by all sessions, since returning visitors with a stored choice never see it. Track accept all, partial, reject all and no choice as separate outcomes, and split each by region, because opt in and opt out regions behave differently.
What is a good cookie consent accept rate?
There is no universal benchmark worth trusting: the rate swings with region, device mix, audience and banner design. The number that matters is your own baseline, measured for at least a week before a change and compared on the same traffic mix after it. With Consent Mode v2 wired, Google can also model some conversions from rejected visits when your property meets its eligibility thresholds, so the accept rate alone does not show everything your measurement keeps.
Keep reading
How to add a cookie banner to WordPress without a plugin
Most guides say to paste the script into header.php. A child theme hook keeps it through updates and prints it ahead of the Google tag your plugins queue.
How to add a cookie banner to a Webflow site
Your banner governs the container. Webflow's Apps and Integrations tab loads Google Analytics and the Meta pixel outside it, and clearing that tab is the step most setups miss.
Start with a scan
See what your homepage already loads before you install anything. The free scanner reads the page and your public Tag Manager container.
A first pass, not a verdict. Four checks on your homepage, and we open your container.
Free for one site and 1,500 monthly sessions. Pro from €7 a month, plus VAT, for unlimited sites.
Step by step installs for WordPress, Shopify, Webflow, Wix and more.
Free for one site
Banner, scan and consent records for one site, free. Pro from €7 a month, plus VAT, for unlimited sites.