Digital Analytics

Is your website really cookie compliant?

Chandrakant Bandha
November 17, 2026
x
min to read

We hate to tell you this but your cookie banner might be lying to you.

You installed a cookie banner. Visitors click Accept or Reject. That's your job done, right? Unfortunately not.

We audit a lot of websites and for most of the websites we audit, the banner looks perfect, but tracking tools are already running before the visitor clicks anything. Some keep running even after a visitor clicks Reject. Your visitors can't see this error but regulators can, and they check for it too. There is some good news: you can conduct a test of your own website within about 10 minutes, using the browser you already have. You can run the test without a developer, without and new software, and at no cost but your own time. And we're here to help you (nag you?) run that test today.

Quick self-test: 5 questions, 30 seconds

Answer honestly. Count how many times you say "Yes" or "I'm not sure".

  1. Do you use Google Analytics, Google Ads, Meta Pixel or any other ad or tracking tool?
  2. Was your cookie banner set up more than a year ago, or by someone who has since left?
  3. Has your marketing team added new tools or pixels since then?
  4. Do you get visitors from Europe, the UK or California?
  5. Are you unsure whether your "Reject" button actually stops tracking?

0-1: You're probably in good shape, but the test below will confirm it.
2-3: There's a real chance something is out of place. Run the test below.
4-5: Your site is very likely leaking data before consent. Run the test now, or ask us to check it for you.

Why this matters: it's not just big tech getting fined

Cookie enforcement has moved past warnings. Here's what happened to some companies when their tracking didn't match their banner:

Who was fined and what went wrong

Google (France, 2025), fined €325 million because consent choices were not presented in a balanced way

Shein (France, 2025), fined €150 million because cookies were placed without consent

Tractor Supply (California, 2025), fined $1.35 million because opt-out link didn't stop trackers; browser privacy signals were ignored

Honda (California), fined $632,500 because the opt-out process was too difficult

Note that Tractor Supply is a farm and ranch retailer, not a tech company. Its investigation started with a single consumer complaint.

The stakes are rising everywhere:

Non-compliance costs money even if a regulator never calls.

The 10-minute cookie compliance test

You only need Google Chrome on a laptop or desktop. Follow along on your own website.

Test 1: What loads before anyone says yes? (3minutes)

This is the big one. For EU and UK visitors, nothing except essential cookies should load until the visitor clicks Accept.

  1. Open Chrome and press Ctrl + Shift + N (Mac: Cmd + Shift + N) to open an Incognito window.
  2. Press F12 to open Developer Tools. Don't worry, you're only going to look.
  3. Type your website address and press Enter. Don't click the cookie banner.
  4. In Developer Tools, click the Application tab, then Cookies on the left, then your website name.
  5. Look at the list of cookie names.

Red flags: if you see any non-essential cookie, tracking started without consent.

What's fine before consent: cookies that keep the website working for the visitor, such as login sessions, the shopping cart, security and bot protection (for example from Cloudflare or Akamai), and the cookie that stores the visitor's consent choice.

Not sure about a cookie that isn't on this list? Use this 3-step check:

  1. Look it up. Search the cookie name on CookieDatabase.org or Cookiepedia, then confirm on the vendor's own website. The vendor's documentation is the strongest proof.
  2. Find what set it. In Developer Tools, press Ctrl + Shift + F (Mac: Cmd + Option + F) and search for the cookie name. If it comes from a file like gtag.js, fbevents.js or a tracking domain, it belongs to a marketing or analytics tool.
  3. Ask "does it break?" question. In the Network tab, right-click the script that sets the cookie and choose Block request URL, then reload. If you can still browse‍
Test 2: Does "Reject" really mean no? (3 minutes)
  1. Close the Incognito window and open a fresh one, so you start clean.
  2. Open Developer Tools again and load your site.
  3. This time, click Reject (or "Necessary only").
  4. Visit three or four more pages. Add something to the cart if you have one.
  5. Check the cookie list again.

Red flags: any of the non-essential cookies appear after you reject them.

Test 3: Is your banner fair? (2 minutes)

Look at your banner with fresh eyes:

  1. Is Reject on the first screen, the same size and visibility as Accept?
  2. Are all optional boxes unticked by default?
  3. Is there a Cookie settings link in the footer so visitors can change their mind?

Red flags: Reject is hidden behind "Settings", greyed out, or missing.

Test 4: Do you respect US opt-outs? (2 minutes)
  1. Scroll to your footer. Is there a "Do Not Sell or Share My Personal Information" or "Your Privacy Choices" link?
  2. Click it. Does it let visitors switch off tracking, or does it just open a contact form?
  3. Bonus check: Open your site in the Brave browser, which automatically sends a "Global Privacy Control" signal saying "don't sell my data". Rerun Test 1. Ad cookies like _fbp and _gcl_au should not appear.

Red flags: no link that only opens a form, or ad cookies that load despite the privacy signal.

Reading your results

Count your red flags across the four tests. Understand what those red flags mean and what you should do to correct the issues.

0 (All clear) Nothing to worry about right now. Keep it that way with a quick check every few months

1–2 (Partially compliant, A few gaps) Fix the specific tools that failed (steps below), then re-test

3 or more (High risk: data is leaking before or despite consent) Act this week. Several failures usually point to a setup problem, not a one-off

All clear? Nothing to worry about

Good news: your site passed the checks that regulators look at first. You don't need to change anything today.

To stay compliant:

  • Re-run this test every three months, and whenever your team adds a new tool, pixel or campaign. That's when most sites slip.
  • Keep your cookie policy in sync with the cookies you see in Test 1. If a tool is removed, take it out of the policy too.
  • Check new pages, such as landing pages and checkout changes. Tags are often added there without anyone checking the banner.
1-2 red flags? Here's how to fix them

These are usually quick to fix once you know where the tag lives:

  1. Identify the tool. Use the red-flag table above to match each cookie to its tool, such as _fbp to the Meta Pixel.
  2. Find where it's installed. Check Google Tag Manager first. If it isn't there, look in your website platform's settings, theme or plugins. Tags added outside the tag manager often bypass the banner.
  3. Put it behind consent. In Google Tag Manager, set the tag to fire only after the right consent category is granted. In your consent platform, make sure the tool is in the correct category, such as Marketing, not Necessary.
  4. Turn on Google Consent Mode v2 if you use Google Analytics or Google Ads, so Google tags respect the visitor's choice.
  5. Re-run the test in a fresh Incognito window to confirm the fix.

Don't just delete the tags. Removing your analytics or ad pixels fixes the compliance issue but breaks your marketing reporting. The right fix keeps your data flowing and respects consent.

‍3 or more red flags? Get it fixed properly

Multiple failures usually mean the consent setup itself isn't connected to your tags correctly. Patching one tag at a time rarely solves it.

  • Prioritise advertising pixels (Meta, Google Ads, Microsoft, TikTok) that fire before consent or after Reject. These carry the highest risk.
  • Note down what you found, including the cookie names and the pages, so whoever fixes it can work quickly.
  • Get an expert to review the whole setup, including tag manager, consent platform and any hard-coded tracking, so it's fixed once and stays fixed.

‍What a 10-minute test can't catch

These tests catch the most common problems. A professional audit goes deeper into the issues that hide below the surface:

  • Hard-coded tags. Tracking added directly in your website platform, theme or plugins, outside Google Tag Manager, often ignores the cookie banner completely. It may only load on certain pages, such as checkout.
  • Google Consent Mode v2 timing. If the "denied" default arrives a split second after your tags load, data leaks, and you won't see it with the cookie list alone.
  • Network requests without cookies. Some tools send data without setting cookies, so they pass Test 1 but still break the rules.
  • Duplicate and legacy tracking. Old pixels from past campaigns, or the same analytics installed twice.
  • Policy and record gaps. A cookie policy that doesn't match reality, missing consent logs, or outdated vendor contracts.
  • Multi-region logic. The right banner for EU visitors, the right opt-out for Californians, and Global Privacy Control handled automatically.

In our experience, sites that pass the quick test still have at least one of these issues more often than not.

Sources:

You might be interested

Digital Strategy
Google Data Manager: How to Build Data Strength for AI-Powered Media
Google Data Manager: How to Build Data Strength for AI-Powered Media
E-Commerce
Bringing in-store sales into Google Ads for Rapha
Bringing in-store sales into Google Ads for Rapha
Our Team
Team Spotlight - Meet Aylen, Solutions Architect
Team Spotlight - Meet Aylen, Solutions ArchitectOur Team