To set up Consent Mode v2, you need a consent banner, four consent signals (ad_storage, analytics_storage, ad_user_data and ad_personalization), a default consent state that loads before any Google tag fires, and an update command that runs when a visitor makes a choice. Then you verify it in Tag Assistant and in the Diagnostics tab of your Google Ads conversion actions. This guide walks through each step for Google Tag Manager and gtag.js, explains Basic versus Advanced mode, and covers what a US home service business should think about before switching it on.
TL;DR
- Consent Mode v2 adds two signals, ad_user_data and ad_personalization, to the original ad_storage and analytics_storage. Google Ads uses all four.
- The default consent command must run before any command that sends measurement data. Order matters more than anything else in the setup.
- Advanced mode keeps tags loaded and sends cookieless pings while consent is denied. Basic mode blocks tags until the visitor chooses. Google says Advanced gives better modeling.
- Verify in Tag Assistant first, then in Google Ads under Goals > Conversions > Summary > Diagnostics. Status can take 48 hours to appear.
- In the US, wire your opt-out choices to the right signals and ask your privacy counsel which defaults fit your states.
Table of Contents
- What Consent Mode v2 does (and what it does not)
- Basic vs. Advanced mode: pick before you build
- Before you start: the checklist
- Step 1: Set the default consent state
- Step 2: Send the update when a visitor chooses
- Step 3: Implement in Google Tag Manager
- Step 4: Implement with gtag.js
- Step 5: Test it in Tag Assistant
- Step 6: Confirm it in Google Ads
- What US businesses should know
- Connecting consent to the rest of your tracking
- Our perspective
- Need this wired into your whole funnel?
- Common setup problems and quick fixes
- FAQ
- Sources
What Consent Mode v2 does (and what it does not)
Consent mode is a way of telling Google's tags what your visitor agreed to. It is not a banner. Google's Tag Manager Help is explicit that consent mode does not provide a consent banner or widget. It interacts with the banner you already run and adjusts how Analytics, Ads and other tags that create or read cookies behave.
The v2 update arrived in November 2023. According to the Google for Developers consent guide, it requires two parameters in addition to ad_storage and analytics_storage:
| Signal | What it controls |
|---|---|
| ad_storage | Whether advertising cookies can be read or written |
| analytics_storage | Whether analytics cookies can be read or written |
| ad_user_data | Consent to send user data to Google for advertising purposes |
| ad_personalization | Consent to use data for personalized advertising, such as remarketing |
Each one takes a value of granted or denied. They operate independently, so a visitor can allow conversion measurement while declining remarketing.
Why it matters for your Google Ads account
When consent is denied, you lose observable conversions. Google's consent mode modeling page explains that conversion modeling uses Google AI to quantify the relationship between consented and unconsented users. The modeled conversions show up in your Conversions column and flow into downstream reports and bidding tools.
That is the practical reason to care. If your bidding runs on conversion data, a gap in that data means weaker decisions on every dollar of spend. One developer guide also notes that without the ad_user_data and ad_personalization signals, accounts can lose audience lists and remarketing for visitors in the European Economic Area and the UK.
Basic vs. Advanced mode: pick before you build
This decision shapes the rest of your implementation, so make it first. Google's consent mode overview describes the two options.
Basic mode stops Google tags from loading until the visitor interacts with the banner. Nothing goes to Google before that choice. If the visitor declines, no data is transferred, and conversion modeling relies on a general model.
Advanced mode loads Google tags when the page opens, with defaults set to denied. While consent is denied, tags send cookieless pings. Only after consent is granted do tags send full measurement data. This feeds an advertiser-specific model, and Google states that Advanced provides improved modeling compared with Basic.
| Basic | Advanced | |
|---|---|---|
| Tags load before choice | No | Yes, with denied defaults |
| Data sent before choice | None | Cookieless pings |
| Data if visitor declines | None | Cookieless pings only |
| Modeling | General model | Advertiser-specific model |
| Typical fit | Strictest consent posture | Teams that want the most measurement recovery |
For a home service company spending real money on Google Ads, the measurement difference is the main argument for Advanced. The legal posture is the main argument for Basic, particularly if you also get European traffic. Some commentators note that sending even cookieless pings before consent is unsettled under the EU ePrivacy rules, so raise it with your counsel if you have EEA or UK visitors.
Before you start: the checklist
Get these in place first, and the rest goes quickly.
- A consent banner you control. Any banner works, as long as it can fire events when a visitor accepts, rejects or changes a choice.
- Google tag on every page. With gtag.js, Google's guide says the tag must be installed on every page because the consent code is added to each one.
- A decision on regions. Decide where you show a banner and where you do not. Defaults can be scoped by region.
- Access to Tag Manager or the site code. You need to be able to place a script high in the page head.
- Linked accounts. Confirm your Google Analytics property is linked to your Google Ads account.
If you use Tag Manager, Google recommends loading your banner through the container using a consent mode template, which you can build yourself or take from the Community Template Gallery.
Step 1: Set the default consent state
The default state is what Google's tags assume until the visitor chooses. Per the official guide, set a default for each consent type you use, and run the default command before any command that sends measurement data, such as config or event.
A typical Advanced mode default for a region where you require opt-in looks like this:
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('consent', 'default', {
'ad_storage': 'denied',
'analytics_storage': 'denied',
'ad_user_data': 'denied',
'ad_personalization': 'denied',
'wait_for_update': 500
});
The wait_for_update value, in milliseconds, tells tags to hold for that long so your banner has time to restore a returning visitor's saved choice. One implementation guide explains that if the consent tool resolves inside that window, the first hit fires consent-aware. Five hundred is a common starting value.
Scope defaults by region
Google's guide says to scope defaults to the regions where you show consent banners, and that more specific regions take precedence. The Cookiebot support documentation gives a US example: the script with your default settings must sit ahead of the gtag.js or GTM snippets, and a setting for US-CA overrides one for US.
In practice that means you can write one default for the whole country and a stricter one for a state or the EEA. Keep the list short and documented, because every extra region is one more thing to maintain.
Step 2: Send the update when a visitor chooses
The default only describes the starting point. When a visitor accepts or rejects, your banner must call the update command with the new values:
gtag('consent', 'update', {
'ad_storage': 'granted',
'analytics_storage': 'granted',
'ad_user_data': 'granted',
'ad_personalization': 'granted'
});
If your banner offers granular choices, map each choice to the right signal rather than flipping all four together. A visitor who allows analytics but declines marketing should produce granted for analytics_storage and denied for the three advertising signals. Google also advises tracking consent updates on the page where they occur, before any page transition, so a choice is not lost.

Most banner platforms handle this call for you once you switch on their Google consent mode integration. Check that they send all four v2 signals, not just the original two.
Step 3: Implement in Google Tag Manager
For most home service sites running Tag Manager, this is the cleanest path.
- In your container, turn on consent overview under Admin > Container Settings so you can see which tags need consent.
- Add a consent mode template for your banner, either from the Community Template Gallery or one your developer built.
- Set the default consent state in that template, including all four signals and your regional rows.
- Fire the banner template on the Consent Initialization trigger, so it runs before every other tag.
- Confirm each Google tag (GA4, Google Ads conversion, remarketing) uses its built-in consent checks.
- Publish, then test.
If your developer builds a custom template, one detail trips people up. A CookieBeam guide explains that templates calling the consent APIs must declare the Accesses consent state permission, and without it the calls fail silently with no console error. If your defaults never seem to apply, check the Permissions tab first.
Step 4: Implement with gtag.js
If you do not use Tag Manager, place the default consent snippet in the head of every page, above the Google tag snippet. Then load gtag.js, then call config. Your banner script calls the update command when the visitor responds.
Two common mistakes break this setup:
- Loading gtag.js before the default command, so the first hit goes out without a consent state.
- Adding the code to some templates but not others, so a few landing pages behave differently from the rest.
Paid landing pages are where this hurts most. Ads send traffic there first, and a page missing the default command means those first visits are measured wrongly. If you run dedicated pages for ad campaigns, add them to your test list. Our notes on landing pages that convert with Google Ads cover how to keep them consistent.
Step 5: Test it in Tag Assistant
Google's verification guide gives the sequence. Start a Tag Assistant session on your site, then:
- Open the earliest Consent event and confirm the default parameters read Denied.
- Accept the banner.
- Open the most recent Consent event and confirm the parameters read Granted.
For a stricter check in Advanced mode, one developer guide suggests confirming the default command comes before config, then verifying the update grants analytics_storage after you allow analytics. Reject, reload, and confirm each optional signal falls back to denied.
In Basic mode, the same guide says filtering the DevTools Network tab by "google" before consent should show no request, and window.dataLayer should be undefined in the console. After you allow analytics, gtag.js should load once with default as the first command.
Step 6: Confirm it in Google Ads
Tag Assistant proves the tags behave. Google Ads proves Google received the signals. Go to Goals > Conversions > Summary, click a website conversion action and open the Diagnostics tab to see consent mode status.
Expect a wait. Google says the active status can take 48 hours to appear, and up to two weeks in some cases. Modeling also needs volume. Per the same page, the threshold is 700 ad clicks over 7 days for a domain and country grouping, and uplift data shows for 4 weeks after modeling starts.
A small local campaign may not reach that threshold in some areas. That does not mean your setup is broken, only that modeling will not start until you have enough traffic.
What US businesses should know
Consent Mode v2 grew out of European rules, and the US works differently. There is no single federal law like GDPR. State privacy laws such as California's CCPA, as well as those in Virginia and Colorado, shape what compliant tracking looks like. Many of them center on notice and the right to opt out rather than prior opt-in. That means your default state in a US region may differ from your European one.
Two practical points follow.
Wire your opt-out to the signals. If a visitor uses your "Do Not Sell or Share" control, that choice should reach Google as ad_personalization denied in your consent update, alongside any other signals your policy ties to it. Which defaults are right for each state is a question for your privacy counsel, not for a tag template.
Remember other scripts. Consent Mode governs Google's tags. It does not automatically control a call-tracking script, a chat widget or a visitor-identification tool. Leadpipe's analysis points out that a visitor-ID tag with no consent trigger fires regardless of the visitor's choice. Put each non-Google script behind its own consent condition.

The June 2026 data controls change
Osano reports that as of June 15, 2026, Google made Consent Mode the single control over advertising data collection for any Analytics property linked to a Google Ads account. The Google Signals setting no longer acts as a second gate. The same update warns that remarketing and Smart Bidding audiences will include only users who granted ad_storage, so audiences that leaned on Google Signals may shrink if your consent capture is under 100%.
If your remarketing lists dropped around that date, check your consent defaults and banner wiring before blaming the ads.
Connecting consent to the rest of your tracking
Consent Mode is one layer of a measurement stack. For a home service company, the stack usually includes call tracking, form tracking, and offline conversions fed back from the CRM. Each piece needs to respect the same consent state.
- Enhanced conversions send hashed customer data, and they depend on the consent signals being right. Our guide to fixing the enhanced conversions setup covers the account side.
- GCLID capture stores the click ID with each lead. See how to pass the GCLID into your CRM so booked jobs trace back to the click.
- Offline conversion imports return closed jobs to Google Ads. Our walkthrough of offline conversion tracking in Google Ads shows how to close the loop.
Get consent right first, because every later step builds on that data.
Our perspective
Most home service owners we meet do not have a consent problem. They have a measurement problem, and consent is where it surfaces. A Google Ads account that cannot see which calls became booked jobs will overpay for the wrong clicks, and a broken consent setup quietly makes that worse.
We treat Consent Mode as part of the infrastructure, not a checkbox. The default state, the banner, the call tracking, the CRM and the ad platform all have to agree about what a visitor chose. When they do, modeled conversions fill the gaps honestly, and bidding has cleaner signals to work with.
That is why we build and host our AI systems in-house. Our lead dispatch and intent scoring run on our own on-premise servers, designed so client data stays proprietary and secure, and not passed to a third-party AI. When a business is careful about what visitors agreed to, it should be just as careful about where the resulting data goes.
Our advice is simple. Choose Advanced mode if your counsel is comfortable with it, send all four signals, test with Tag Assistant, and then check your Google Ads diagnostics a few days later. Do the unglamorous parts properly and the numbers you steer by become far more trustworthy.
Everson Gorski
Need this wired into your whole funnel?
Consent Mode is only useful if the data behind it ends up in booked jobs. At Leapify Media we manage Google Ads and Meta Ads for home service businesses, and we connect tracking, CRM and automation so spend ties back to revenue. Google Ads Management is $1,500 per month, and our Foundation plan starts from $2,500 per month. CRM Integration starts from $3,000 as a one-off project. See all options on our pricing page, or look at the services we offer.

We work with home service companies at $500K in annual revenue and above, including HVAC, plumbing, roofing, landscaping, electrical and restoration businesses.
Common setup problems and quick fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Defaults never apply | Default command runs after the Google tag | Move the consent script above gtag.js, or use the Consent Initialization trigger in Tag Manager |
| Custom template does nothing | Missing consent state permission | Add the Accesses consent state permission in the template |
| Only two signals appear | Banner integration is on the old version | Update the banner integration so it sends ad_user_data and ad_personalization |
| Diagnostics show no status | Not enough time or volume | Wait up to 48 hours, sometimes two weeks, and check click volume |
| Remarketing lists shrink | Audiences now include only consented users | Review banner placement, wording and signal mapping |
| Some pages behave differently | Snippet missing from certain templates | Audit every template, including ad landing pages |
FAQ
Is Consent Mode v2 required for Google Ads in the US?
Google introduced the v2 parameters in November 2023, and they are what Google Ads uses to handle consent for advertising data. US state laws are generally built around notice and opt-out, so whether you need a banner depends on your obligations. Ask your privacy counsel, then use Consent Mode to pass whatever choices you collect.
Do I need a consent banner to use Consent Mode?
Yes. Google states that consent mode does not provide a banner or widget. It works with the banner you already use and adapts tag behavior to the visitor's choice. Pick a banner that can send all four v2 signals.
Should I choose Basic or Advanced mode?
Advanced loads tags with denied defaults and sends cookieless pings, which Google says gives better modeling. Basic sends nothing until the visitor chooses. If measurement recovery matters most and your counsel agrees, Advanced is usually the better fit. If you want the most conservative position, choose Basic.
How long until Google Ads shows consent mode as active?
Google says the status can take 48 hours to appear, and up to two weeks in some cases. Check the Diagnostics tab on a website conversion action under Goals > Conversions > Summary. Modeling also needs 700 ad clicks over 7 days for a domain and country grouping.
Does Consent Mode control my other scripts?
No. It controls Google's tags. Call tracking, chat and visitor-identification scripts need their own consent conditions, or they will fire whatever the visitor chose.
Sources
- Set up consent mode on websites, Google for Developers
- About consent mode, Tag Manager Help
- About consent mode modeling, Google Ads Help
- About consent mode, Google Ads Help
- Verify consent mode implementation, Tag Manager Help
- Implementing Google Consent Mode, Cookiebot Support
- How to implement Google Consent Mode v2, inth
- Google Consent Mode v1 vs v2, Kukie.io
- Google Consent Mode v2 implementation guide, CookieChimp
- Build a custom consent mode template for GTM, CookieBeam
- Google Consent Mode v2 complete 2026 implementation guide, YeezyPay
- Navigating Google Consent Mode v2 (2026 update), Osano
- Google Consent Mode v2 and visitor identification, Leadpipe
