Why your GA4 conversions dropped overnight
The campaigns did not change, the site did not change, and yet Tuesday's conversions are half of Monday's. When GA4 falls off a cliff overnight, the cause is rarely the marketing. It is usually the measurement layer, and most often one of five things.
1. Someone touched the banner
The most common culprit. A CMP update, a new banner version, a redesign that moved the accept button: anything that changes how or when consent is granted changes how many tags fire. If the drop lines up with a deploy or a CMP release, start there. Check whether the default consent state is still set before your Google tags load, and whether the update silently switched you from advanced to basic behaviour.
2. A tag now fires before consent is ready
Tag order is fragile. If Google Tag Manager loads before the consent defaults are set, tags fire in a denied state or get blocked entirely, depending on your setup. The symptom is a partial drop rather than a clean zero: some browsers, some regions, some pages. The fix is structural: consent defaults first, everything else after. In GTM, the Consent Initialization trigger exists precisely for this. The same fault has a second signature worth knowing: sessions carrying conversions but no origin at all, which is one of the three shapes of Unassigned traffic after a banner.
3. A region rule flipped
Consent platforms let you vary behaviour by region: explicit consent in the EU, notice only elsewhere. One toggle in those settings can put your largest market behind a wall it was not behind yesterday. If the drop is concentrated in one geography, compare your region configuration against last week's.
4. Did the conversions fall, or only the measurement?
Check the business numbers before panicking: orders in the shop system, leads in the CRM, calls answered. If revenue held steady while GA4 fell, you have a measurement problem, which is annoying but fixable. If both fell, you have a different conversation ahead of you.
A related case is GA4 falling while Google Ads holds up, which sends people hunting for a fault that is not there. Some of that difference is built into how the two count, and only part of it is yours to fix: why Google Ads and GA4 report different conversion numbers separates the two halves.
5. Modelling stopped
If a meaningful share of your reported conversions were modelled, losing modelling eligibility looks exactly like losing conversions. This happens when advanced consent mode gets downgraded, when the cookieless pings stop, or when traffic drops below the thresholds Google publishes for behavioural modelling. The tell is in the timing: modelled data adjusts over a few days rather than instantly. Once you know that is what happened, the fix is a short chain, in order, with the one verification step most setups miss: restoring the consent signals modelling depends on.
How do you find the cause fast?
Most of it takes one browser session and the network tab. Work through it in this order:
- Leave out the last two days. GA4 can take a day or more to finish processing data, as Google's data freshness table sets out, so a drop confined to the most recent days may simply not have arrived yet.
- Count the orders and leads in the shop system or the CRM for the same days. If they held while GA4 fell, the fault is in the measurement.
- Load the site in a fresh private window, reject the banner, and watch the requests to Google. With advanced Consent Mode you should still see pings, carrying
gcs=G100. With basic Consent Mode nothing is sent until the visitor accepts, and that is expected. - Accept everything, reload, and check again. The requests should now carry
gcs=G111. If they still say denied, or nothing is sent even after accepting, the banner is not passing the choice on. - Line the date of the drop up against the last banner release, container publish and region setting change.
On sites running Velo, the audit log shows every consent state change and every version of the banner, so the question of what changed on Tuesday has an answer you can read rather than reconstruct.
Your next step in website privacy.
Velo puts your consent banner, regional settings and consent records in one place, and passes each visitor's choice to your Google tags through Consent Mode v2.
Common questions
What people ask about this topic.
Why did my GA4 conversions drop overnight?
When the campaigns and the site did not change, the cause is usually the measurement layer: a banner update that changed when consent is granted, a tag that now fires before the consent defaults are set, a region rule that flipped, a key event that was renamed or unmarked, or conversion modelling that stopped because the site no longer meets Google's eligibility thresholds. Check the orders in your shop or CRM first to confirm the sales really fell.
Could the drop just be GA4 processing delay?
For the most recent days, yes. GA4 can take a day or more to finish processing data, so the last day or two often look low and then fill in. Judge the drop on fully processed days only, and treat anything confined to the last two days as unconfirmed.
How do I tell if the cookie banner caused the drop?
Reject the banner in a fresh private window and watch the requests to Google, then accept everything and watch again. After accepting everything, the gcs parameter should read G111. If it still reads G100, or nothing is sent even after accepting, the banner or the tag order is the cause. A drop that starts on the day of a banner release points the same way.
Does a drop in GA4 conversions mean I lost sales?
Not necessarily. GA4 only counts what the tags could measure, so a consent or tag fault can cut the reported number sharply while orders stay flat. If the shop system and the CRM held steady, you have a measurement fault to fix, not a sales problem.
Website privacy, in one place.
Scan your site →