A cookie banner is up. Is your tracking actually respecting it?
Having a cookie banner on screen does not prove your tags are listening to it. If a visitor clicks Reject and your analytics or advertising scripts carry on firing, or if a visitor clicks Accept and your campaign source disappears into Direct traffic, the banner and your tags are not talking to each other properly. - Visitors click Reject on the banner, but marketing or analytics cookies still get written. - Direct traffic jumped and paid channels dropped after a cookie banner was added or updated. - Google Ads remarketing lists or UK/EEA conversion signals stopped populating because Consent Mode v2 parameters are missing. - You need a clear, tested setup across your banner and Google Tag Manager without guesswork. Agentix provides technical cookie consent audits, Consent Mode v2 configuration and tag verification for UK eCommerce, B2B and trade businesses. We connect your consent banner to Google Tag Manager and your tracking scripts, test what happens across every visitor choice, and make sure your measurement follows the rules your policy owner has set.
Why a visible banner is only half the job
In our experience, many cookie banners are fitted onto a website and left alone. Someone installs the script from a Consent Management Platform (CMP), sees the popup appear on the homepage, and assumes the job is done. Underneath, two very different faults can happen: 1. **Tags fire regardless of the visitor's choice.** Because triggers inside Google Tag Manager were never updated to check for consent, analytics and ad pixels fire the moment the page loads, before the visitor has touched the banner, or carry on firing even after they click Reject. 2. **Tags fire too late and ruin your attribution.** When a banner blocks tags until the visitor clicks Accept, the tag fires late or on the second page of the visit. By the time it fires, the original referrer or campaign click has been lost, so GA4 records the visit as Direct traffic and treats page two as the landing page. We check and fix the wiring between your banner and your tags so neither of those happens.
How tag loading order changes what GA4 and Google Ads record
Google's Consent Mode documentation sets out two ways to run Google tags alongside a cookie banner: **Basic** (where tags are blocked completely until consent is granted) and **Advanced** (where tags load before the banner dialog with a default `denied` state, sending cookieless pings until the visitor makes a choice). Here is an illustrative comparison (not a client result) showing how the loading sequence changes what happens across four visitor actions: | Visitor action on your site | Banner blocks tags until choice (Basic or delayed firing) | Default consent set before tags fire (Advanced Consent Mode) | Effect on your GA4 and Google Ads reporting | | -- | -- | -- | -- | | Visitor clicks Accept on Page 1 | Tags fire late after the click. In our experience, late firing can lose the initial referrer. | Tags load on arrival with default `denied`, then update to `granted` on the same page. | Preserves the original campaign source instead of filing the visit under Direct. | | Visitor clicks Reject on Page 1 | No tags load and zero pings are sent to Google. | Tags send cookieless pings without writing cookies or reading device identifiers. | Cookieless pings can contribute to GA4 b
Where cookie consent setups quietly fail
Rather than just checking that a banner appears on your homepage, we test what happens across every choice a visitor can make: | Visitor action on your site | What goes wrong when the setup is broken | What it costs your business | | -- | -- | -- | | First page load (before any click) | Analytics or ad tags fire before the visitor has made a choice, or the default state fires after the container | Your site writes cookies before permission is given, or loses the visitor's landing page and campaign source | | Visitor clicks Accept All | The banner closes, but the consent update never triggers the tags waiting on that page | You lose attribution on the entry page from visitors who were happy to accept cookies | | Visitor clicks Reject All | Hardcoded pixels or custom HTML tags ignore the banner and carry on tracking | Your website does the opposite of what your cookie banner promised the visitor | | Visitor accepts analytics only | Category rules inside Tag Manager are mapped all-or-nothing | You either lose analytics data you were permitted to collect, or fire ad tags the visitor declined | | Visitor changes their choice later | Updating preferences in the footer fails to update th
Technical verification vs legal advice
We are tracking and measurement specialists, not lawyers. Your organisation and its legal or privacy advisers decide your cookie policy, banner wording, default states and lawful basis. Our job is technical: once your team has decided how the banner should work, we configure and test your tags so the website actually does what your banner says it does.
Frequently asked questions
### What is Consent Mode v2, and why does Google Ads need it? Consent Mode v2 added two specific parameters (`ad_user_data` and `ad_personalization`) alongside the original `ad_storage` and `analytics_storage` signals. Google requires these signals for UK and EEA traffic if you want to build remarketing audiences and pass consent states to Google Ads conversion measurement. We check Tag Assistant to verify that all four parameters are set on page load and updated properly when a visitor makes a choice. ### Why did our Direct traffic jump after we installed a cookie banner? In our experience, this happens when the consent banner and your tags fire out of sequence, or when tags are held back until the visitor clicks Accept on a later page. By the time the analytics tag runs, the original campaign referrer is gone, leaving visits that cannot be tied to a source. Ordering the default consent command before your tags load helps preserve the entry source. ### Does setting up Consent Mode guarantee GA4 will fill in our missing data? No. Basic Consent Mode sends no pings at all when cookies are declined, so it gets no behavioural modelling. Advanced Consent Mode sends cookieless pings, b
Speak to us about your consent setup
Whether you need Consent Mode configured properly, want to check if your tags actually respect a Reject click, or need to find out why your traffic sources changed after a banner update, we can help.