Platform

Conversion API (CAPI)

Server-side forwarding, platform setup, dedupe, and match quality optimization.

AI brief: Configure destinations in dashboard with OAuth/pixel IDs. Trackrift sends server events with same event_id as browser pixel for dedupe. Requires fbclid/gclid on events + fbp/fbc in context for Meta match quality.

Browser pixels lose 20–40% of conversions on iOS and ad-blocked sessions. Conversion API sends the same events server-side from Trackrift's collector — enriched with click IDs, cookies, and hashed PII when available.

Supported destinations

Platform	What we send	Dashboard setup
Meta	Standard events + fbp/fbc + event_id	OAuth + Pixel ID + test event code
Google Ads	Enhanced conversions / offline imports	OAuth + conversion action ID
TikTok	Events API 2.0 payloads	Pixel ID + access token
LinkedIn	Conversions API	Partner ID + conversion rule URN

Event flow

Browser track('purchase') → collector stores event → destination worker maps to platform schema → HTTPS POST to Meta/Google/etc. Same event_id as your browser pixel prevents double counting.

Dedupe with the browser pixel

purchase-dedupe.ts

const eventId = tracker.track('purchase', {
  value: 297,
  currency: 'USD',
  content_ids: ['sku_starter'],
});

// Meta Pixel — eventID must match
fbq('track', 'Purchase', {
  value: 297,
  currency: 'USD',
  content_ids: ['sku_starter'],
}, { eventID: eventId });

// Google gtag — same concept
gtag('event', 'purchase', {
  transaction_id: eventId,
  value: 297,
  currency: 'USD',
});

Meta match quality checklist

Load Meta Pixel on the same registrable domain as Trackrift collector (CNAME helps).
Preserve fbclid in landing URLs — avoid stripping query params on redirect.
Call identify({ email }) before purchase when possible (hashed server-side).
Pass shared event_id to pixel and SDK.
Use Test Events in Meta Events Manager when validating setup.

Offline conversions

CRM closed-won events via sendServerEvent still forward to CAPI when email matches an identity with prior ad click IDs.