Your cookie banner is probably decoration.

Here is a test that takes two minutes. Open your own website in a private window. When the cookie banner appears, don’t click anything. Open the browser’s network panel and look at what has already loaded.

On most sites I check, the analytics tag has fired, the ad pixels have fired, and the visitor hasn’t chosen anything yet. Then you click “No thanks” and watch again. Often nothing changes. The banner goes away and the tags carry on as before.

That is a banner doing the job of a painting. It looks like consent. It isn’t.

The worst of both

A business in that position has paid for a consent tool, annoyed every visitor with a pop-up, and still collects data it has told people it won’t. It also has no idea which of its numbers were gathered with permission and which weren’t.

I don’t give legal advice, and what you are obliged to do is a question for your legal adviser. My point is narrower. If the banner says one thing and the site does another, you have a problem whatever the rules are where you trade. And visitors from Europe and the UK bring their rules with them.

Why it happens

Because the banner and the tags are usually set up by different people, at different times, and nobody is asked to check that one controls the other. Installing a consent tool is an afternoon’s work. Making every tag wait for it is the real job, and it is the part that gets left.

The off-the-shelf setting rarely fits either. The same rules for every visitor is simple, and wrong for a business that sells in more than one region.

Three things have to hold together:

  1. The banner records a real choice. Clear categories, and a “no” that is as easy to give as a “yes”.
  2. Every tag is held to that choice. Google Consent Mode and Tag Manager do this for Google’s tags. The other platforms’ tags need the same treatment, one by one.
  3. The choice travels with the visitor. When a form goes to your CRM, or a conversion is sent to an ad platform from your server, it should carry the same permission the browser tags had. This is the part most setups miss.

Then there is region. A custom setup can ask where the visitor is and behave accordingly: ask first where the rules expect it, and show a plain notice where they don’t. This site does that. Visitors in Australia see a notice. Everyone else is asked, and nothing loads unless they agree.

It costs less data than you fear

The usual objection is that proper consent will wreck the numbers. Some data is lost when people say no. In my experience the bigger losses come from the opposite problem: tags blocked for the wrong reason, or misfiring, because nobody set the rules deliberately.

Done well, Consent Mode lets Google model part of what it can’t observe, and server-side conversions can still be sent where the visitor agreed to advertising.

What I’d do

Run the two-minute test today. If tags fire before the choice, or ignore it, you know where you stand.

Then have it fixed once: an audit of what fires when, a banner with rules by region, every tag and form held to the choice, and a tag-by-tag record you can hand to whoever asks. That record is the difference between saying you respect consent and being able to show it.

Sound familiar?

Tell me what’s going on. I’ll reply with questions or a scoped proposal.