CONNECTIONS / MariaDB / MariaDB to Snap Offline CAPI
MariaDB tables into Snapchat, built for Snapchat in-store conversions.
Signals reads your MariaDB tables through a read-only database user scoped to the MariaDB tables you name, then reports in-store purchases against the Snapchat campaigns that reached the buyer so Snapchat sees offline conversions without an export.
- ● mariadb → snap.capi :: live
- > read closed_deals rows=15,484
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 13,626 matched
WHAT THIS ENABLES
MariaDB to Snapchat Offline CAPI
Snapchat Offline CAPI for MariaDB: Signals reports in-store purchases against the Snapchat campaigns that reached the buyer straight from your MariaDB tables, hashed and consent-screened each time the read runs.
- Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, reading your MariaDB tables each time the read runs.
- In-person conversions Snapchat can bid on, with no export step out of your MariaDB tables.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how MariaDB closes the loop.
Built for the teams that own the number.
Engineering teams running MariaDB who need physical-world sales counted inside Snapchat performance out of MariaDB tables.
From kickoff to verified events.
-
Connect
A read-only database user scoped to the MariaDB tables you name, mapped to Snapchat's Conversions API and tuned for offline event timing.
-
Map
Columns from your MariaDB tables 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 MariaDB tables 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 MariaDB records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=mariadb.closed_deals
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1784458370 · price 47284 · currency GBP
- ✓ accepted · match=true
Adjacent moves on the same stack.
from MariaDB
MariaDB to Google OCI
Google Offline Conversions for MariaDB: Signals reconciles closed-won revenue to the Google…
Learn morefrom MariaDB
MariaDB to Google Store Sales
Google Store Sales for MariaDB: Signals matches in-person transactions to Google accounts…
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 MariaDB Snap Offline CAPI sync run?
You set the cadence, from near-real-time to a nightly MariaDB sync of your MariaDB tables into Snapchat. Since Signals reads only the records changed since the last run, physical-world sales counted inside Snapchat performance keeps pace and engineering teams running MariaDB watch offline event timing. One scoped connection sets it up, cadence adjustable later.
What match rate should a MariaDB-sourced Snap Offline CAPI batch expect?
Match rate follows identifier coverage in your MariaDB tables, which engineering teams running MariaDB control, not MariaDB itself. A record with a current hashed email or phone matches for Snapchat; one missing both cannot. First-run feedback from Conversions API pinpoints offline event timing, the number engineering teams running MariaDB tune against.
NEXT STEP