Consent mode is a signal layer that passes a visitor's cookie choice to Google tags. When the user consents, measurement works normally; when they decline, tags do not go silent but switch to a restricted mode that sends signals without identifiers. The second version adds two extra signals covering advertising data, making the distinction sharper. Without it, users who decline send nothing at all and those conversions sit outside your measurement entirely.
What do the four consent signals do?
Consent mode is not a single on-off switch; it splits the user's choice into four separate areas. In a correct setup, the selection in your cookie banner maps one to one onto these four signals.
- Analytics storage: whether analytics cookies may be used.
- Ad storage: covers advertising cookies; this one directly drives remarketing audiences.
- Ad user data: whether user data may be sent to Google for advertising purposes.
- Ad personalization: whether personalized ads may be served.
How does declined consent affect measurement?
The impact lands in three places with different severity. Directly measured conversions fall, modelling partially restores the total, but audience size takes the hardest hit, because joining an audience requires ad storage consent. That is why sites with low consent rates see remarketing lists shrink fast.
How do you set up consent mode?
Setup takes four steps and the last one is skipped most often. Installing a banner is not enough; you have to verify that the choice it captures actually reaches your tags.
- Choose a consent tool: use a certified cookie banner solution compatible with Google.
- Wire the signals: make sure the banner's choices map correctly onto the four consent signals.
- Gate the tags: ensure tags do not fire for categories the user declined; this link lives in your tag manager.
- Verify: decline in a browser and confirm that tags switch to restricted mode.
How do you raise the consent rate?
Acceptance varies noticeably with banner design. But there is a boundary: designs that mislead users, such as hiding the reject option or steering with color contrast, create legal risk and damage trust. The right approach is to make the request honest and legible.
- Say what you want it for: a concrete benefit instead of improving the experience; people consent more when they understand the trade.
- Show both options equally: accept and reject should have equal visibility; this is both a legal and an ethical requirement.
- Keep the banner light: a heavy banner that delays the page hurts both consent rate and page speed.
- Do not ask twice: remember the choice; a banner that reappears on every page drives users away.
Why do your conversion numbers disagree?
Ads Sensor puts your ad platforms next to GA4 and explains measurement gaps with AI analysis.
How do you recover consent-driven loss?
Consent mode reduces the loss but does not erase it. Two paths close the remaining gap: server-side measurement and first-party data. Server-side sending works independently of browser limits and recovers part of the signal; we covered the method in server-side tracking. For the Meta equivalent see Conversions API setup. The most durable long-term answer is collecting your own data: first-party data strategy.
What happens without consent mode?
Two consequences follow. On the measurement side, declining users send no signal, conversions under-report, and Smart Bidding learns from weaker data. On the compliance side, tags that keep firing after a user declined create serious exposure under data protection rules. Part of the gap between GA4 and platform numbers also comes from here; see conversion discrepancy.
Consent mode is not a compliance checkbox, it is part of your measurement infrastructure. To see cross-platform conversion gaps in one dashboard, join the Ads Sensor beta.