CONNECTIONS / GCS / GCS to Snap Offline CAPI
Your GCS objects, wired to Snapchat in-store conversions.
Connect GCS and point Signals at your GCS objects; 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.
- ● gcs → snap.capi :: live
- > read closed_deals rows=72,753
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 58,930 matched
WHAT THIS ENABLES
GCS to Snapchat Offline CAPI
GCS to Snapchat Offline CAPI: your GCS objects, 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 GCS objects 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 GCS objects by data teams landing exports in GCS.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how GCS closes the loop.
Built for the teams that own the number.
Data teams landing exports in GCS activating Snapchat in-store conversions straight from GCS objects.
From kickoff to verified events.
-
Connect
A read-only service account scoped to the one GCS bucket you name to feed Snapchat's Conversions API, sized for offline event timing.
-
Map
Signals picks up your GCS objects, 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 GCS objects, 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 GCS records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=google-cloud-storage.closed_deals
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1784131147 · price 23181 · currency SAR
- ✓ accepted · match=true
Adjacent moves on the same stack.
from GCS
GCS to Google OCI
GCS to Google Offline Conversions: your GCS objects, hashed and consent-checked, feed…
Learn morefrom GCS
GCS to Google Store Sales
GCS to Google Store Sales: your GCS objects, hashed and consent-checked, feed Google Ads as…
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 GCS Snap Offline CAPI sync run?
The pace follows your GCS objects: Signals sends changes from GCS 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 data teams landing exports in GCS keep offline event timing in view. Delivery needs no export and no manual upload.
What match rate should a GCS-sourced Snap Offline CAPI batch expect?
Coverage of hashed identifiers across your GCS objects decides it, and data teams landing exports in GCS own that inside GCS. A live email or phone matches into Snapchat; neither, and it will not. First-run feedback flags offline event timing, which data teams landing exports in GCS then raise inside your GCS objects.
NEXT STEP