The cookie banner was updated
Visitors click "accept", but Google, Meta or TikTok are never told. Every visitor is treated as declined and conversions vanish from reports.
Free tracking scan · No login · 30 seconds
Plumfinch loads your site like a real visitor, accepts the cookie banner and records every ad and analytics tag that fires. You get a score, the problems that cost you conversions, and how to fix them.
Read-only. We only see what any visitor's browser sees, and we never store visitor data.
Checks 25 ad and analytics platforms, including
The problem
Nobody gets an error message when a conversion tag stops firing. The ad platforms simply optimise on less data, and you find out weeks later in a client meeting.
Visitors click "accept", but Google, Meta or TikTok are never told. Every visitor is treated as declined and conversions vanish from reports.
A new checkout, a site redesign or a "cleanup" drops the purchase event. Smart bidding keeps running on nothing.
A previous agency's Ads ID or pixel still sits on the site, double-counting conversions or sending data to an account you don't own.
How it works
A headless Chrome browser opens your site from the outside, exactly like a new visitor from an ad.
We record what fires before the cookie banner, accept it, and check that every platform gets the update.
We load the page with test click IDs to see if redirects keep the information that ties a sale to an ad.
A 0–100 score, the problems ranked by impact, the evidence for each one and the steps to fix it.
What we check
Each check is based on the platforms' own public setup guidance. If the scan cannot tell, it says "unknown" rather than guessing.
Every platform's base tag loads once and actually sends events, not just loads a script.
Google Consent Mode v2 default and update, IAB TCF and GPP signals, and pixels that respect "reject".
Second Google Ads accounts, extra Meta or TikTok pixels and leftover agency tags.
gclid, fbclid, ttclid, msclkid and others still in the URL after http→https, www and language redirects.
Email addresses sent in plain text inside pixel requests, which every ad platform forbids.
Google tag gateway and server-side setups that keep measurement working when browsers block trackers.
Coming next · Monitoring
A public scan sees your site once. Monitoring connects read-only to Google Ads, GA4, Meta and TikTok and watches every client account around the clock.
FAQ
Yes. The score and the top problems are free with no sign-up. The full report with evidence and fix steps is free too: we only ask for an email address so we can tell you when monitoring launches.
No. The scan only visits your public page, like any visitor. Monitoring will use read-only access. We never change your tags, ads or accounts.
Google tag / Tag Manager, Google Analytics 4, Google Ads, Floodlight (DV360 / CM360), Meta (Facebook & Instagram), TikTok, Microsoft Advertising (Bing UET), Amazon Ads, LinkedIn Insight Tag, Snapchat, Pinterest, X (Twitter), Reddit, The Trade Desk, Criteo, Adform, Taboola, Outbrain, Quora, Yahoo DSP, Awin, Yandex Metrica, LINE Tag, Naver, Kakao.
We scan as a brand-new visitor from outside your network, with no cookies, and we test both before and after the cookie banner. Tag debuggers usually run in your own logged-in browser, where consent was given long ago.
Yes, scan your order confirmation ("thank you") page as well as your homepage. If the page fires purchase events, we check that each one carries a value, a currency and an order ID, as the platforms recommend.
No. It sees which tags fire on the page you scan. Whether conversions are actually recorded in Google Ads, GA4, Meta or TikTok needs read-only access to the accounts, which is what monitoring does.
The scan result: which tags and IDs your public page loads, and the request URLs they sent. No cookie values, no visitor data. If you give us your email, we store that too. See the privacy page.
Enter any page: your homepage, a landing page or a product page.