Free tool - no signup

Consent Mode v2 checker

Enter your site URL. We load it before any click and after Reject, and show you which requests were sent in each case and which consent signals your Google tags carried.

We open your site in a real browser. Takes about 40 seconds.

What this checker does and does not do. This is a technical check of what your site sends. It is not legal advice and it does not certify compliance.

What we check for consent

Each check describes what your site sent in one clean browser session, before any click and after Reject. 6 checks.

Consent

  • Tracking tags fire and no consent banner was detected
  • Tags fire before the visitor interacts with the banner
  • Tracking requests are still sent after the visitor clicks Reject
  • Google tags run without Consent Mode v2 signals
  • Consent Mode is present but ad_user_data or ad_personalization is missing
  • A TCF banner is present but Meta or TikTok tags ignore its decision

See what you get

This is a sample for a fictional store. Scan your own site above.

Sample report

northwind-outdoor.example

6 things to fix today, 2 to improve, 12 already working.

Fix today (6)

Critical and high impact issues. Quick wins first.

  • Why it matters

    Every event Meta, Google and TikTok receive from your store today goes through the visitor's browser. Ad blockers, Safari's tracking prevention, consent banners and slow pages stop a share of those events before they arrive, and nothing sends them again. The platforms then see fewer purchases than you make, optimise your campaigns on incomplete data and report a lower return on your ad spend. Server-side tracking (Meta Conversions API, Google enhanced conversions, TikTok Events API) is the standard fix, and an ad account without it is working with a blind spot.

    How to fix it

    Send your events from a server as well as from the browser, starting with Purchase, for every ad platform you pay for.

    1. 1Turn on a server-side connection for each ad platform you run ads on (Meta Conversions API, Google enhanced conversions, TikTok Events API).
    2. 2Or run server-side tagging (for example a server GTM container) on a subdomain of your store.
    3. 3Make sure browser and server events share the same event_id so they are deduplicated.
    4. 4Check in each platform's events manager that server events arrive, then scan again.

    A scan sees what the browser sends, so a server feed that runs entirely behind your store does not show here. If you believe you already have one, open each platform's events manager and confirm that server events arrive for every event, not only for some.

    With AxiTrace: AxiTrace sends your events to Meta, Google, TikTok and more from your server, next to the browser tags you already have.

    What we saw
    Platforms detected in the browserMeta, Google Analytics, Google Ads, TikTok
    First-party hosts we checkednone
    Server-side patterns foundnone

Improve (2)

Medium and low impact issues worth fixing next.

Fix times are estimates for someone who can edit your theme, tag manager or app settings.

Working (12)

Checks your store passed.

  • Advertising or analytics tags were found

    Affects All tags
  • Your Meta pixel sends PageView

    Affects Meta
  • Your product page sends a product view event

    Affects MetaAffects GA4
  • ViewContent carries content_ids and content_type

    Affects Meta
  • GA4 view_item carries an items array

    Affects GA4

Score breakdown

  • Pixels & events25/100

    25% of the score

  • Server-side & dedup0/100

    20% of the score

  • Signal quality50/100

    15% of the score

  • Cookie durability50/100

    15% of the score

  • Consent0/100

    15% of the score

  • Ad-blocker exposure75/100

    10% of the score

Not checked

These checks could not run on your site, so they count neither for nor against you.

  • Cookies come from a host on a different IP, so Safari caps them at 7 days

    None of your identity cookies is set by a server, so this check does not apply.

  • Consent Mode is present but ad_user_data or ad_personalization is missing

    Google Consent Mode was not detected, so its v2 signals could not be checked.

The gcs and gcd parameters, briefly

Every request a Google tag sends carries the consent state in two query parameters. The checker decodes both on every Google request it sees.

gcs: storage consent

G1 followed by one digit for ad_storage and one for analytics_storage: 1 is granted, 0 is denied. No gcs at all means the tag ran before any consent default was set.

gcs values
gcs ad_storage analytics_storage
G100 denied denied
G110 granted denied
G101 denied granted
G111 granted granted

gcd: all four v2 signals

A longer code such as 13p3p3p3p5l1 with one letter per signal, in the order ad_storage, analytics_storage, ad_user_data, ad_personalization. An l in the third or fourth place means a v2 signal is missing.

Common gcd letters
Letter Meaning
l Signal not set at all
p Denied by default, no update yet
q Denied by default, denied again by the update
r Denied by default, granted by the update
v Granted by default, granted by the update

Frequently asked questions

How do I check if Consent Mode v2 is working?

Enter your site URL above. The checker loads the page in a fresh browser, records every request before anyone touches the banner, clicks Reject when it can and records again. It decodes the gcs and gcd parameters on each Google request and lists the tags that fired in each phase.

What is the difference between gcs and gcd?

gcs carries the two original signals, ad_storage and analytics_storage, as a short code such as G100. gcd carries all four Consent Mode v2 signals, including ad_user_data and ad_personalization, and records both the default and the update for each. A Google request without gcs ran with no consent state at all.

Is it a problem if Google tags still send requests after Reject?

Not by itself. In advanced mode Google tags send cookieless pings with the denied state, which is how the mode is designed. What the checker looks at is whether those requests carry the denied state in gcs and gcd, and whether other vendors keep sending hits after Reject.

Does a good result mean my site is compliant?

No. This is a technical check of what your site sends in one browser session. It is not legal advice and it does not certify compliance with GDPR, the ePrivacy rules or any other law. Use it to find technical gaps, and ask a qualified adviser about your legal position.

Why was the after-Reject check skipped?

Some banners hide the Reject option behind a settings screen or use controls our browser cannot operate reliably. When we cannot click Reject automatically we say so and mark that check as not checked, rather than guessing a result.