Tracking Before Consent: UK Website Checks
A cookie banner is only useful if it controls what happens behind the scenes. Many websites display a banner but still allow analytics, advertising pixels or marketing scripts to load before a visitor has accepted non-essential cookies.
This guide explains how to check whether Google Analytics, Google Tag Manager, Google Ads, Meta Pixel, marketing scripts, WordPress plugins and Shopify apps are loading before consent.
This is practical website guidance only. It is not legal advice or formal compliance certification.
What Does Tracking Before Consent Mean?
Tracking before consent means that optional analytics, advertising or marketing technologies activate before the visitor has made a consent choice. This can happen even when a cookie banner is visible.
Analytics Tags
Google Analytics, GA4 or similar tools may start measuring page views before analytics consent is accepted.
Advertising Pixels
Meta Pixel, Google Ads, TikTok Pixel or LinkedIn Insight Tag may fire before marketing consent is accepted.
Plugin and App Scripts
WordPress plugins, Shopify apps, embedded widgets and custom scripts can bypass banner controls if not configured properly.
Why Tracking Before Consent Matters
Website owners often assume that adding a cookie banner solves the issue. In reality, the banner must be connected to the tracking tools it is supposed to control.
If Google Analytics, Meta Pixel, Google Ads, remarketing tags or other scripts load before a visitor has made a choice, the website may not be respecting the consent message shown on the banner.
The main check is simple: what happens before consent, after rejection and after acceptance?
Common Sources of Pre-Consent Tracking
Tracking can be added from several places. A banner may control one source but miss another.
Google Tag Manager
GTM can fire analytics, advertising and conversion tags before consent if triggers, consent settings or exceptions are not configured properly.
WordPress Plugins
SEO, analytics, form, chat, booking, ecommerce and header-script plugins may add tracking outside the cookie banner’s control.
Shopify Apps
Shopify apps, customer events, pixels, sales channels and checkout tracking can add scripts that need to be tested against consent choices.
Tracking Before Consent Checklist
Use this checklist to review whether optional tracking activates before the visitor has made a choice.
- Does the cookie banner appear before optional scripts load?
- Does Google Analytics load before consent?
- Does Google Tag Manager fire tags before consent?
- Does Meta Pixel fire before marketing consent?
- Do Google Ads or conversion tags load before consent?
- Do embedded videos, maps or widgets set cookies early?
- Do WordPress plugins or Shopify apps add hidden scripts?
- Does rejection block analytics and marketing tags?
- Can visitors change their consent later?
- Are analytics, marketing and necessary cookies separated?
- Is Consent Mode configured where Google tags are used?
- Does the cookie policy match the tools actually used?
- Has the site been tested on mobile and desktop?
- Has tracking been retested after plugin, app or theme changes?
How to Test Tracking Before Consent
Testing should cover three stages: before consent, after rejection and after acceptance.
Before Consent
Open the site in a private browser session and check whether analytics cookies, pixels, requests or scripts appear before any choice is made.
After Rejection
Reject non-essential cookies and check whether analytics, advertising and marketing tags remain blocked or receive denied consent signals.
After Acceptance
Accept analytics or marketing cookies and confirm that only the relevant tags activate after that choice has been made.
Google Consent Mode and Pre-Consent Tracking
Google Consent Mode can help Google tags respond to a visitor’s consent choices, but it does not replace a cookie banner. It needs to work with the website’s consent banner or consent management platform.
- analytics_storage: analytics-related storage.
- ad_storage: advertising-related storage.
- ad_user_data: advertising user data consent where relevant.
- ad_personalization: personalised advertising consent where relevant.
Where Google tags are used, review whether default consent states are set before tags fire and whether consent states update correctly after acceptance or rejection.
Consent Mode should be tested alongside the cookie banner, not assumed to work just because Google tags are installed.
Common Pre-Consent Tracking Mistakes
These issues are common on websites using tag managers, analytics, pixels, plugins, apps and custom scripts.
Banner Visible, Tags Still Active
The website shows a cookie banner, but analytics or advertising scripts are already active before the visitor chooses.
Reject Does Not Stop Scripts
The visitor rejects cookies, but analytics, advertising pixels or marketing tags continue to load in the background.
Policy Does Not Match Tracking
The cookie policy names only basic cookies while the site uses analytics, pixels, plugins, apps or third-party marketing tools.
Official Guidance and Practical Disclaimer
The ICO explains that consent must be freely given, specific and informed, and must involve some form of unambiguous positive action. The ICO also explains that websites should provide clear information about cookies and similar technologies.
Google explains that Consent Mode lets websites communicate consent status to Google tags, but it does not provide a consent banner or widget by itself.
CookieBanner.co.uk provides practical website observations and general educational guidance. We do not provide legal advice, legal representation or formal compliance certification.
Tracking Before Consent FAQs
What is tracking before consent?
Tracking before consent is when optional analytics, advertising pixels or marketing scripts activate before the visitor has accepted the relevant cookie category.
Can a website have a banner but still track before consent?
Yes. A banner may be visible, but scripts can still load if the banner is not connected to Google Tag Manager, plugins, pixels, apps or custom code.
Does Google Analytics need checking before consent?
Yes. Google Analytics should be reviewed to confirm whether it is using cookies or identifiers before the visitor has accepted analytics cookies.
Does Meta Pixel need checking before consent?
Yes. Meta Pixel is usually a marketing or advertising technology and should be checked to see whether it fires before the visitor has accepted the relevant consent category.
How do I check if scripts load before consent?
Use a private browser window, developer tools, tag debugging tools or a specialist review to check what loads before consent, after rejection and after acceptance.
Related Cookie Banner Guides
Continue with practical guidance on consent buttons, cookie banner examples, Google Analytics, Meta Pixel and platform-specific tracking checks.
Check Whether Your Website Tracks Before Consent
Download the free checklist or request a practical review of your cookie banner, Google tags, analytics setup, advertising pixels, plugins, apps and tracking behaviour.
This is practical website guidance only and is not legal advice or formal compliance certification.