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

    CONNECTIONS / Redshift / Redshift to Google Store Sales

    Offline and in-store sales in Redshift, activated for Google Store Sales matching.

    Grant a scoped IAM role, name the table or materialized view, and Signals matches in-person transactions to Google accounts as store-sales conversions with no UNLOAD to S3 and no file to hand off.

    Talk to our team Explore the setup

    redshift -> google-store-sales :: live

    1. ● redshift → google.sales :: live
    2. > read sales.pos_fact rows=41,469
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 33,590 matched

    WHAT THIS ENABLES

    Redshift to Google Store Sales

    Redshift to Google Store Sales: The Redshift Data API reads the offline and in-store sales in your Redshift tables, and Signals matches in-person transactions to Google accounts as store-sales conversions, hashed and consent-checked as the materialized view refreshes.

    • Signals matches in-person transactions to Google accounts as store-sales conversions, reading your Redshift tables as the materialized view refreshes.
    • Counter and showroom revenue inside the same ROAS view as online orders, 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 Store Sales Direct API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Omnichannel retailers reconciling point-of-sale against Google spend, with the numbers already modeled in Redshift tables and materialized views.

    Analytics teams maintaining Redshift tables and materialized views who need counter and showroom revenue inside the same ROAS view as online orders.

    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' Store Sales Direct API, sized for the store-sales match rate.

    2. Map

      The Redshift Data API reads your Redshift tables, and its columns map to Google Ads' Store Sales Direct API in the visual mapper, hashed and checked for the store-sales match rate.

    3. Deliver

      As the materialized view refreshes, Signals matches in-person transactions to Google accounts as store-sales conversions, touches only the rows changed since the last read, with the store-sales match rate 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 Store Sales 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 Store Sales actually receives.

    signals :: redshift.google-store-sales :: wire

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=redshift.sales.pos_fact
    3. transaction_time 2026-07-19T17:21:43 · transaction_amount_micros 21100000000
    4. currency_code SAR
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=81%
    RELATED USE CASES

    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 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 Store Sales

    ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Store Sales

    Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Redshift Google Store Sales 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 counter and showroom revenue inside the same ROAS view as online orders stays fresh for the store-sales match rate without RA3 load rising.

    What match rate should a Redshift-sourced Google Store Sales 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' Store Sales Direct API, the figure omnichannel retailers reconciling point-of-sale against Google spend weigh against the store-sales match rate.

    NEXT STEP

    Redshift to Google Store Sales, in production this week.

    Talk to our team All Redshift use cases