CONNECTIONS / Redshift / Redshift to Snap Offline CAPI
Offline and in-store sales in Redshift, activated for Snapchat in-store conversions.
Grant a scoped IAM role, name the table or materialized view, and Signals reports in-store purchases against the Snapchat campaigns that reached the buyer with no UNLOAD to S3 and no file to hand off.
- ● redshift → snap.capi :: live
- > read sales.pos_fact rows=52,953
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 46,069 matched
WHAT THIS ENABLES
Redshift to Snapchat Offline CAPI
Redshift to Snapchat Offline CAPI: The Redshift Data API reads the offline and in-store sales in your Redshift tables, and Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, hashed and consent-checked as the materialized view refreshes.
- Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, reading your Redshift tables as the materialized view refreshes.
- Physical-world sales counted inside Snapchat performance, fed by analytics teams maintaining Redshift tables and materialized views.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how Redshift closes the loop.
Built for the teams that own the number.
Analytics teams maintaining Redshift tables and materialized views who need physical-world sales counted inside Snapchat performance.
From kickoff to verified events.
-
Connect
A scoped IAM role with SELECT on the schema you name to feed Snapchat's Conversions API, sized for offline event timing.
-
Map
The Redshift Data API reads your Redshift tables, and its columns map to Snapchat's Conversions API in the visual mapper, hashed and checked for offline event timing.
-
Deliver
As the materialized view refreshes, Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, touches only the rows changed since the last read, 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 Redshift records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=redshift.sales.pos_fact
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1784482141 · price 40267 · currency USD
- ✓ accepted · match=true
Adjacent moves on the same stack.
from Redshift
Redshift to Google OCI
Redshift to Google Offline Conversions: The Redshift Data API reads the offline and…
Learn morefrom Redshift
Redshift to Google Store Sales
Redshift to Google Store Sales: The Redshift Data API reads the offline and in-store sales…
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 Redshift Snap Offline CAPI sync run?
The refresh schedule drives it: when the materialized view rebuilds nightly, Snapchat gets a nightly feed, and an hourly refresh runs hourly. Each read touches only changed rows, so physical-world sales counted inside Snapchat performance stays fresh for offline event timing without RA3 load rising.
What match rate should a Redshift-sourced Snap Offline CAPI batch expect?
The fill rate of the view matters more than Redshift itself. A clean hashed email or phone matches; a blank one never will. The first scheduled read reports quality from Snapchat's Conversions API, the figure retail and QSR advertisers whose Snapchat audience buys in person weigh against offline event timing.
NEXT STEP