First-party proxy · First-party proxy tier

Serve your tags from your own domain.

Route third-party scripts through a subdomain you own so domain blocklists have nothing to match. Ad-blocker and ITP resilient, set up with one CNAME.

the problem

Why this breaks today.

✗

Blocklists target vendor domains.

Ad blockers and privacy browsers match on known tracking hosts. When the script never loads, the visit never counts.

✗

Third-party cookies are short-lived.

Safari's tracking prevention limits cookies set by scripts from other domains, so returning visitors look new.

how it works

How TracerKit handles it.

✓

One CNAME.

Point a subdomain such as metrics.yoursite.com at TracerKit. The loader, config and proxied scripts are then served from it.

✓

Automatic source rewrite.

Tags you manage are rewritten to load through your subdomain. No change to each vendor snippet.

✓

Still verified.

Proxied tags report health like any other, so you can see the difference first-party serving makes.

questions

Asked and answered.

Is this the same as Google tag gateway?+

Similar idea, wider scope. Google's gateway serves Google tags first-party; TracerKit's proxy covers the tags you manage, whatever the vendor.

Do I need server-side tracking too?+

Not necessarily. The proxy keeps browser tags loading; server-side forwarding sends conversions from the server so they arrive even when the browser drops them. Many sites start with the proxy.

What DNS access do I need?+

The ability to add one CNAME record on your domain.

the terms behind it

more of what you get

Stop guessing whether your tracking works.

Tag management is free forever. Paid tiers start with a 14-day trial, no card.