Server-to-server conversion tracking
Server-to-server (S2S) conversion tracking reports a conversion from one server directly to another — typically your backend to an ad platform or affiliate network — keyed by a click ID captured at the landing visit. It removes the dependence on a browser pixel firing at conversion time, which matters for offline conversions, multi-step flows, and environments where client tags are unreliable.
What this means
In server-to-server tracking, the platform appends a click identifier (such as a gclid or fbclid) to the landing URL. Your system stores that identifier with the user's record. When the conversion completes — possibly minutes or weeks later, possibly offline — your server sends a postback to the platform referencing that click ID, and the platform attributes the conversion to the original interaction.
This decouples conversion reporting from a browser being present at the moment of conversion, which is essential for leads closed by phone, subscriptions activated later, or app events.
Where it fits and its caveats
S2S is the backbone of offline conversion import, affiliate postbacks, and mobile measurement. Because the click ID is the join key, accuracy depends on capturing and storing it reliably and respecting its lifetime within the platform's lookback window.
Caveats: if the click ID is lost (stripped, not stored, expired) the conversion cannot be matched; consent and data-handling rules still apply to the identifiers you store; and S2S reports a deterministic match for one click, so it is not itself a multi-touch model. Google and other platforms document the click-ID-based postback contract.
- Keyed by a stored click ID (e.g. gclid), not a live pixel
- Enables offline, delayed, and multi-step conversion reporting
- Match fails if the click ID is not stored or expires
How it appears in analytics and logs
A conversion arriving via a stored click ID rather than a live pixel indicates S2S tracking; the credit ties back to the original click even though the browser was no longer involved.
Diagnostic use case
Use S2S tracking to report conversions that finalize off-page or later (callbacks, phone sales, app installs), keyed to the click ID you stored at the original visit.
What WebmasterID can help detect
WebmasterID captures campaign and click context first-party at the landing visit, the data an S2S postback later needs to attribute a conversion.
Common mistakes
- Failing to capture and persist the click ID at the landing visit.
- Posting back after the platform's lookback window has closed.
- Treating a single S2S match as a multi-touch attribution model.
Privacy and accuracy notes
S2S relies on click identifiers and your own data, still subject to consent and minimization rules. This page is educational, not legal advice.
Related pages
- Conversions API (CAPI)
A Conversions API (CAPI) is a server-side interface that sends conversion and event data directly from a business's servers to an ad platform, rather than relying solely on a browser pixel. It exists because in-browser tags increasingly miss events due to tracking prevention, ad blockers, and lost cookies; a server connection can pass events the browser never reported, subject to consent and matching.
- Offline conversion import
Offline conversion import (OCI) connects events that happen away from the website — a sales call that closes, an in-store purchase, a qualified lead in a CRM — back to the online ad click that began the journey. It works by capturing a click identifier (such as Google's GCLID) at the start and later uploading the offline outcome keyed to that identifier, closing the online-to-offline attribution loop.
- Server-side attribution and tagging
Server-side attribution moves the collection and forwarding of measurement events from the browser to a server you control — via server-side tag management or platform conversion APIs like Meta's CAPI. It can improve resilience to browser restrictions and give you governance over what data leaves your environment, but it is a data-flow change, not a way to bypass consent.
- Campaign links
Preserve click and campaign IDs for later S2S matching.
Sources and verification notes
- Google Ads Help — Import conversions from clicks (offline / click ID)Documents click-ID-keyed server-side conversion import.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.