Tracking checker.
Enter your website and see what your tracking really does: which pixels and tags run, what fires before cookie consent, whether Consent Mode v2 and ad click IDs work, and if you have server-side tracking.
- Opening your site as a new visitor
- Recording what fires before consent
- Accepting the cookie banner
- Checking ad click IDs and duplicates
- Looking for server-side tracking
This usually takes 20 to 40 seconds.
Tracking health
Fix these first
Every check
Tags we found
| Tag | IDs | Before consent |
|---|
Want this fixed?
We’ll set up consent, Consent Mode v2, click IDs and server-side tracking properly, for a fixed price agreed before we start.
We can only see what a browser sees: not your conversions, and not whether a server-side set-up forwards everything. Scans run from a data centre, so banners shown only in some countries may differ. Results are kept for a few hours.
Free, no sign-up. We open your site in a secure browser and only read what any visitor’s browser would see.
How to read your results.
The checker loads the page you enter (your homepage, or an ad landing page, which often has different tracking) twice in a fresh browser. The first visit touches nothing, so anything that fires is firing before the visitor has chosen. Then it accepts your cookie banner, reloads the page and records again. Test ad click IDs are added to the address, the way an ad click would add them, so it can see whether they survive.
The five areas
- Tracking set-up: whether Google Analytics 4, a tag manager and your ad platforms’ tags (Google Ads, Meta, Microsoft, TikTok, LinkedIn and others) are on the page.
- Consent and privacy: whether there is a cookie banner, whether tracking waits for it, and whether Google Consent Mode v2 passes the visitor’s choice to Google’s tags.
- Ad click IDs: whether gclid, fbclid and msclkid are stored after consent, and whether a redirect strips them. Without them, ad platforms can’t match conversions to clicks.
- Data quality: duplicate page views or pixels, which inflate traffic and distort conversion rates, plus leftover Universal Analytics code.
- Server-side tracking: signs that tags send data through your own domain, which ad blockers and browser limits cut less.
What the grade means
Each check is weighted by how much it affects the data your ad platforms optimise on. A or B means the basics are solid. C or below usually means ad platforms are bidding on incomplete or unconsented data. Start with the “fix these first” list: the fixes are ordered by impact.
What it can’t see
It doesn’t submit forms or place orders, so conversion tags, enhanced conversions and the Conversions API aren’t tested. For those, see our guides to the Meta Conversions API and GA4 key events, or how we approach measurement. Tagging links properly matters too: the UTM builder helps there.
Keep calculating.
UTM builder
Tag your links with presets for Meta, TikTok, Google, email and more, then see which GA4 channel each link lands in, and get dynamic URL parameters for your ad platforms.
Open tool →Costs & biddingCPM calculator
Calculate cost per thousand impressions from spend and impressions, and see the budget needed to hit a reach target.
Open tool →Costs & biddingCPA calculator
Work out cost per acquisition, conversion rate and CPC, and the maximum you can bid per click to hit a target CPA.
Open tool →Tracking questions.
01What does the tracking checker test?
It opens your website the way a new visitor would and records every tracking request. It shows which tags you run (GA4, Google Ads, Meta, TikTok, Microsoft, LinkedIn and more), whether anything fires before cookie consent, whether Google Consent Mode v2 is active, whether ad click IDs such as gclid and fbclid are kept, whether pages are counted twice, and whether there are signs of server-side tracking.
02How do I check if my Meta pixel is working?
Enter your website above. The checker lists every Meta pixel ID it sees, whether it fires before or after consent, whether it sends PageView more than once, and whether the Meta click ID (fbclid) is stored in the _fbc cookie, which improves event matching.
03How can I tell if Google Consent Mode v2 is set up?
Google tags send consent signals with every request. The checker reads them and tells you if Consent Mode v2 is active, only on the older version 1, or missing. Since March 2024 Google has needed v2 to build audiences and model conversions from UK and EU visitors.
04Is it a problem if tracking fires before consent?
In the UK, PECR and UK GDPR need consent before analytics or advertising cookies are set. Tags that start before the visitor chooses are a privacy risk, and they also mix unconsented data into your reports. Google’s cookieless “consent denied” pings are allowed, so the checker doesn’t count those against you.
05Can the checker see my conversions or server-side set-up?
No. It doesn’t place orders or fill in forms on your site, so it can’t see conversion events. It can spot signs of server-side tracking, such as tags loading from your own subdomain or server-set cookies, but it can’t confirm the server forwards everything correctly.
06Why does it say it couldn’t accept my cookie banner?
The checker recognises the common consent tools (OneTrust, Cookiebot, CookieYes, Usercentrics and others) and most “Accept all” buttons. Custom banners sometimes use wording or code it can’t click. Some consent tools also only show a banner in certain countries, so results can differ from what UK visitors see.
07Does running a scan affect my analytics?
A scan is one or two page views from an automated browser, using test click IDs that start with BPTEST. Many analytics tools filter automated visits, and the rest is a single visit you can ignore.
We set up consent, Consent Mode v2, click ID storage and server-side tracking for a fixed price agreed up front.