Skip to content
TagSentry
Blog

Answer · Consent

Why your analytics dropped after you added a cookie banner

The four usual causes of a traffic or conversion drop after a banner goes live, how to tell which you have, and how to get back the data you could keep.

The TagSentry team · September 24, 2026 · updated October 2, 2026 · 4 min read

The question, as people ask it

“We installed a cookie banner and now GA4 traffic and conversions are way down. Did we break something?”

Asked in reddit.com, reddit.com, community.shopify.com

The short answer

Some drop is expected, because people who say no aren't counted. A big drop usually comes down to one of these causes. You're applying EU rules to everyone, Google's tags are fully blocked instead of running cookieless, your consent defaults load too late, or blocking triggers are swallowing the page view too. Each one is quick to test.

First, the drop you should expect

A working banner will reduce what you see. In places where the law says ask first, anyone who clicks "Reject all" or ignores the banner is no longer tracked with cookies, which is what the banner is for.

How much you lose depends on where your visitors are and how the banner asks. Worry if the drop is bigger than your share of visitors from ask-first regions, or if conversions fall while orders and leads carry on as normal.

Cause 1: the strictest rules applied to everyone

Most banners ship with one setting for the whole world, usually the EU's. So a visitor in Texas gets a wall they didn't need, and their visit is dropped until they answer.

Most US states work the other way round: the law lets you track until the visitor opts out. As one analyst put it: "Applying EEA strictness worldwide throws away hits you were allowed to keep."

To check, visit your site from a US connection in a private window. If you get the same full-screen banner and your Google requests show consent denied, this is your problem.

The fix is regional rules. Ask first in the EU, UK and similar places. Let US visitors opt out, and honour the browser privacy signal (GPC) in the states that require it.

Cause 2: Google's tags blocked instead of cookieless

You can hold Google's tags in two ways. Block them completely until consent, or let them run without cookies and send anonymous pings until the visitor answers. Google calls these Basic and Advanced.

With full blocking, a visitor who never answers leaves no trace at all. With the cookieless approach, Google at least knows a visit or a conversion happened, and it can model some of what it didn't see.

To check, filter the browser's network panel to collect. Before you answer the banner, is there any request to Google Analytics? None at all means full blocking.

Pick one on purpose. Full blocking is the more cautious reading of EU rules and is common in Germany.

Running cookieless recovers more data, but modelling only works above Google's thresholds: at least 1,000 events a day with analytics storage denied for seven days, and 1,000 daily consented users. Small sites won't see modelled numbers either way.

Cause 3: defaults that load too late

Consent Mode needs a default state set before any Google tag runs. If your banner loads after Tag Manager, or from a Tag Manager tag that fires late, the first hits of each visit go out with no consent state. Depending on the tag, they're dropped or sent wrong.

To check, open Tag Manager's preview and look at the very first event on the page. The consent state should already be set there. If it only shows up a few events later, your defaults are late.

To fix it, set the defaults from a script at the very top of <head>, above your Tag Manager snippet, or from a tag on Tag Manager's "Consent Initialization" trigger. A tag on "All Pages" is too late.

Cause 4: blocking triggers that eat the page view

A common do-it-yourself setup adds a blocking trigger to each tag: "don't fire unless marketing consent is granted." If that also catches the GA4 configuration tag, there's no page view for anyone who hasn't answered yet, and no session to attach later events to.

In a thread about this exact setup, one person warned that blocking triggers for consent "will completely" wreck your traffic reporting.

To check, look for tags whose triggers include a consent condition, starting with the Google tag or GA4 configuration tag.

To fix it, let Consent Mode handle Google's tags and take the consent-based blocking triggers off them. Keep blocking triggers for non-Google tags, which don't read Consent Mode.

A quick diagnostic table

What you seeMost likely cause
Drop across all countries, including the USCause 1
Zero Google requests before the banner is answeredCause 2
Conversions attributed to "Direct" much more than beforeCause 3 or 4 (sessions lose their source)
Page views fine, conversions goneA tag with "Not set" consent settings, or a trigger problem
Drop only on one page type, like checkoutA tag on that page fires before or without consent state

Check that the drop is really tracking

Before you change anything, compare with something the banner can't touch, like orders in your store, leads in your CRM or calls. If those held steady while analytics fell, the problem is measurement. If they fell too, it's demand, and no consent setting will fix that.

If it's Google Ads conversions rather than GA4 that fell, this triage table covers the Ads side, including a banner that turns every Accept into a cookieless ping.

How TagSentry handles this

TagSentry gives each visitor the rules for where they are, so US visitors aren't shown an EU wall.

Google's tags run cookieless until a visitor agrees, so Google can still model some of what it doesn't see. Our script sits above Tag Manager on the page, so it's the one that sets the defaults. Event monitoring shows you, event by event, what still reaches Google after the change.

Sources

  1. r/GoogleAnalytics: Your GA4 traffic probably did not drop, your consent rate did
  2. r/GoogleAnalytics: Geo-based consent got my team back real data
  3. r/GoogleAnalytics: blocking triggers and traffic reporting
  4. Google Analytics Help: Behavioral modeling for consent mode
  5. Google Tag Manager Help: Consent mode overview