CONNECTIONS / AWS S3 / AWS S3 to Snap Offline CAPI
S3 exports into Snapchat, built for Snapchat in-store conversions.
Signals reads your S3 exports through a read-only IAM key scoped to the one S3 bucket you name, then reports in-store purchases against the Snapchat campaigns that reached the buyer so Snapchat sees offline conversions without an export.
- ● aws s3 → snap.capi :: live
- > read closed_deals rows=57,682
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 50,760 matched
WHAT THIS ENABLES
AWS S3 to Snapchat Offline CAPI
Snapchat Offline CAPI for AWS S3: Signals reports in-store purchases against the Snapchat campaigns that reached the buyer straight from your S3 exports, hashed and consent-screened each time a new file lands.
- Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, reading your S3 exports each time a new file lands.
- In-person conversions Snapchat can bid on, with no export step out of your S3 exports.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how AWS S3 closes the loop.
Built for the teams that own the number.
Data teams landing exports in S3 who need physical-world sales counted inside Snapchat performance out of S3 exports.
From kickoff to verified events.
-
Connect
A read-only IAM key scoped to the one S3 bucket you name, mapped to Snapchat's Conversions API and tuned for offline event timing.
-
Map
Columns from your S3 exports align to Snapchat's Conversions API in the visual mapper, hashed as the file lands and checked for offline event timing.
-
Deliver
Each time a new file lands, Signals reads your S3 exports and reports in-store purchases against the Snapchat campaigns that reached the buyer, processes only the newly dropped file, 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 AWS S3 records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=aws-s3.closed_deals
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1783913390 · price 33461 · currency GBP
- ✓ accepted · match=true
Adjacent moves on the same stack.
from AWS S3
AWS S3 to Google OCI
Google Offline Conversions for AWS S3: Signals reconciles closed-won revenue to the Google…
Learn morefrom AWS S3
AWS S3 to Google Store Sales
Google Store Sales for AWS S3: Signals matches in-person transactions to Google accounts 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 AWS S3 Snap Offline CAPI sync run?
You set the cadence, from near-real-time to a nightly AWS S3 sync of your S3 exports into Snapchat. Since Signals processes only the newly dropped file, physical-world sales counted inside Snapchat performance keeps pace and data teams landing exports in S3 watch offline event timing. One scoped connection sets it up, cadence adjustable later.
What match rate should a AWS S3-sourced Snap Offline CAPI batch expect?
Match rate follows identifier coverage in your S3 exports, which data teams landing exports in S3 control, not AWS S3 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 data teams landing exports in S3 tune against.
NEXT STEP