tracking.audit
Server-side tracking systems

Transparent advertising: follow the real trail of your ad spend.

Client-side tags lose data every day — to Safari's cookie limits, to ad blockers running on standard domain lists, and to the extra weight they add to your page. I build server-side tracking systems that close the gaps that can actually be closed, and make your pages faster in the process.

No commitment. 20-minute review of your current setup.
Client-side signal — gaps from blockers & ITP Server-side signal — most gaps closed
Where the data leaks

Three ways your pixels are already failing

iOS & ITP

Apple shrinks your window every update

Safari's Intelligent Tracking Prevention cuts first-party cookie life to 7 days. Your retargeting window shrinks a little more with every release.

Ad blockers

Blocked by domain, not by disguise

Most ad blockers match against known domains like googletagmanager.com — moving off that domain closes this gap. Brave and DuckDuckGo go further and resolve the DNS behind your own subdomain, so that trick alone won't fool them.

Broken pixels

Silent drift from reality

One tag manager typo or one CMP misconfiguration, and months of conversion data quietly stop matching what actually happened.

The fix

Move the tag off the browser: less for it to load, more for you to control

Client-side tag
  • Blocked outright by domain-based ad blockers
  • Cut short by Safari's ITP cookie limits
  • One more third-party script weighing the page down
  • Depends entirely on the visitor's browser and settings
Server-side pipeline
  • Avoids blocklist-based ad blocking — how most ad blockers work
  • Can match server-side events to hashed customer data (email, order ID) — durable identity that doesn't depend on cookie lifetime at all
  • Fewer third-party scripts in-browser — faster pages, which affects Core Web Vitals and SEO
  • One point to filter, enrich, and govern data before it leaves your infrastructure

Note: this closes the gap against standard, blocklist-based ad blockers. Browsers with built-in CNAME resolution — Brave, DuckDuckGo — still detect and block a subdomain that resolves to known tracking infrastructure, and Safari's own ITP has capped CNAME-cloaked cookies at 7 days since 2020, so a plain subdomain pointing at different infrastructure than your main site doesn't grant durable cookies by itself. No client-triggered setup is fully immune to that; the reliable fix for identity is hashed-data matching, not stretching cookie lifetime.

Stop feeding your ad platforms bad data

A free audit shows exactly how much conversion data you're losing today, what's realistically recoverable, and how much faster a server-side setup would make your pages.