igors@portfolio

They clicked "reject", but the cookies were already set

Share

Press F12 before you click the banner: if _ga is already in the cookie list, the "reject" button does nothing. The visitor pressed it and believed it changed something. But the analytics and advertising cookies were set the moment the page opened, while the banner was still on screen.

It's a "No filming" sign on the door while the camera under the ceiling is already recording. The visitor sees the sign. They don't see the camera.

The owner may well be sure the matter is closed: there is a banner, there are buttons, and a quick look finds no fault. What he doesn't see is what F12 shows. The banner and the analytics were set up by different people at different times, and nobody checked that one controls the other. A banner that doesn't control the cookies is just a sign.

Seven sites in ten set cookies before the choice

I opened the homepages of sites where analytics code had already been found, and looked at which cookies were set by themselves, without a single click.

All the numbers as a table
What I sawSitesOfShare
Tracking cookies before the visitor's choice9,27512,89671.9%
Banner on screen, but cookies set before a choice1,6672,54465.5%
Banner present, nothing tracked before a choice87712,8966.8%

Look at the second row on its own: even where a banner was on screen, in two cases out of three it held nothing back. In my data, having a banner and having one that works are barely connected.

The law is about the moment of writing, not how the banner looks

Article 5(3) of Directive 2002/58/EC allows information to be stored on a user's device, or read from it, only if the user has consented after clear and complete information. The exception is what is strictly necessary for a service the user asked for, such as the contents of a shopping cart. In Latvia this is carried over by Article 7.1 of the Informācijas sabiedrības pakalpojumu likums (the Law on Information Society Services).

On 8 May 2026 the Datu valsts inspekcija (DVI, the Latvian Data State Inspectorate) named, among the most common problems, cookies set before a choice and non-essential cookies still set after "reject". The same material includes the sentence: "Uzstādīts nefunkcionējošs baneris vēl nenozīmē atbilstību prasībām", which means that installing a banner that doesn't work is not yet compliance. It also reminds site owners that "accept" and "reject" must be shown as equals, and that scrolling on or closing the banner is not consent.

There has been a public case, too. After a preventive check of cookie use, the DVI fined a Latvian company 20,000 euros (decision of 26 January 2023, upheld on 7 March 2023). The fine was for three things: the site gave no clear information on which cookies it used and why; the cookie policy did not say how to accept, refuse or withdraw consent; and for more than nine months the company did not answer the inspectorate or do what it required. Cookies created before consent appear in the decision too, but as the company's own admission.

What to do

  1. Check it yourself, five minutes. Open your site in a private window. Before you click anything, open the list of cookies: in Chrome or Edge, press F12 → Application → Cookies. If _ga, _fbp or _gcl_au are already there, they were set before any choice. These belong to Google Analytics, the Meta pixel and Google Ads. Now click "reject" and reload the page: if the same cookies are still there, the banner ignores the choice.
  2. Look at the banner through a visitor's eyes. "Reject" should be as visible on the first screen as "accept", not hidden behind "settings". Then open any form: contact, enquiry, newsletter. Next to it there should be a short line saying who receives the data and why, with a link to the privacy policy (Article 13(1) of the GDPR).
  3. Give whoever installed the banner these words. "No analytics or advertising code may load before the visitor's choice. 'Reject' must be as easy as 'accept'." Attach the cookies you found and the moment they appeared, so they don't have to guess.
  4. Ask where exactly the analytics is switched on. If the counters are connected through Google Tag Manager or a consent plugin, every tag has a firing condition. It should be "after the visitor's consent", not "on every page". This is a setting, not a rebuild of the site, and I would allow an hour for it.
  5. Repeat step 1 after every change. A new plugin, a new counter, a theme update: any of them can switch analytics back on before the choice. Check once a quarter anyway, even if you changed nothing.

What it buys you

The visitor's choice starts to mean something: they press "reject" and the camera really is off. For you it means the banner does what it promises, not what the inspectorate fined for in the decision above. I don't promise it will change your sales; I have no data on that. But a sign on the door that tells the truth costs the same as one that lies.

How I counted

On 21 September 2026 I opened the homepages of 12,896 Latvian company websites where analytics code had been found: once, with no clicks, and I did not press "accept" or "reject". "Banner not found" only means my tool did not recognise it. I did not see banners that load late, or cookies on other pages. The EU Digital Omnibus (Commission proposal COM(2025) 837, 19 November 2025) also touches the cookie rules, but in October 2026 it is a proposal under discussion, not law; this article describes the rules in force. The rest: how I checked 27,591 websites.

Sources

If you would like me to open your site with F12 and name the cookies set before the choice, get in touch.

Share
← All articles