Consent Mode Explained: Measuring With Privacy in Mind

When a visitor declines cookies, your analytics and ad tags should respect that. Consent mode is a way to tell Google's tags what the visitor agreed to, so the tags adjust their behaviour instead of ignoring the choice or breaking.

This is a practical overview, not legal advice. Privacy rules differ by country and change over time, so check requirements for your audience with a qualified professional.

What consent mode does

Your cookie banner records a visitor's choices, such as allowing or denying analytics storage and advertising storage. Consent mode passes these choices to Google tags as signals.

• If the visitor agrees, tags work normally and can use cookies.
• If the visitor declines, tags limit what they store and may send reduced, cookieless signals, depending on your configuration.

Google can use some of these signals for modelling, which estimates part of the activity that consented data cannot show. Modelled figures are estimates, so treat them as directional and not exact counts.

The setup flow

1. Choose a consent management platform (CMP) that supports consent mode, or confirm your banner tool does.
2. Set default consent states before tags load. Many sites default non-essential storage to denied until the visitor chooses, particularly where local rules require it.
3. Make the banner update the states when the visitor accepts, rejects or customises.
4. Configure your tags in Google Tag Manager so analytics and ad tags check the consent state.
5. Test with Preview mode and your browser's developer tools in both accept and reject scenarios.

Our cookie consent banner guide covers the banner design and wording side.

What changes in your reports

Expect some differences after you introduce proper consent handling:

• Fewer users and sessions may be observed directly, because declined visitors are not tracked in the usual way.
• Conversion counts in ad platforms may fall, and platforms may fill part of the gap with modelling.
• Channel reports may show more direct or unassigned traffic when campaign parameters are lost.

Add a note to client or team reports when you introduce the banner, so a dip is not misread as a performance problem. A change log in your website analytics setup checklist helps here.

A hypothetical example

A clinic chain launches a consent banner. The following month, reported sessions fall while appointment enquiries received by phone and WhatsApp stay steady. The team concludes the fall is mainly a measurement effect, not a demand problem, and cross-checks with internal booking counts before reporting.

Practical tips

• Treat first-party sources, such as CRM and booking data, as your anchor for real business results.
• Keep a record of the date you changed consent settings.
• Do not hide the reject option or pre-tick boxes; clear choices build trust and are often required.
• Review your setup after any banner, theme or tag changes.

For the bigger picture, read our note on privacy-first marketing.