Glossary · Data plumbing

Server-side tracking

Sending conversion events from your server rather than the visitor’s browser — more reliable measurement of a dataset that may be worse.

One of 25 entries in the Endpoint Forms glossary.

Definition

Emitting analytics and conversion events from your own infrastructure — a server-side tag container or a direct API call — instead of relying on a script in the visitor’s browser.

Why it matters

Browser-side pixels lose events, systematically and unevenly: blockers, tracking prevention, short cookie lifetimes, and people who navigate away before the tag fires. The loss is not random, which is worse than the loss being large.

“People don’t switch forms because of price. They switch because their tracking is broken. Typeform doesn’t fire server side pixels. If you run paid acquisition, half your conversions disappear into iOS 14 and ad blockers. … The real moat isn’t the builder. It’s the integrations. Server side Meta CAPI, TikTok CAPI, Google Ads, GA4. That’s what marketers pay $99/mo for.”

OP, eighteen months building a Typeform alternative · r/SaaS · 2026 (self-promotional; treat as an operator’s claim, not a measurement)

In practice

Send a shared event_id from both the browser and the server so the platform deduplicates rather than double-counting. See duplicate leads.
Pass hashed identifiers — email, phone, click id — as match keys. Match quality is the metric that determines whether any of this worked.
Carry consent state to the server explicitly. Moving the call server-side does not move the legal basis with it.
Fire on a validated submission, not on a request. Otherwise you have built a very reliable pipe for reporting spam.

The common mistake

Treating it as a way around consent.

It is sold, sometimes explicitly, as the answer to blockers and privacy controls. It is not a legal mechanism. It is a reliability mechanism, and the same rules about what you may collect and why apply to a request originating from your data centre.

The measurement version of the same error: judging the migration by event volume. Volume goes up by construction, because you stopped losing events. That tells you the pipe works. It tells you nothing about whether the events are worth having.

Related terms

Conversions API: The server-to-server endpoint each ad platform provides for conversion events. A transport, not a truth.
GCLID: The click id Google appends to your landing page URL — the join key between your CRM and your ad account, and it is discarded by default.
Offline conversion import: Uploading what happened downstream back to the ad platform against the click id — a standard practice, and one that teaches the platform while teaching the form nothing.
Duplicate leads: The same person, twice — inflating your conversion count and, through it, the signal you send back to the ad platform.
Hidden field: An input the visitor never sees, carrying your attribution into the submission — and the first thing an automated filler reads.