Server-side forwarding · Server-side tier
Conversions that land even when the pixel doesn't.
Forward conversions server-side to the Meta Conversions API, Google Ads, GA4 and TikTok with hashed PII, click-id matching and pixel dedupe. No containers to host.
the problem
Why this breaks today.
Browsers lose conversions.
Blockers, tracking prevention and visitors who close the tab before the thank-you page loads all drop the browser event.
Server-side usually means running servers.
The common route is a server-side GTM container you host, size and pay for by request volume.
Off-page conversions have no pixel at all.
Bookings, form tools and payments happen on someone else's site, where your pixel never fires.
how it works
How TracerKit handles it.
Forwarded to each platform's server API.
Conversions go to the Meta Conversions API, Google Ads offline conversion upload, GA4 Measurement Protocol and the TikTok Events API from a delivery queue with retries.
Matched to the real visit.
Click ids and browser ids captured on landing (fbc, fbp, gclid, ttclid, the GA client id) travel with the conversion, plus email and phone hashed before storage.
Counted once.
Server events share an event id with the browser pixel fire, so platforms that dedupe count one conversion, not two.
Webhooks for off-page conversions.
Point Calendly, Typeform, Stripe, or any tool through Zapier, Make or n8n at a TracerKit webhook and the conversion is forwarded like any other.
questions
Asked and answered.
Do I need to host anything?+
No. There is no container to deploy or scale. Connect each destination's credentials in the dashboard and turn forwarding on.
Is it priced per event?+
No. Server-side is a flat monthly price per site with no per-conversion metering.
How do I know deliveries succeed?+
Every forwarded event records its delivery status per destination, and reconciliation compares what TracerKit observed against what the platform reports.
the terms behind it
What is server-side tracking?
Server-side tracking sends conversion events from your server to ad and analytics platforms, instead of relying only on scripts in the visitor's browser.
What is the Conversions API?
The Conversions API (CAPI) is Meta's server-to-server endpoint for sending conversion events directly to Meta, alongside or instead of the pixel.
What are enhanced conversions?
Enhanced conversions is a Google Ads feature that sends hashed email and phone with a conversion to improve how it's matched to ad clicks.
What are click IDs?
Click IDs like gclid, fbclid and ttclid are URL parameters ad platforms add to ad links so a later conversion can be tied back to the specific click.
more of what you get
Tag manager
A tag manager that lives outside your repo.
Version history
Every tag change, on the record.
Tag verification
Know every tag is actually firing.
Silence alerts
Hear about a dead pixel in minutes, not weeks.
Platform reconciliation
Your numbers, checked against theirs.
First-party proxy
Serve your tags from your own domain.
Stop guessing whether your tracking works.
Tag management is free forever. Paid tiers start with a 14-day trial, no card.