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