How-to · Updated October 11, 2026
Set up consent mode so a cookie banner doesn't wipe out your conversions
Updated October 11, 2026
1 hour
Let Google's tags load and read the banner's answer instead of being blocked. Turn on consent mode in your banner tool, map its categories to Google's four consent types, and remove extra consent blocks on Google tags in Tag Manager. A banner that blocks tags outright sends Google nothing about visitors who decline.
Before you start
- Admin access to your banner tool (the consent management platform) and Publish access to Tag Manager.
- A decision on what the banner must ask, from whoever handles privacy for the business. Which laws apply, and which category a cookie belongs in, are legal questions; this page covers how the answers reach Google.
- A list of every script the banner controls, with the category each is filed under, call tracking included.
Make the banner send signals instead of blocking
This part sets the banner to tell Google's tags the visitor's answer instead of stopping them loading, because a blocked tag leaves Google nothing, not even the fact that the visitor declined.
- In your banner tool, turn on its Google consent mode setting. Google's Set up consent mode page links instructions for many banner tools; if yours is not listed, ask its support team.
- Map the banner's categories to Google's consent types: ad_storage, ad_user_data and ad_personalization to the advertising category, and analytics_storage to the analytics category. Google says ad_user_data is required for tag-based conversion tracking and enhanced conversions, and both ad_user_data and ad_personalization must be granted for personalized advertising such as remarketing.
- Set the defaults your rules call for, and make sure the banner sets them before any Google tag fires (in Tag Manager, a banner tag runs on the Consent Initialization trigger). Google warns that otherwise its tags fire as if consent mode is not in use. For a banner you maintain yourself, Google's instruction is an In-Page Default of denied and an In-Page Update of granted when the visitor accepts.
- If your rules allow advanced consent mode, find the banner setting that blocks Google tags until consent is given, and turn it off or exempt Google's tags from it. Unblock only Google tags that support consent mode. Google says blocked or delayed tags make modeled conversions less accurate.
Remove the old blocks in Tag Manager
This part removes extra consent blocks from Google Ads, Google Analytics, Floodlight and Conversion Linker tags in Tag Manager, which Google says to do once consent mode is in place.
- In Tag Manager, click Tags and read the Firing triggers column for exceptions on those tags. Open each one, click Triggering, and click Remove next to the exception.
- In each of those tags, open Advanced Settings, then Consent Settings, and set Additional Consent Checks to Not set or No additional consent required.
- Replace any trigger built on the banner's consent-granted event with the tag's normal trigger, such as a page view.
- Keep consent checks on tags that are not Google's. Google says they do not change their behavior based on consent mode, so the banner has to control them.
- Click Save on each tag you changed, then Preview to test, then Submit and Publish.
The extra checks cost more than they look. Google warns that if the banner loads after the tags, a tag blocked when it first triggered does not fire even when the visitor accepts a moment later. On a landing page, that click ID may never be stored.
Decide where call tracking and uploads sit
This part decides which banner category the call tracking script sits in, and what consent goes with leads you upload to Google Ads.
- A call tracking script usually does not react to Google's consent mode; check with its vendor. If the banner files it under advertising or marketing, visitors who decline may see your plain number, and the call tracking tool cannot tie those calls to the ad click. Decide its category deliberately with whoever handles privacy, not by the banner's default.
- If you upload leads to Google Ads, send each lead's consent (in a file upload, the Ad User Data and Ad Personalization columns). Google warns that leaving consent empty may make conversions not attributable, and says data from a person in the EEA who denied consent is not used for measurement.
Check it worked
Open Tag Assistant, enter your website's address, and accept all on the banner. In the Summary, select the earliest Consent event: on the tag's Consent tab, the On-page Default column should show the defaults you chose for ad_storage, ad_user_data, ad_personalization and analytics_storage. Select the latest Consent event: On-page Update should read Granted. Under Tags, the Google tags should be listed as fired.
Repeat in a new session and decline. The latest Consent event's On-page Update should read Denied. If you use advanced consent mode, Google's tags should still appear as fired, sending cookieless pings; in basic mode they should not fire at all. Non-Google advertising tags should not fire in either mode.
In Google Ads, click the Goals icon, open Conversions, click Summary, open a website conversion action and select the Diagnostics tab. Google says the consent mode status can take 48 hours to appear, and up to 2 weeks in some cases. Consent mode is implemented is the expected status for most small accounts; modeling needs at least 700 ad clicks over 7 days for a domain and country, among other thresholds.
Basic or advanced consent mode?
In basic consent mode, Google's tags do not load until the visitor interacts with the banner, and when someone declines, nothing reaches Google. In advanced consent mode, the tags load straight away and send cookieless pings while consent is denied, which gives Google an advertiser-specific model instead of a general one. Google recommends letting its tags load in all cases; whether your rules allow it is part of the legal decision above.
What a declined visit still sends
With ad_storage denied, Google's tags write no new advertising cookies and read none, and Ads products truncate the IP address. The pings may still say whether the page or an earlier one carried an ad click ID, along with the consent state and the time, and Google models conversions from them.