Check your tracking setup
Enter a site and we report what's visible from the outside: which tags load, whether cookies survive Safari, and whether consent signals are in place. We also tell you what a page scan can't see.
Check your tracking setup
We load your page and report the tags, cookies and consent signals we can see. Nothing is installed.
Four things visible from your page
Ad-platform tags
Which pixels and tags load (Meta, Google, TikTok, Pinterest, Snap, LinkedIn) and whether they load from domains that common blocklists filter.
Server-set cookies
Whether your server sets the Meta browser cookie (_fbp) itself, and for how long. Safari limits cookies created by scripts to 7 days.
Consent signals
Whether a consent banner is installed and whether Google Consent Mode v2 defaults are set in the page.
First-party endpoint
Whether tracking goes through a subdomain you control or straight to third-party ad-network domains.
The parts that matter most happen on your server
A page scan only sees what the browser sees. The check lists these as "install to verify" and leaves them out of the score:
- Whether purchases are also sent server-side through the Conversions API
- Whether browser and server events share an event_id for deduplication
- Settings inside Events Manager, Google Ads or your GTM container
- What the ad platforms actually received and accepted
Every signal gets a receipt
Anacoic runs a first-party gateway on a subdomain you control. Events from the browser and your server go through it to Meta, Google and other destinations, and each one is logged with what was captured, what was sent and what the platform replied. That's how you verify the items a scan can't.
Set up a gatewayFrequently asked questions
How does the check work?
We load your page once from our edge network, the way a browser would, and read the HTML, response headers and cookies it sets. We don't run your JavaScript, log in, or place orders, so anything that only happens on checkout or on your server is outside what we can see.
How is the score calculated?
Only issues we actually observed lower the score, weighted across four areas: match quality, cookie persistence, blocker exposure, and consent and deduplication. Items we can't see are listed separately and never counted.
Why do server-set cookies matter for Safari?
Safari caps cookies created by JavaScript at 7 days, and at 24 hours on visits from links with tracking parameters. Cookies set by your server on your own domain aren't subject to that script cap, though Safari applies other rules, for example when the tracking subdomain resolves to a different IP range than your main site.
Do you store what you scan?
Results are cached for about ten minutes so repeat checks are fast. We only fetch the public page you enter. If you ask for help, we send the result summary and your email to our team so we can reply; nothing else is shared.
Get one gateway live before the next planning cycle.
Start with a single first-party path, validate delivery with the simulator and health views, then scale the same infrastructure across paid channels and agent-ready operations.
Best for operators who want to test immediately inside the dashboard.
Start freeBest for teams migrating off another setup or planning a multi-gateway rollout.
Book demoExplore gateway monitoring, live logs, health charts, and delivery analytics with synthetic data — no account required.
Try the sandbox →