CONNECTIONS / Backblaze B2 / Backblaze B2 to Snap Offline CAPI
From Backblaze B2 files to Snapchat in-store conversions.
Connect Backblaze B2 and point Signals at your Backblaze B2 files; it reports in-store purchases against the Snapchat campaigns that reached the buyer each time a new file lands, hashed and consent-checked for Snapchat.
- ● backblaze b2 → snap.capi :: live
- > read closed_deals rows=47,707
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 40,551 matched
WHAT THIS ENABLES
Backblaze B2 to Snapchat Offline CAPI
Backblaze B2 to Snapchat Offline CAPI: your Backblaze B2 files, hashed and consent-checked, feed Snapchat as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer each time a new file lands.
- Offline and in-store sales from your Backblaze B2 files activated for Snapchat, as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer.
- Physical-world sales counted inside Snapchat performance, drawn from your Backblaze B2 files by teams archiving exports to Backblaze B2.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how Backblaze B2 closes the loop.
Built for the teams that own the number.
Teams archiving exports to Backblaze B2 activating Snapchat in-store conversions straight from Backblaze B2 files.
From kickoff to verified events.
-
Connect
A read-only application key scoped to the Backblaze B2 bucket you name to feed Snapchat's Conversions API, sized for offline event timing.
-
Map
Signals picks up your Backblaze B2 files, and its columns map to Snapchat's Conversions API in the visual mapper, hashed and checked for offline event timing.
-
Deliver
On each run, Signals pulls your Backblaze B2 files, reports in-store purchases against the Snapchat campaigns that reached the buyer, and processes only the newly dropped file, with offline event timing 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 Backblaze B2 records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=backblaze.closed_deals
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1784779835 · price 21979 · currency SAR
- ✓ accepted · match=true
Adjacent moves on the same stack.
from Backblaze B2
Backblaze B2 to Google OCI
Backblaze B2 to Google Offline Conversions: your Backblaze B2 files, hashed and…
Learn morefrom Backblaze B2
Backblaze B2 to Google Store Sales
Backblaze B2 to Google Store Sales: your Backblaze B2 files, hashed and consent-checked,…
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 Backblaze B2 Snap Offline CAPI sync run?
The pace follows your Backblaze B2 files: Signals sends changes from Backblaze B2 to Snapchat each time a new file lands. Because it processes only the newly dropped file, physical-world sales counted inside Snapchat performance stays current while teams archiving exports to Backblaze B2 keep offline event timing in view. Delivery needs no export and no manual upload.
What match rate should a Backblaze B2-sourced Snap Offline CAPI batch expect?
Coverage of hashed identifiers across your Backblaze B2 files decides it, and teams archiving exports to Backblaze B2 own that inside Backblaze B2. A live email or phone matches into Snapchat; neither, and it will not. First-run feedback flags offline event timing, which teams archiving exports to Backblaze B2 then raise inside your Backblaze B2 files.
NEXT STEP