The ads are running and the phones are ringing, but Google Ads reports zero conversions. Often the cause isn't the ads but the order in which the cookie banner and the tracking codes load on the website. We'll show where it goes wrong and how to check it.
What Consent Mode v2 is
Consent Mode is how a website tells Google whether the visitor consented to cookies. Tracking tags behave differently depending on it: with consent they measure fully, without consent they send only limited signals without cookies. Version 2 added two new consent signals for advertising. For websites targeting Europe it has been a condition for personalised ads and remarketing since March 2024.
The whole thing only works if the default consent state is set before the first tag fires. Where the order gets mixed up, tracking either doesn't start or runs regardless of the visitor's choice. Both are a problem, one for marketing, the other for GDPR.
Typical mistakes
Where several people added tracking over the years, each usually put their code in a different place. The website then ends up with this:
- The cookie banner loads twice. Once inserted directly into the website template, a second time through Google Tag Manager. The banner then shows warnings and the consent state can get overwritten.
- A standalone Google Ads or Analytics code runs alongside Tag Manager. Such code doesn't know about the Tag Manager settings and may not respect consent.
- The default consent state is set too late. If the code doesn't set it before Tag Manager loads, the tags fire before they know it.
- What counts as an enquiry for the company isn't measured. Form submissions are, but clicks on the phone number or email aren't.
On one company website, Cookiebot loaded twice, once directly in the template and again through Google Tag Manager, and a standalone Google Ads code ran next to it. After the cleanup, Cookiebot loads only through Tag Manager, and the default consent state is set by code in the page header before it, so it is known before anything is measured.
What to measure as an enquiry
For services where people prefer to call, a submitted form is only part of the enquiries. That's why on the same website we measure clicks on the phone number, clicks on the email address and, separately, the start of filling in the form. The difference between started and submitted forms shows how many people the form put off.
Each of these events goes to Tag Manager and from there to Analytics, or as a conversion to Google Ads. One place, one set of consent rules.
How to check it
- Open the website in a private window and look at the console in the browser's developer tools. You'll see a warning about the cookie banner loading twice right away.
- On the Network tab, search for
gtag/jsandgtm.js. If a standalone gtag loads besides Tag Manager, find out who put it there and why. - Start preview mode in Tag Manager (Tag Assistant). The first event should show the default consent state, and only after it the other tags.
- Decline the banner once and accept it once. After declining, no analytics or advertising cookies may be stored.
- Make a test enquiry, click the phone number and the email address, and check that the events show up in the preview and in the real-time report.
When to bring in an expert
When a website pays for ads and the conversions in Google Ads don't match how many enquiries actually came in, it pays to go through the whole tracking setup. It's not about one tag. Often the codes that have piled up on the website over several years need cleaning up and consolidating into Tag Manager. We'll do that and leave you a description of what is measured where, so the mess doesn't come back with the next campaign.
Before you increase the campaign budget, check the tracking first. Deciding on the budget based on numbers that miss half the enquiries costs more than an hour of checking.