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.
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
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.
1Turn on a server-side connection for each ad platform you run ads on (Meta Conversions API, Google enhanced conversions, TikTok Events API).
2Or run server-side tagging (for example a server GTM container) on a subdomain of your store.
3Make sure browser and server events share the same event_id so they are deduplicated.
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 browser
Meta, Google Analytics, Google Ads, TikTok
First-party hosts we checked
none
Server-side patterns found
none
Why it matters
Meta counted two PageView events for one visit. Double events inflate your numbers, confuse the algorithm about which visitors matter and make your cost per result look better than it is. This usually happens when a theme, an app and Google Tag Manager each install the pixel.
How to fix it
Keep one installation of the Meta pixel and remove the others.
1Open Meta Pixel Helper on your home page and note every place the pixel ID appears.
2Keep one installation (your platform's native integration or GTM, not both).
3Remove the pixel code from theme files or the second app.
When someone clicks your Meta ad, the link carries an fbclid. The pixel should save it in the _fbc cookie so that later events can be matched to that click. We opened your site with a test fbclid and no _fbc cookie appeared, so conversions from ad clicks are harder for Meta to attribute.
How to fix it
Make sure the Meta pixel loads on landing pages before any redirect removes the fbclid.
1Check that the Meta pixel loads on landing pages before any redirect removes the query string.
2Make sure redirects (for example to a country store) keep the full query string.
3If your consent banner blocks the pixel until consent, _fbc appears only after consent, which is expected.
With AxiTrace: AxiTrace saves the fbclid from the landing page in the _fbc cookie and sends it with the visitor's server events.
We loaded your page and did not click anything on your consent banner. These tracking requests were sent anyway. If your banner is meant to ask first, the tags are not waiting for it. This is a technical observation, not a legal assessment.
How to fix it
Assign each listed tag to a consent category so it waits for the visitor's choice.
1In your consent platform, check that the listed tags are assigned to a consent category.
2In GTM, add consent checks (Consent Mode or trigger conditions) to these tags.
3Scan again and confirm the list is empty or contains only requests with Consent Mode denied signals.
What we saw
Banner detected
CookieYes
Banner detected at
1500 ms after the page started loading
Request before any click
Meta PageView to www.facebook.com at 1.2 s
Request before any click
Google Analytics page_view to www.google-analytics.com at 1.3 s
Why it matters
Your Google tags send hits, but we found no Consent Mode default command and no consent parameters (gcs or gcd) on the hits. Google needs Consent Mode v2 signals for visitors in the European Economic Area to use their data for measurement and remarketing, so audiences and conversion modelling for those visitors can stop working without them.
How to fix it
Set Consent Mode defaults before your Google tags load, and update them when the visitor chooses.
1Check whether your consent platform supports Google Consent Mode v2 and turn it on.
2Make sure a gtag('consent', 'default', ...) command runs before the Google tag loads.
3Make sure the banner sends gtag('consent', 'update', ...) after the visitor chooses.
4Scan again and check that the hits carry gcs and gcd.
What we saw
Google tags
G-NWO2026, AW-50011122
Consent commands found
none
gcs and gcd on hits
absent
Why it matters
Safari deletes cookies written by JavaScript after 7 days (24 hours when the visit comes from a link with a click ID). A returning Safari visitor then looks like a new person, so conversions after a week lose the link to the ad that brought them. About a third of ecommerce traffic is Safari.
How to fix it
Set your identity cookies from your own server with a Set-Cookie header.
1Set the identity cookie from your own server with a Set-Cookie header on your main domain.
2Serve tracking from a subdomain that resolves to your own server's IP address, not to a third-party CNAME.
3Scan again: the cookie row should show "Set by: server".
With AxiTrace: When tracking runs through your own domain, AxiTrace sets its visitor cookie from your server, so Safari no longer cuts it to 7 days.
What we saw
Cookie
_fbp: set by JavaScript, expiry requested 90 days
Safari lifetime (computed)
_fbp: 7 dayscomputed
Cookie
_ga: set by JavaScript, expiry requested 400 days
Safari lifetime (computed)
_ga: 7 dayscomputed
Cookie
_ga_NWO2026: set by JavaScript, expiry requested 400 days
Safari lifetime (computed)
_ga_NWO2026: 7 dayscomputed
Cookie
_gcl_aw: set by JavaScript, expiry requested 90 days
Safari lifetime (computed)
_gcl_aw: 1 daycomputed
Cookie
_ttp: set by JavaScript, expiry requested 400 days
Safari lifetime (computed)
_ttp: 7 dayscomputed
Improve (2)
Medium and low impact issues worth fixing next.
Why it matters
Your product page sends ViewContent, but without a value or a currency. Meta uses them to learn which products and visitors are worth more, and to report the value of product views. Without them, value-based optimisation and catalogue ads work with less information.
How to fix it
Send value and currency with every ViewContent event.
1In your Meta integration or GTM tag, add value (the product price as a number) and currency (a three-letter code such as EUR or USD) to ViewContent.
We checked your tracking requests against EasyPrivacy, the list most ad blockers use. Visitors with an ad blocker never send the matched requests, so their visits and sales are missing from your ad platforms. Ad blockers are common on desktop, especially with younger and tech-savvy audiences.
How to fix it
Send your most important events through your own domain or server, where the list does not match them.
1Start with purchase and lead events, which matter most for optimisation.
2Send them through a server-side feed (Conversions API, enhanced conversions) or a first-party endpoint on your domain.
3Keep the browser tags for everything else.
4Scan again to see the share drop.
With AxiTrace: When tracking runs through your own domain, AxiTrace collects events on a path the common ad-blocker list does not match and sends them to the ad platforms from your server.
What we saw
List checked
easyprivacy (202609280000)
Tracking requests checked
10
Requests on the list
8 (80%)
Example of a matched request
Meta (www.facebook.com)
Example of a matched request
Google Analytics (www.google-analytics.com)
Example of a matched request
Google Ads (googleads.g.doubleclick.net)
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
29out of 100
Needs work
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.