The latest articles on DEV Community by Sean Q (@sean_gdprchecker). https://dev.to/sean_gdprchecker https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3999232%2Fd92ab3b0-d582-4204-beea-0398c59b9d18.png https://dev.to/sean_gdprchecker en Sean Q Tue, 23 Jun 2026 17:55:14 +0000 https://dev.to/sean_gdprchecker/how-to-check-if-google-analytics-fires-before-cookie-consent-4ig5 https://dev.to/sean_gdprchecker/how-to-check-if-google-analytics-fires-before-cookie-consent-4ig5 <p>Many websites have a cookie banner, but that does not always mean tracking is blocked before consent.</p> <p>One common issue is that Google Analytics, GA4, Google Tag Manager, Meta Pixel, or other marketing scripts load as soon as the page opens. The banner appears visually, but the tracking has already happened.</p> <p>That is a problem because consent is not just a design element. The technical behavior of the website matters.</p> <h2> What you are checking </h2> <p>You want to know whether analytics or marketing requests happen before the visitor clicks “Accept”.</p> <p>Common signals include requests to:</p> <ul> <li>google-analytics.com</li> <li>googletagmanager.com</li> <li>doubleclick.net</li> <li>facebook.com/tr</li> <li>connect.facebook.net</li> <li>hotjar.com</li> <li>clarity.ms</li> </ul> <h2> Manual test </h2> <p>Open the website in a private browser window.</p> <p>Do not click the cookie banner.</p> <p>Open DevTools and go to the Network tab.</p> <p>Reload the page.</p> <p>Search for requests such as:</p> <ul> <li>collect</li> <li>gtag</li> <li>google-analytics</li> <li>googletagmanager</li> <li>doubleclick</li> <li>facebook</li> <li>fbevents</li> <li>hotjar</li> <li>clarity</li> </ul> <p>If those requests appear before consent, the website may be tracking before the user has agreed.</p> <h2> Why this happens </h2> <p>This usually happens because analytics or marketing scripts are installed outside the consent manager.</p> <p>Common causes:</p> <ul> <li>GA4 is installed directly in the page</li> <li>Google Tag Manager fires tags before consent checks</li> <li>Meta Pixel is not gated behind the CMP</li> <li>Chat widgets or heatmap tools load immediately</li> <li>The cookie banner records consent, but does not block scripts</li> </ul> <h2> What should happen instead </h2> <p>Before consent, non-essential tracking should not fire.</p> <p>After consent, analytics and marketing tags can load according to the consent choices the user made.</p> <p>For Google tools, this often means configuring Consent Mode correctly and making sure tags respect consent states.</p> <h2> A cookie banner is not enough </h2> <p>A banner can look compliant while the website still sends tracking requests too early.</p> <p>That is why it is worth testing the actual browser behavior, not just checking whether a banner appears.</p> <h2> Automated scanning </h2> <p>I’m building GDPRChecker, a free GDPR scanner for websites that checks cookies, trackers, cookie banner signals, and pre-consent tracking behavior.</p> <p>You can try it here:</p> <p><a href="https://www.gdprchecker.online/scanner" rel="noopener noreferrer">https://www.gdprchecker.online/scanner</a></p> <p>It is not legal advice, but it can help identify technical consent issues that are easy to miss.</p> privacy webdev analytics cookie