Server-side conversions

Browser-side conversion pixels miss a lot: ad blockers, tracking protection, and cross-device journeys all eat events the ad platforms never see. Sapt closes that gap by uploading the conversions it measures server-side, with customer data hashed before it leaves Sapt. The platforms get a more complete, better-matched signal — which directly improves Smart Bidding and optimization. Sapt sends conversions to two destinations. Connect either or both.

​

Meta CAPI

Connect Meta, pick a pixel, and conversions upload to Meta’s Conversions API server-side — with hashed PII plus the browser’s fbc/fbp cookies for matching, and deduped against your browser pixel by event id. This is the same engine documented in detail, with full REST examples, on the API reference page:

​

Google Ads CAPI

Connect Google Ads, pick a conversion action, and from then on every conversion Sapt records uploads to Google Ads server-side, automatically. Both lead and purchase conversions are eligible. A conversion uploads whenever it carries an identifier Google can match on: This recovers the attribution the browser loses (blocked tags, expired cookies, cross-device) and feeds Google’s Smart Bidding the offline-confirmed conversions it needs to optimize toward real outcomes rather than form-fills the tag happened to catch.

​

Set it up

You can wire up Google server-side conversions two ways:

​

From the dashboard

Open Analytics → Tracking, connect Google Ads, and choose the conversion action that recorded conversions should upload to. Once it’s set, no per-conversion work is needed — anything Sapt records flows through automatically.

​

From the Attribution MCP

Do the same from an AI agent with the Attribution MCP:

• getGoogleConversionsSetup — read the current configuration.
• configureGoogleConversions — connect Google Ads and pick the conversion action.

​

Keep going