Server-Side Conversion Tracking
Server-side conversion tracking explained — sending authoritative outcomes from your server or CRM, and why it does not mean sending everything twice.
Updated July 22, 2026.
Server-side conversion tracking is the transmission of conversion events from a controlled backend, CRM, app service, POS or server container to an advertising platform.
Why it matters
A server often knows whether an order actually completed, whether a lead qualified and what value changed later. Server delivery can improve reliability and matching, but it does not bypass consent, policy or duplicate-control requirements.
How it works across ad platforms
| Platform or system | Current treatment |
|---|---|
| Meta | Conversions API supports website, app, offline and messaging events. |
| Conversions API supports server and CRM outcomes through direct, partner and GTM paths. | |
| TikTok | Events API supports web, app and offline events; TikTok recommends Pixel plus API for web. |
| Conversions API supports conversion events; deduplication is required with Pixel. | |
| API for Conversions supports web, app and offline events and shared event-ID deduplication. | |
| Microsoft Advertising | UET Conversions API is a limited pilot; offline imports remain broadly documented. |
| Google Ads | Data Manager/enhanced conversions for leads and current supported APIs/import paths. |
Implementation rules
- Send the authoritative event time and source value.
- Use permitted match keys and required normalization/hashing.
- Implement platform-specific deduplication when browser and server overlap.
- Send promptly enough for measurement and bidding.
- Log requests, responses and rejected rows.
- Never treat server-side as consent-free.
Common mistakes
- Sending the same event from browser and server without shared ID.
- Using server time instead of actual conversion time.
- Double-hashing identifiers.
- Batching events too late for optimization.
- Building against a pilot API without account eligibility.
Minimum QA
- Compare source records with API accepted events.
- Test duplicates and retries.
- Validate timestamp/timezone.
- Review match quality and error responses.
- Test retraction/correction paths where supported.
Official sources
- Meta Conversions API
- LinkedIn Conversions API
- TikTok standard events
- Reddit Conversion Events
- Pinterest API for Conversions
- Google Ads offline conversions
- Microsoft offline conversions
Technically verified: July 22, 2026. This reference uses official platform sources only for platform-specific behavior. Definitions and implementation recommendations are editorial synthesis by The Ad Spend.