CONNECTIONS / Freshsales / Freshsales to Snap Offline CAPI
Your Freshsales deals and lifecycle stages, wired to Snapchat in-store conversions.
Signals reads your Freshsales deals and lifecycle stages through scoped OAuth access to Freshsales, reading only your Freshsales deals and lifecycle stages, then reports in-store purchases against the Snapchat campaigns that reached the buyer so Snapchat sees offline conversions without an export.
- ● freshsales → snap.capi :: live
- > read closed_deals rows=40,911
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 31,911 matched
WHAT THIS ENABLES
Freshsales to Snapchat Offline CAPI
Snapchat Offline CAPI for Freshsales: Signals reports in-store purchases against the Snapchat campaigns that reached the buyer straight from your Freshsales deals and lifecycle stages, hashed and consent-screened as records change.
- Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, reading your Freshsales deals and lifecycle stages as records change.
- In-person conversions Snapchat can bid on, with no export step out of your Freshsales deals and lifecycle stages.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how Freshsales closes the loop.
Built for the teams that own the number.
Sales teams running Freshsales who need physical-world sales counted inside Snapchat performance out of Freshsales deals and lifecycle stages.
From kickoff to verified events.
-
Connect
Scoped OAuth access to Freshsales, reading only your Freshsales deals and lifecycle stages, mapped to Snapchat's Conversions API and tuned for offline event timing.
-
Map
Columns from your Freshsales deals and lifecycle stages align to Snapchat's Conversions API in the visual mapper, hashed as the sync runs and checked for offline event timing.
-
Deliver
As records change, Signals reads your Freshsales deals and lifecycle stages and reports in-store purchases against the Snapchat campaigns that reached the buyer, sends only the records that changed, with offline event timing watched in the debugger.
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 Freshsales records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=freshsales.closed_deals
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1783960636 · price 15179 · currency AED
- ✓ accepted · match=true
Adjacent moves on the same stack.
from Freshsales
Freshsales to Google OCI
Google Offline Conversions for Freshsales: Signals reconciles closed-won revenue to the…
Learn morefrom Freshsales
Freshsales to Google Store Sales
Google Store Sales for Freshsales: Signals matches in-person transactions to Google…
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.
How often does the Freshsales Snap Offline CAPI sync run?
The pace follows your Freshsales deals and lifecycle stages: Signals sends changes from Freshsales to Snapchat as records change. Because it sends only the records that changed, physical-world sales counted inside Snapchat performance stays current while sales teams running Freshsales keep offline event timing in view. Delivery needs no export and no manual upload.
What match rate should a Freshsales-sourced Snap Offline CAPI batch expect?
In Freshsales, match rate tracks the email and phone quality your Freshsales deals and lifecycle stages carry. Clean identifiers land for Snapchat; blank ones never will. The first Conversions API report shows sales teams running Freshsales where offline event timing needs work, a data-quality task handled in Freshsales.
NEXT STEP