Google Analytics sets a cookie before consent
Google Analytics set _ga on https://hollowbrook.app/ 1.25 seconds after the page loaded, before anyone answered the cookie banner. Non-essential cookies need a visitor’s agreement first, and this is one of the first things regulators have checked, because it shows in the network log.
What Peeky saw
In plain words
Google Analytics puts a cookie on your visitors’ browsers before they click “accept cookies”. It’s like a shop signing you up for its loyalty card the moment you walk in, before you’ve said whether you want one. Cookies should load only after a visitor agrees to them. This is usually a setting in your cookie banner.
The fix
- Load Google Analytics from your consent tool’s accept callback instead of on page load.
- If you use Google tags, set consent mode to “denied” by default.
- Re-scan to confirm no request fires before the click.
Ready prompt for your AI coding tool
PeekWell EU-01 (Non-essential trackers firing before consent) observed on hollowbrook.app: Google Analytics sets a cookie before consent. Find where Google Analytics is loaded (look for _ga-setting scripts in the layout template or tag manager). Move the loader behind the consent tool's accept event, so nothing from Google Analytics runs until the visitor accepts. Keep the session cookie as is. Then test: open hollowbrook.app in a private window, do not touch the banner, and confirm in the network tab that no request goes to Google Analytics; accept, and confirm it loads. Do not change unrelated behaviour. Summarise the change and how you tested it.














