CONNECTIONS / Redshift / Redshift to Meta Offline CAPI
Offline and in-store sales in Redshift, activated for Meta's offline optimization.
Grant a scoped IAM role, name the table or materialized view, and Signals credits dealer, branch, and phone sales to the Meta campaigns behind them with no UNLOAD to S3 and no file to hand off.
- ● redshift → meta.capi :: live
- > read sales.pos_fact rows=25,433
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 20,346 matched
WHAT THIS ENABLES
Redshift to Meta Offline CAPI
Redshift to Meta Offline CAPI: The Redshift Data API reads the offline and in-store sales in your Redshift tables, and Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, hashed and consent-checked as the materialized view refreshes.
- Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, reading your Redshift tables as the materialized view refreshes.
- In-store and phone revenue joining Meta's optimization loop, fed by analytics teams maintaining Redshift tables and materialized views.
The click, the conversion, and the credit.
The conversion happens off Meta, 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 in-store and phone revenue joining Meta's optimization loop.
From kickoff to verified events.
-
Connect
A scoped IAM role with SELECT on the schema you name to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.
-
Map
The Redshift Data API reads your Redshift tables, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.
-
Deliver
As the materialized view refreshes, Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, touches only the rows changed since the last read, with Meta's 62-day event window 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 /offline_conversions source=redshift.sales.pos_fact
- event_name "Purchase" · event_time 2026-07-13T09:32:42
- value 33483.00 · currency GBP
- em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-94162"
- ✓ accepted match=80%
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 Meta Offline CAPI
ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Meta Offline CAPI
Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…
Learn moreAsked on almost every call.
How often does the Redshift Meta Offline CAPI sync run?
The refresh schedule drives it: when the materialized view rebuilds nightly, Meta gets a nightly feed, and an hourly refresh runs hourly. Each read touches only changed rows, so in-store and phone revenue joining Meta's optimization loop stays fresh for Meta's 62-day event window without RA3 load rising.
What match rate should a Redshift-sourced Meta 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 Meta's Offline Conversions API, the figure considered-purchase brands closing revenue far from the browser weigh against Meta's 62-day event window.
NEXT STEP