How to check if Google Analytics runs before consent
Find out whether Google Analytics runs before consent on your site, using two free browser tools, and what to fix if it does.
By the Savira teamPublished Last reviewed 6 min read
Your cookie banner promises that Google Analytics waits until a visitor says yes. To check if Google Analytics runs before consent, open your site in a private window, watch the browser’s network traffic before you touch the banner, and look for GA4 requests and cookies. If either shows up early, the banner isn’t doing its job.
Why check if Google Analytics runs before consent?
Because a banner only means something if the site actually listens to it. Your banner, your privacy policy and your website should all tell the same story, and people notice when they don’t. In the Office of the Australian Information Commissioner’s (OAIC) Australian Community Attitudes to Privacy Survey 2026, 65% of people said sharing their information rarely or never feels like a real choice. A banner that asks but doesn’t listen is exactly that.
The banner looking right on screen proves nothing. The test happens in the browser, where you can see what your site really sends. If you’d like a list of every tracker on your site first, run the free website privacy scanner, then use the steps below to check Google Analytics in detail. Not sure you need a banner at all? Start with do you need a cookie banner in Australia.
What you need before you start
You need Google Chrome, your website’s address and the ability to click through your own banner. That’s it for the main test. For the second test you’ll also want Google’s free Tag Assistant Companion extension.
Test the live site as a visitor would see it. Some analytics plugins hide tracking from logged-in admins, which is one reason the steps below use a private window.
How to check GA4 in Chrome DevTools
The DevTools test shows every request your site sends, so you can see whether GA4 fires before anyone clicks your banner.
Open a new Incognito window in Chrome. You start with no saved cookies or consent choices.
Open DevTools: press F12 or Ctrl+Shift+I on Windows, or Cmd+Option+I on a Mac. Click the Network tab.
Tick Preserve log, so requests stay listed when the page reloads.
In the filter box, type collect. GA4 sends its data to an address ending in /g/collect, usually on google-analytics.com.
With DevTools still open, enter your website address and load the page. Don’t click anything on the banner.
Let the page finish loading and scroll a little. Check the Network list for any collect requests.
Click the Application tab, open Cookies under Storage and select your domain. Look for cookies starting with _ga.
Note what you see, then test the other two choices:
Reject. Click your banner’s reject or decline option, reload the page, and check the Network tab and cookies again.
Accept. Close the window, open a fresh Incognito window, repeat steps 2 to 5, then click Accept. Collect requests and _ga cookies should now appear.
What does a pass look like?
A pass means GA4 stores nothing and sends no normal tracking data until a visitor clicks Accept. To see the consent value on a collect request, click it and open the Payload tab, then look for gcs.
No collect requests and no _ga cookies before a choice. Pass. Analytics is waiting.
Collect requests showing gcs=G100, but no _ga cookies. This is Google Consent Mode in its advanced setting. GA4 loads straight away but sends cookieless pings marked as consent denied. That’s a decision for your business rather than a fault, so make sure your banner and privacy policy describe it honestly.
Collect requests with no gcs value, or with G101 or G111, before any click. Fail. GA4 is behaving as if consent was already given.
_ga cookies set before any click. Fail, whatever the Network list shows.
Collect requests or new _ga cookies after Reject. Fail. The reject choice isn’t being honoured.
Nothing after Accept. Your banner is blocking too much, or GA4 isn’t installed properly. Not a privacy problem, but your reports will be empty.
How to check consent with Google Tag Assistant
Tag Assistant is Google’s free debugging tool, and it shows which consent state your Google tags are reading. It’s a useful second opinion, especially if your site uses Google Tag Manager.
Install the Tag Assistant Companion extension in Chrome.
Go to tagassistant.google.com, add your domain and enter your website address. Your site opens in a new tab, connected to Tag Assistant.
Don’t touch the banner yet. In Tag Assistant, select your GA4 tag at the top and open the Consent tab.
Check the On-page Default column. analytics_storage should show as denied.
On your site, click Accept. Back in Tag Assistant, check the On-page Update column. analytics_storage should now show as granted.
In the summary, open the Tags tab to see which tags fired and which were held back.
If the Consent tab is empty, Google Consent Mode isn’t set up on the page. That isn’t automatically a fail: if your banner blocks GA4 completely until someone accepts, the DevTools test is the one that tells you whether it works. Tag Assistant also can’t tell basic and advanced consent mode apart, so rely on the Network tab for that.
What to do if GA4 runs before consent
If GA4 fires early, the usual cause is that it’s being loaded from somewhere your banner doesn’t control. Work through these in order.
Find every place GA4 is installed
Check your site’s header code, theme settings, analytics plugins, Google Tag Manager and your page builder. Plenty of sites have GA4 installed twice, with only one copy connected to the banner. Find your measurement ID (it starts with G-) in GA4 under Admin, then Data streams, and search your page source for it.
Load GA4 through your banner, not around it
Remove the extra copies so GA4 loads from one place your banner manages. If you use Google Tag Manager, make sure the default consent state is set before any Google tag fires, and that your GA4 tag needs analytics consent to run. If your site runs on WordPress, start with our WordPress cookie consent plugin page.
Decide how consent mode should behave
Choose between GA4 waiting for a yes, or sending cookieless pings before a choice, and make that choice on purpose. Then check your policy covers it, using our guide to privacy policy requirements in Australia.
Clear caches and test again
Caching plugins and content delivery networks can keep serving old pages after a fix. Clear them, then rerun the DevTools test in a fresh Incognito window for all three choices: no click, Reject and Accept.
Check your other trackers too
GA4 is rarely the only script on a site. Ads, social and video tags can fire early in the same way, so read our guide to tracking pixels and your privacy obligations. If you run a clinic or practice website, also read tracking pixels on health websites.
Google’s own steps for the Tag Assistant test are in Troubleshoot consent mode with Tag Assistant on Google for Developers.
This is general information, not legal advice. Every business handles information a bit differently, so if you’re not sure how this applies to yours, it’s worth checking with a lawyer or privacy adviser.
Is it a problem if Google Analytics loads before someone clicks Accept?
What does gcs=G100 mean in a Google Analytics request?
What does gcs=G100 mean in a Google Analytics request?
It means Google Consent Mode is running and both analytics and advertising consent are currently denied. You usually see it in advanced consent mode, where GA4 sends cookieless pings before a visitor chooses. G101 means analytics consent is granted, G111 means both are granted, and no gcs value means consent mode isn’t set up.
Do I need Tag Assistant or is Chrome DevTools enough?
Chrome DevTools is enough for the core test, because it shows exactly what your site sends and which cookies it sets. Tag Assistant adds a view of the consent state your Google tags are reading, which helps if you use Google Tag Manager. It can’t tell basic and advanced consent mode apart, so keep DevTools as your main check.
Why does Google Analytics still run after I click Reject?
Usually because GA4 is installed somewhere your banner doesn’t control, such as header code, a theme setting, an analytics plugin or a second Tag Manager container. Find every copy of your measurement ID, remove the extras and load GA4 from one place your banner manages. Then clear any caches and test again in a fresh private window.
How often should I test my cookie banner and Google Analytics?
Test after any change that touches your site’s scripts, such as a new plugin, a theme update, a Tag Manager change or a new marketing tool. Beyond that, a check every few months is a good habit, because updates can quietly reinstall tracking code. Note the date you tested so you know when it was last checked.