Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / Redshift / Redshift to Google OCI

    Offline and in-store sales in Redshift, activated for Google Ads offline conversion import.

    Grant a scoped IAM role, name the table or materialized view, and Signals reconciles closed-won revenue to the Google Ads click through GCLID with no UNLOAD to S3 and no file to hand off.

    Talk to our team Explore the setup

    redshift -> google-oci :: live

    1. ● redshift → google.oci :: live
    2. > read sales.pos_fact rows=22,601
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 18,081 matched

    WHAT THIS ENABLES

    Redshift to Google Offline Conversions

    Redshift to Google Offline Conversions: The Redshift Data API reads the offline and in-store sales in your Redshift tables, and Signals reconciles closed-won revenue to the Google Ads click through GCLID, hashed and consent-checked as the materialized view refreshes.

    • Signals reconciles closed-won revenue to the Google Ads click through GCLID, reading your Redshift tables as the materialized view refreshes.
    • Smart Bidding trained on booked revenue instead of a mid-funnel proxy, fed by analytics teams maintaining Redshift tables and materialized views.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off Google, away from any pixel. Here is how Redshift closes the loop.

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google R Scheduled read sync recorded in Redshift S Signals hash · dedupe Offline Conversion Impo… delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers whose Google-sourced deals close days after the click, with the numbers already modeled in Redshift tables and materialized views.

    Analytics teams maintaining Redshift tables and materialized views who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A scoped IAM role with SELECT on the schema you name to feed Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      The Redshift Data API reads your Redshift tables, and its columns map to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed and checked for GCLID coverage.

    3. Deliver

      As the materialized view refreshes, Signals reconciles closed-won revenue to the Google Ads click through GCLID, touches only the rows changed since the last read, with GCLID coverage watched in the debugger.

    WHAT YOU GET

    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 OCI 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.
    ON THE WIRE

    What OCI actually receives.

    signals :: redshift.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=redshift.sales.pos_fact
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-18T09:00:54"
    5. conversion_value 37056 · currency_code GBP
    6. ✓ accepted · batch=daily
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Redshift

    Redshift to Google Store Sales

    Redshift to Google Store Sales: The Redshift Data API reads the offline and in-store sales…

    Learn more

    from Redshift

    Redshift to Meta Offline CAPI

    Redshift to Meta Offline CAPI: The Redshift Data API reads the offline and in-store sales…

    Learn more

    same use case

    ActiveCampaign to Google OCI

    ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…

    Learn more

    generic

    Google Offline Conversion Import

    Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Redshift Google OCI sync run?

    The refresh schedule drives it: when the materialized view rebuilds nightly, Google Ads gets a nightly feed, and an hourly refresh runs hourly. Each read touches only changed rows, so Smart Bidding trained on booked revenue instead of a mid-funnel proxy stays fresh for GCLID coverage without RA3 load rising.

    What match rate should a Redshift-sourced Google OCI 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 Google Ads' Offline Conversion Import (Google Ads API), the figure advertisers whose Google-sourced deals close days after the click weigh against GCLID coverage.

    NEXT STEP

    Redshift to Google OCI, in production this week.

    Talk to our team All Redshift use cases