Your client's Google Ads account still runs. The ads still serve. Since 6 March 2024, though, Google stops using European visitors' data for remarketing, audience building and full conversion measurement unless it gets a consent signal for them. A proper consent mode v2 setup fixes that, and for one client site it takes about one afternoon. You install a Google-certified consent banner, set all four consent parameters to denied by default, choose basic or advanced mode on purpose, and prove it works with a tag check.
The damage comes from shortcuts. A homemade banner. A default consent state that fires after the Google tag has already loaded. A setup that maps two of the four parameters because those were the only two anyone knew about last year. Each of these looks fine from the client's side and leaves the Google Ads account missing data.
This part covers what changed this month, what to gather before you touch a container, and the first three steps. You'll have the banner chosen, the default state firing first and every banner choice mapped to the right parameter. The later steps cover the mode decision, non-Google tags and testing.
Since 6 March, Google treats EEA traffic without consent signals as traffic it cannot fully use
By the end of this article you'll have three things for each client. A site that sends all four consent signals to Google, a tag check that passes from a European location, and a one-page record you can hand the client showing what was set up, what was chosen and who approved it.
Two weeks ago the EU's Digital Markets Act obligations started applying to Google as a designated gatekeeper. Google responded by enforcing its EU user consent policy through Consent Mode. The policy covers visitors in the European Economic Area and the UK. If your client's tags don't pass consent signals for those visitors, Google won't use their data to build remarketing lists, it won't personalise ads to them, and conversion measurement loses the modelled data that fills the gaps.
Consent Mode v2 adds two parameters to the two you already had. Here's what each of the four controls.
- ad_storage: whether advertising cookies get stored on the visitor's device.
- analytics_storage: whether analytics cookies, such as the ones GA4 uses, get stored.
- ad_user_data: new in v2. Whether the visitor's data can be sent to Google for advertising purposes.
- ad_personalization: new in v2. Whether that data can be used for personalised advertising, which includes remarketing.
So v1 was about cookies on the device, and v2 adds what Google does with the data once it has it. A v1 setup with ad_storage and analytics_storage working perfectly still fails the new requirement.
If your client only gets some traffic from Europe, you still need it. A UK-based dentist running local ads needs it for nearly every visitor. A US software company with 15% European traffic needs it for that 15%, and the setup can be scoped by region so American visitors are unaffected. If you do nothing, the campaigns keep running, but European remarketing audiences stop growing and conversion reporting for those visitors gets thinner every week.
Gather five things before you open a client's tag container
An afternoon turns into a fortnight when you're waiting on a login. Collect these before you book the work.
- Admin access to the client's Google Tag Manager container, or access to the site code if they load gtag.js directly without GTM.
- Admin access to the client's Google Ads account and GA4 property, so you can check diagnostics and consent settings afterwards.
- A list of every tag on the site, including non-Google ones such as social pixels, heatmap scripts and chat widgets.
- The client's privacy policy and current cookie list, so the banner's categories match what the policy says.
- Written sign-off naming who owns the legal decision. That's the client and their adviser, not your agency.
The fifth item matters more than it looks. You implement the setup and you record it. Choosing between basic and advanced mode, deciding what counts as valid consent, and wording the banner are legal calls. Put that in the scope email before you start, and have the client reply to it.
Step 1: Use a Google-certified consent platform, not a banner you built yourself
The action is simple. Pick a consent management platform, or CMP, from Google's certified CMP partner list. A CMP is the tool that shows the banner, stores the visitor's choice and passes it to your tags.
Certified platforms ship with Consent Mode v2 support built in. They send the default and update commands in the format Google expects, and most offer a ready-made template in the GTM template gallery. Google already required certified CMPs from 16 January 2024 for publishers serving Google ads to EEA and UK visitors. Advertisers aren't under that exact rule, but the certified list is the shortest route to a setup Google's systems read correctly.
Once installed, you should see a banner with accept and reject options of equal weight. Same size, same prominence, both on the first layer. There should also be a settings layer where the visitor can toggle categories such as statistics and marketing separately.
Can you keep the client's current banner? Only if it's from a certified platform and supports v2. A cookie banner alone doesn't count as Consent Mode. Plenty of banners hide scripts until someone clicks accept and never tell Google anything. Google gets no signal and treats the visitor as unknown.
Step 2: Make consent mode v2 setup start with every parameter denied before any tag fires
Order is everything here. Google tags need to know the consent state before they load, so the default has to arrive first.
In Google Tag Manager, open Admin, then Container Settings, and tick Enable consent overview under Additional Settings. A shield icon appears on the Tags screen. That's where you'll later see every tag's consent status.
Next, set the default consent state. If your CMP has a GTM template, add it as a tag and fill in the default settings there. In plain words, the default command tells Google that for visitors in these regions, all four parameters start as denied. It looks roughly like this.
gtag('consent', 'default', {
'ad_storage': 'denied',
'analytics_storage': 'denied',
'ad_user_data': 'denied',
'ad_personalization': 'denied',
'region': ['AT', 'BE', 'DE', 'FR', 'GB', 'IE', 'NL'],
'wait_for_update': 500
});
The region list above is shortened for space. Yours should include every EEA country code plus GB for the UK, because Google's EU user consent policy covers the UK too. The wait_for_update value gives the banner half a second to send an update before tags proceed. If the client wants to treat all visitors the same way, drop the region line and the denied default applies worldwide.
Fire this tag on the Consent Initialization - All Pages trigger. It's a built-in GTM trigger that runs before the standard Initialization and All Pages triggers, so the default lands before any other tag gets a chance to fire. In preview mode, you should see a Consent event at the very top of the event list, with all four parameters showing denied.
Step 3: Map each banner choice to all four parameters, not just the two you already knew
The default tells Google where things start. The update tells Google what the visitor chose. When someone clicks accept, or saves their preferences, the CMP sends an update command that flips the relevant parameters to granted.
In the CMP's settings, or in its GTM template, connect each banner category to the parameters below. Accepting marketing grants three of them. Accepting statistics grants one.
| Banner category | Parameter | What it controls |
|---|---|---|
| Statistics | analytics_storage | Analytics cookies, such as GA4's |
| Marketing | ad_storage | Advertising cookies on the device |
| Marketing | ad_user_data | Sending the visitor's data to Google for ads |
| Marketing | ad_personalization | Using that data for remarketing and personalised ads |
In GTM preview, accept marketing only. You should see an update event after the Consent Initialization one, with ad_storage, ad_user_data and ad_personalization now granted and analytics_storage still denied. Then clear cookies, reload, accept statistics only, and check the reverse. If one click flips all four, the categories aren't separated, and the visitor's choice isn't being respected.
The usual mistake here comes from upgrading a v1 setup. Last year's mapping sent ad_storage and analytics_storage, and nobody added the two new ones. The banner looks identical, the preview shows grants happening, and Google still receives no instruction for ad_user_data or ad_personalization. Check all four, every time, including on sites you set up last year.
Step 4: Choose basic or advanced mode on purpose and write the choice down
There are two ways to run Consent Mode, and they differ in what happens to a visitor who clicks reject. Neither is wrong. The real problem is picking one by accident because it happened to be the default in the CMP template, and then having nothing written down when the client asks why.
Basic mode blocks Google tags completely until the visitor consents. Someone who declines sends Google nothing at all, no cookies and no pings. It's simple to explain to a client's legal adviser, because the rule is that nothing loads without permission. The cost is weaker modelling. Google gets no signal from people who decline, so it falls back on a general model to estimate the conversions it can't see.
Advanced mode loads Google tags straight away in a denied state. For visitors who decline, the tags set no cookies, but they send cookieless pings carrying basic, non-identifying information such as the timestamp, the browser and whether a conversion happened. Google uses those pings to model conversions and fill the gap left by declined consent. You get better data. The trade-off is that something does go to Google before consent, and some legal advisers aren't comfortable with that under their reading of EU rules.
| Basic mode | Advanced mode | |
|---|---|---|
| Google tags before consent | Blocked | Loaded, denied state |
| Data sent when visitor declines | None | Cookieless pings |
| Conversion modelling | General model only | Modelled from the site's own pings |
| Easier to defend | Yes | Depends on the adviser's view |
Modelling also isn't automatic. Google needs enough volume before it models anything. For Google Ads conversion modelling, Google's guidance puts the threshold at around 700 ad clicks over seven days per country and domain grouping. GA4 behavioural modelling needs at least 1,000 events a day from users who declined analytics, sustained for seven days. A small local client running a few hundred clicks a month won't hit those numbers, so advanced mode buys them very little. For them, basic mode is the obvious choice.
Warn the client about the numbers before you switch anything on. Reported conversions for European visitors will drop after setup, more so in basic mode. Sales haven't fallen. Google has stopped counting people who never agreed to be counted. Put that sentence in your handover email so the first monthly report doesn't land as bad news.
Step 5: Add consent checks to the tags Google does not cover for you
Google's own tags read consent state on their own. The Google tag, GA4 event tags, Google Ads conversion tracking and remarketing tags all have built-in consent checks, so once the default and update commands are right, they behave. Everything else on the site ignores Consent Mode completely unless you tell it otherwise.
That covers social media pixels, heatmap and session recording scripts, chat widgets, affiliate tracking and review widgets. For each one in GTM, open the tag, go to Advanced Settings, then Consent Settings, and choose Require additional consent for tag to fire. Add the parameter that matches its job. A social ad pixel needs ad_storage, and usually ad_user_data as well. A heatmap tool needs analytics_storage. A chat widget that sets no tracking cookies can be marked No additional consent required, which tells GTM you checked it on purpose.
Go back to the shield icon on the Tags screen. You should see every tag listed in the consent overview with a status, either built-in checks, additional checks or no additional consent required. Anything still sitting under Not configured hasn't been looked at yet. That list should be empty before you publish.
Then look outside the container. Open the site's page source and search for script tags that aren't GTM. Theme files, page builder header boxes and plugin settings are where pixels hide. A hard-coded pixel fires on page load no matter what GTM says.
Step 6: Prove it works with Tag Assistant, GA4 and the Google Ads diagnostics
Testing from your own office in, say, Chicago or Toronto will show you the non-EEA default, which proves nothing. Use a VPN set to an EEA country, or a browser profile routed through one, and open a private window so no earlier consent choice is stored.
In Tag Assistant, connect to the client's site. Click the first event in the list and open the Consent tab. You should see all four parameters, ad_storage, analytics_storage, ad_user_data and ad_personalization, listed with an on-page default of denied. Click accept on the banner, then select the next event. The on-page update column should now show granted for the categories you chose. If any of the four is missing from the table, Google never received it.
Now start a fresh private window and click reject. Work through a few pages and the thank-you page of a test form. In basic mode, no Google tags should fire at all. In advanced mode, Google tags fire but the Consent tab shows everything denied. In both modes, the Tags Fired list should contain no social pixels or heatmaps. Screenshot each result for the client record.
Next, check what Google itself sees. In Google Ads, go to Goals, then Conversions, then Summary, open a conversion action and select its Diagnostics tab. It reports whether Consent Mode signals are arriving and in what share of traffic. In GA4, go to Admin, then Data streams, open the web stream and look at Consent settings. It shows whether ad_user_data and ad_personalization signals are being received for EEA traffic.
If the check fails, the cause is almost always one of four things
Failed tests tend to repeat the same handful of faults. Work through these in order, because the first one is the most common and the quickest to spot in preview mode.
The default consent state loads after the Google tag
In Tag Assistant, the Google tag fires on Initialization or Container Loaded, and the consent default appears after it. Move the CMP's default tag onto the Consent Initialization - All Pages trigger, and make sure the Google tag isn't also on that trigger. On gtag.js sites, move the default command above the Google tag snippet in the page head.
Only two of the four parameters are being sent
The Consent tab shows ad_storage and analytics_storage but no ad_user_data or ad_personalization. That's a v1 mapping or an outdated CMP template. Update the template from the GTM gallery to its current version, then remap the marketing category to grant all three advertising parameters, as in Step 3.
European visitors are getting the wrong regional default
Tests from one EEA country pass and another fails, or every European test shows granted by default. Check the region list in the default command for missing or mistyped country codes, including GB for the UK. Then retest from at least two EEA countries, for example Germany and Spain, plus the UK.
A tag outside the container ignores consent entirely
A pixel or analytics script fires after reject, but it isn't in GTM. Find it in the theme, plugin or page builder settings, delete it there, and rebuild it in GTM with the right consent checks. Two related faults show up the same way. A second Google tag duplicated in theme code sends hits with no consent state, so remove the hard-coded copy. And a caching plugin or CDN serves an old page without the banner script, so purge the cache after publishing and test again.
Bill it as a compliance deliverable and close the email consent gap at the same time
This work is fixed, finite and easy to describe, which makes it easy to sell. Scope it as a deliverable per client site, not as hours. The output is a one-page record listing the certified CMP chosen, the mode chosen and who approved it with the date, the Tag Assistant screenshots for denied default, accept and reject, the Google Ads and GA4 status once active, and a retest date.
Then add a quarterly recheck to the retainer. Sites change. Someone installs a new chat widget, a developer pastes a pixel into the footer, a CMP template falls out of date. A short recheck against the same record catches those before they cost data. If you're shaping your retainer strategy for this year, the recheck sits well beside reporting and deliverability reviews as a line clients understand.
There's one gap this setup doesn't close. Cookie consent and email consent are separate things. A visitor who accepts every cookie on an ad landing page hasn't agreed to receive marketing emails, and a visitor who rejects cookies can still sign up to a newsletter. If your client's European ads send people to a page with a sign-up form, that form needs its own clear consent, a record of when and how each address joined, and protection from fake submissions. Our guide to lead capture forms secured before launch covers that side in full.
SendTo handles the email side for agencies. It doesn't set up Consent Mode, and nothing in this article depends on it. What it does is give your clients bot-protected signup forms, embedded on their own site or hosted on a SendTo landing page, with optional double opt-in so each European subscriber confirms their address before the first campaign goes out. Before sending, an AI reviewer that checks basic compliance looks over subject lines, structure, language and links. Agencies run all of it under their own brand and their own prices. See the pricing page for what the partner plan costs.
So a client advertising to Europe ends up with ads that pass Google's consent check, a landing page form that collects real, confirmed subscribers, and one record covering both. That's a full afternoon of work with a clear handover, and it keeps paying back every quarter you recheck it.
Recommend SendTo to agencies and earn 20% of the partner subscription every agency you refer pays us, every month they pay it. Attribution lasts 90 days from the first click, first touch wins, and commission is paid monthly by PayPal.
Join the SendTo affiliate programme


