After you add a consent banner, the numbers in GA4 and ad platforms can change for perfectly good reasons. What matters is telling a smaller observable data volume caused by privacy choices apart from a technical error that stops tags from behaving correctly after the user makes a choice.

In short

The CMP collects the choice

The banner has to store the user’s consent and pass it on in a technically correct way.

Consent Mode controls Google tags

The default state and the updated state determine how Google tags behave.

Test the real user flow

How the banner looks isn’t enough on its own: you need to check the tags, the consent state and the data requests.

“Our GA4 traffic dropped after we added a cookie banner.” This question comes up a lot in practice. Sometimes the reason is perfectly logical: users used to be tracked before consent was taken into account, and now they aren’t. But sometimes it’s a technical error. The consent state arrives too late, a tag fires in the wrong order, or the user’s choice doesn’t update.

The consent banner, or CMP, collects the user’s choice. Google Consent Mode helps Google tags behave according to that choice. One doesn’t replace the other.

CMP / cookie banner

Shows the options, stores the user’s preference and passes it on technically to the website and the tag management system.

Google Consent Mode

Passes the consent state on to Google tags, for example analytics_storage, ad_storage, ad_user_data and ad_personalization.

I don’t check consent management just by whether the banner opens. I also check what actually happens to the tags before and after the user makes a choice.

Richard Pikmets

Why can GA4 data drop after you add a banner?

  • some users decline analytics;
  • with basic Consent Mode, Google tags are held back more before consent;
  • the previous setup may have tracked users before consent was taken into account;
  • the new CMP may block some tags that weren’t blocked before;
  • if there’s a technical error, tags may not recover even after the user accepts.

In basic mode, Google tags are held back more strictly before the user consents. In advanced mode, Google tags can load in a denied state and send cookieless pings. Which one fits depends on the company’s requirements, the technical setup and a legal assessment. This article covers the technical side and isn’t legal advice.

Four common technical mistakes

1. The consent default is set too late

If the GA4 page_view or Google Ads tag manages to fire first and the consent state is only set after that, the order of events is wrong.

2. Accepting doesn’t update the consent state

The banner may visually show “Accept”, but in GTM analytics_storage or ad_storage stays denied.

3. The tag is blocked twice

The CMP blocks the tag one way, and GTM has a separate consent condition on top. The result can be a tag that doesn’t fire even after the user accepts.

4. Meta and Google are put under the same logic

Google Consent Mode only works with Google tags. The behaviour of the Meta Pixel and other services has to be reviewed separately. Server-side GTM doesn’t let you bypass consent either, and the server-side GTM article explains more.

  1. I open the site in a new private browser window.
  2. I check the consent default before any choice is made.
  3. I look at which tags actually fire.
  4. I accept and check whether the consent state updates (consent update).
  5. I do the same with declining.
  6. I change the choice later and check whether the consent state and tags update.
  7. I look at GTM Preview, the browser’s network requests and, if needed, GA4 DebugView.

Which CMP should you use?

There’s no universal answer. If you already have a working Usercentrics, OneTrust or other solution, there’s no point replacing it just because of a trend. If you need a new managed CMP with Google Consent Mode support, one practical option is Cookiebot by Usercentrics.

What won’t a CMP solve for you?

A CMP on its own doesn’t guarantee that GTM, GA4, Google Ads and Meta behave correctly. After installing it, you still need to test the technical data flow with real usage scenarios.

Affiliate note: the Cookiebot by Usercentrics link is an affiliate link. If you sign up through it, I may earn a commission; your price doesn’t change.

Do smaller numbers mean worse analytics?

Not necessarily. With privacy-aware tracking, the goal isn’t to track every user at any cost. What matters more is knowing which share of the data is observable, how consent affects it and whether campaigns get the right data for optimisation. If a visitor declines, hashed customer data is not sent either; the enhanced conversions article explains more.

If the numbers changed sharply after you added the banner, check the Google Tag Manager, GA4 and conversion tracking chain together rather than looking for the answer in a single report.