Customer Impact

Data & Tracking

Check cookies on your website: does it set cookies before consent?

Copy for AI

You can check cookies on your website in five minutes, with Chrome alone.

Open your site in a private window and don’t click the cookie banner. Then look in the developer tools at which cookies are already set and which trackers already send data.

The verdict: if _ga, _fbp or _gcl_au show up before a click, or hits leave for Google, Meta or LinkedIn, your site isn’t waiting for consent.

Very common. On 6 October 2026 we loaded 37 Belgian websites in a real Chrome browser, without clicking anything.

Here’s what we found:

COOKIE SCAN, 6 OCTOBER 2026 Most sites with tracking don’t wait Sites loaded 37 Sites using tracking 20 Tracking before a choice 14 Real Chrome, no clicks. Cookies set or non-denied hits sent before the visitor chose.

What went wrong on those sites

20 of the 37 sites used tracking.

On 14 of them, tracking cookies were already set or non-denied hits were sent before the visitor had made a choice.

The details:

  • 4 sites sent Google Analytics 4 hits without Consent Mode
  • 2 sites granted consent by default
  • 10 sites got it right: everything denied until the visitor chooses

Prefer it automated? Our cookie scanner runs it for you.

Below, you’ll run the same test yourself.

A banner is only the question.

What counts is what happens technically while that question is still open.

What the Belgian authority requires

The Belgian Data Protection Authority (page in Dutch) is clear.

No cookie that isn’t strictly necessary may be placed or read until the user has given consent.

Analytics cookies are included. According to the authority, they’re not needed to deliver the service the visitor asked for.

Why you can’t see it by looking

A banner can appear nicely while Google Analytics, the Meta pixel and the LinkedIn Insight Tag already fire in the background.

That doesn’t follow the rule. And you can’t spot it by simply looking at your site.

Hence this test.

How to check cookies on your website in 5 minutes

All you need is Google Chrome. Other browsers work too, but the menus have different names.

Step 1: Open a private window

Press Ctrl+Shift+N (on Mac, Cmd+Shift+N).

You start without earlier cookies or saved choices. That’s the state a first-time visitor is in.

Step 2: Open the developer tools first

Press F12 and choose the Network tab before you load the site.

Tick “Preserve log”, so you miss nothing on a redirect.

Step 3: Load your homepage and click nothing

Not the banner, not the page.

Wait ten seconds or so and scroll down. Some tags only fire on scroll.

Step 4: Look at the cookies

Go to the Application tab, open Cookies on the left and click your domain.

Chrome’s DevTools cookie documentation lists the columns you’ll see, such as Name, Value, Domain and Expires.

Note what’s there. Check the other domains in that list too.

This is the view to look at:

Step 5: Filter the network traffic

Type these search terms, one after another, into the Network filter:

  • collect (Google Analytics 4 and Google Ads)
  • facebook.com/tr (the Meta pixel)
  • px.ads.linkedin (the LinkedIn Insight Tag)
  • analytics.tiktok, clarity and hotjar

Every line that appears is a tracker already sending data.

Click a g/collect request (Google Analytics 4) or a Google Ads request.

Then look for the gcs parameter in the URL. More on that below.

Step 7: Repeat after “Reject”

Open a new private window and click “Reject all” this time.

Then check whether marketing trackers still fire afterwards.

Using Google Tag Manager?

If you use Google Tag Manager, you can see the same sequence in Tag Assistant.

Select the first Consent event. In the Consent tab, check that the four Google signals are set to denied before any tag fires.

How do you read the gcs parameter?

Google sends the consent state along with every hit.

According to Google’s consent mode documentation, the gcs parameter transmits the visitor’s choice for ad_storage and analytics_storage.

In practice we see three patterns:

  • gcs=G100: both signals are denied. Consent Mode works and is waiting for a choice. This is what you want to see before the click.
  • gcs=G111: both signals are granted. If you see this before anyone clicked “Accept”, your site grants consent by default.
  • No gcs: Consent Mode isn’t set up. Google doesn’t know whether there’s consent, and the tag simply fires.

Other combinations, such as G110 or G101, mean one of the two signals is granted.

That shouldn’t happen before a choice either.

What you see, what it means and what to do

Use this table to translate each finding into an action:

What you see before a clickWhat it meansWhat to do
Only cookies from your consent tool or sessionThis is how it should beRepeat the test after every major change
_ga or _ga_XXXXGoogle Analytics sets cookies without consentSet the default to denied and tie GA4 to consent
_fbp, _gcl_au, _ttp, li_fat_idAd pixels (Meta, Google Ads, TikTok, LinkedIn) are already onFire pixels only after marketing consent
g/collect with gcs=G100Consent Mode works, cookieless pingsFine, but check the update after a click
g/collect with gcs=G111Consent is granted by defaultSet the default to denied in your consent tool or GTM
g/collect without gcsNo Consent ModeInstall Consent Mode v2
Hits to facebook.com/tr or px.ads.linkedin.comMarketing data leaves without a choicePut the tag behind the right consent category

Example: say you find _fbp before a click.

That’s the Meta pixel firing without consent.

What do the rules say in Belgium and the Netherlands?

Both regulators want prior consent. The Dutch one already checks sites with software.

Belgium

The Data Protection Authority requires prior consent for every cookie that isn’t strictly necessary, analytics cookies included.

Three more rules from the same page:

  • Pre-ticked boxes don’t give valid consent
  • Withdrawing must be as easy as giving
  • A cookie wall that blocks people who refuse doesn’t comply with the GDPR

How your banner meets these rules is covered in cookie banner rules in Belgium. For the analytics side, see Google Analytics and the GDPR.

The Netherlands

The Dutch Autoriteit Persoonsgegevens checks websites with its own software.

In April 2025 it sent its first 50 warning letters (in Dutch). The authority aims at 500 sites a year.

Among the targets:

  • sites that placed cookies before the visitor agreed
  • sites where refusing took more clicks than accepting
  • sites with pre-ticked boxes

What a failed test means

If your test shows trackers firing before a click, your site doesn’t follow the Belgian authority’s guidance.

That’s a finding, not a verdict. It’s almost always a technical error that’s quick to fix.

The five causes we see most often

Almost every failed test traces back to one of these:

1. A hardcoded tag in the theme

The Google tag or the Meta pixel sits directly in the <head>, next to the version in GTM.

The consent tool controls the GTM version. The hardcoded one always fires.

2. A plugin that loads its own pixels

WordPress and webshop plugins for analytics, chat or reviews often load their own trackers.

They do it outside your consent tool.

3. A tracker in the wrong category

Your consent tool’s scan puts an unknown cookie under “necessary” or “unclassified”.

And nobody looks at it.

In GTM it sits on All Pages instead of Consent Initialization.

So the first hit leaves without a consent state.

5. Defaults set to granted

Someone set the default consent to granted “so we don’t lose data”.

That gives you no usable data, only a bigger risk.

How to fix it

The fix always follows the same line:

  • One place for all tags. Remove hardcoded scripts from the theme and manage everything through Google Tag Manager.
  • A consent tool installed correctly. For example Cookiebot through the official template, on Consent Initialization, with all four signals denied by default.
  • Consent Mode v2 for Google Ads. Without the four signals, Google treats your EEA traffic as not permitted. See how in Consent Mode v2.
  • Non-Google tags tied to consent. Meta, LinkedIn, TikTok and Hotjar only fire after the right consent.
  • A new test. Repeat the five-minute test after every theme update, new plugin or new tag.

The four signals are ad_storage, analytics_storage, ad_user_data and ad_personalization.

Still picking one? We compare the main options in Cookiebot vs Usercentrics vs Complianz.

Google’s documentation describes two modes.

In basic mode, Google tags stay blocked until the visitor interacts with the banner. In advanced mode, tags load with consent denied and send cookieless pings.

Rule of thumb: advanced mode keeps more modelled data, but you still need denied defaults. The impact on campaigns is in Consent Mode for Google Ads.

A step further: server-side tagging

If you want to depend less on what the browser does, server-side tagging is a next step.

It doesn’t replace consent. It gives you more control over your data.

Rather not do it yourself?

You can run the same check automatically with our cookie scanner.

You’ll see which cookies and trackers your site sets before a click, and which consent state Google receives.

When to bring in help

Want to be sure the whole chain is right, from consent to GA4, Google Ads and Meta? Start with a tracking audit.

Would you rather have it set up properly straight away? Our tracking specialist installs your consent tool, Consent Mode v2 and the tests. Price on request.

Frequently asked questions

How do I check which cookies my website sets?

Open your site in a Chrome private window, press F12 and look in the Application tab under Cookies, without clicking the banner. Anything there apart from your consent tool and your session cookies deserves a second look.

Can Google Analytics set cookies without consent?

According to the Belgian authority, no: analytics cookies aren’t strictly necessary and therefore need prior consent. With Consent Mode in advanced mode, Google can send cookieless pings while consent is set to denied.

What does gcs=G111 before a click mean?

That your site tells Google by default that the visitor consented to ad and analytics storage, while they haven’t chosen anything yet. Set the defaults to denied in your consent tool or GTM.

Is my site fine if the banner shows “Reject”?

Not necessarily. Also test what happens after “Reject”: if hits still go to Meta, LinkedIn or TikTok, your setup doesn’t respect the choice.

How often should I check the cookies on my website?

After every change to your theme, plugins or tags, and at least every quarter. New tags are often added by marketing or an external partner, outside the consent settings.

What to do today

Run the five-minute test on your homepage and one landing page.

Found a tracker before consent? Send us the result and we’ll tell you which of the five causes it is.

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.