CONNECTIONS / Redshift
Redshift + Datahash: activate the warehouse you already report from.
Your Redshift tables hold purchases, leads, LTV scores, and offline sales your ad platforms never see. Signals reads them on a schedule through a scoped IAM role and delivers them hashed and consent-aware.
- ● redshift :: signals live
- > data api read sales.pos_fact rows=57,410
- > materialized view high_value_customers
- hash sha256(email,phone) role=iam_read_only
- route meta · google · tiktok · snap · linkedin
- ✓ 5 destinations synced · match 85%
The signal Redshift yields, and receives.
Every kind of signal that moves between Redshift and the platforms, through one hashed, deduplicated route.
- Offline conversions
- Point-of-sale and closed-won tables leave Redshift hashed and matched to the campaign that drove the sale.
- Lead conversions
- Opportunity-stage tables read through the Data API arrive as conversion events without an UNLOAD to S3.
- Custom audiences
- A high-value segment defined once in SQL becomes a hashed, scheduled audience with no CSV export.
- Lead generation inbound
- Renewal and subscription events sync as the materialized view refreshes, keeping recurring revenue in bidding.
Pick your platform. Every use case for it, in one place.
Every way Redshift data moves, grouped by platform and ranked by how many use cases Redshift supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect with a scoped read-only IAM role.
-
Map
Map columns to event fields and match keys in the visual mapper.
-
Hash and consent
Hashing and consent flags applied at read.
-
Deliver
Scheduled or incremental delivery, with per-destination match feedback.
Redshift questions, answered.
Does Datahash copy our warehouse?
No. Reads run through the Redshift Data API against a scoped IAM role, delivery is event-level, and nothing from your cluster is copied to our side. Identifiers are SHA-256 hashed before rows leave Redshift, and a self-hosted Core deployment is available when data cannot leave your perimeter, in which case the hashing happens inside your own environment.
How fresh is the sync?
On the schedule your materialized views already refresh, from every 15 minutes to weekly, with reads that touch only rows changed since the last run. A view rebuilt nightly delivers nightly and one refreshed every few minutes delivers close to real time, so RA3 load stays low with no full re-scan and no UNLOAD to S3.
Who writes the SQL?
You point Signals at a table or a materialized view and the mapper handles the rest, so no new SQL or export job is needed to feed a platform. Custom views are welcome when you want to pre-shape the data, and the mapping can change later without granting the IAM role any new access.
NEXT STEP
See your Redshift data working in every ad platform.
Ready to enable a use case, or still mapping what Redshift data could do? Our team helps you find the right place to start.
