CONNECTIONS / Salesforce / Salesforce to Snap Offline CAPI
Salesforce revenue, delivered to Snap on your schedule.
Closed-won deals in Salesforce rarely happen on Snapchat itself. Signals hashes the Opportunity and Contact record and delivers it to Snap's Conversions API on the cadence your sales operations can sustain.
- ● salesforce → snap.offline_capi :: live
- > event Opportunity closed-won value=18,600 AED
- hash sha256(email,phone)
- route snap.offline_capi batch=daily
- ✓ delivered · match 61%
WHAT THIS ENABLES
Salesforce to Snapchat Offline Conversions API
Salesforce to Snapchat Offline Conversions API is the pipeline that delivers closed-won Salesforce revenue to Snap's Conversions API on a schedule you set, matched by hashed customer identifiers, so in-store and call-centre sales count toward Snap campaign optimization.
- Closed-won Salesforce deals counted inside Snap campaign optimization.
- A delivery cadence set to how often your sales team actually updates Opportunity records.
- The same hashed-identifier pipeline you already run for other offline destinations.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how Salesforce closes the loop.
Built for the teams that own the number.
Teams with Salesforce as the system of record for offline conversions closing on Snap-attributed leads.
From kickoff to verified events.
-
Connect
Connected App access to the Salesforce Opportunity and Contact objects that carry the closed deal.
-
Map
Closed-won mapped to a Snap offline conversion event in the visual mapper.
-
Deliver
Scheduled delivery to Snap's Conversions API, deduped and monitored per batch.
What changes when the CSV goes away.
| Capability | Manual CSV upload | Datahash |
|---|---|---|
| Reporting | Offline sales sit in a separate export, reconciled by hand. | Revenue counted in the same Offline CAPI reporting as web conversions. |
| Deduplication | A re-uploaded file risks counting the same conversion twice. | Deduped delivery, so a resent record never counts as a second conversion. |
| Match visibility | Match quality is a guess until the numbers look off. | Match rate reported per upload, tied to the source event set that produced it. |
| Effort and latency | An analyst exports and uploads on a manual cadence. | Server-side and automatic the moment Salesforce records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=salesforce.opportunity
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "c48a12…" · hashed_phone_number "9de701…"
- timestamp 1784127360 · price 18600 · currency AED
- ✓ accepted · match=true
Adjacent moves on the same stack.
from Salesforce
Salesforce to Google OCI
Salesforce to Google Offline Conversion Import is the pipeline that persists the GCLID…
Learn morefrom Salesforce
Salesforce to Google Store Sales
Salesforce to Google Store Sales is the pipeline that hashes contact and closed-won…
Learn moresame use case
ActiveCampaign to Snap Offline CAPI
ActiveCampaign to Snapchat Offline CAPI: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
Snap Offline CAPI
Deliver offline conversions to Snap on a schedule that fits your operations.
Learn moreAsked on almost every call.
What delivery cadence works best for Salesforce-sourced Snap conversions?
Fresher delivery generally helps Snap's optimization more, so daily is a common default where sales operations allow it. Weekly batches still work, since Snap accepts offline events within its attribution lookback window, and the right choice usually comes down to how often your Salesforce Opportunity records actually get updated.
How does Snap match a closed Salesforce deal back to the original ad?
Through hashed customer identifiers, most commonly email and phone pulled from the Salesforce Contact tied to the Opportunity. Snap matches those hashes to its own record of ad exposure on its side, so raw contact data from Salesforce never leaves your environment unhashed at any point in the pipeline.
NEXT STEP