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

    CONNECTIONS / Datahash API / Datahash API to Google Store Sales

    Post offline and in-store sales to the Datahash API, wired to Google Store Sales matching.

    Send offline and in-store sales to one documented REST endpoint from any backend, in any language; Signals matches in-person transactions to Google accounts as store-sales conversions, hashed and consent-checked, with no pixel and no warehouse read.

    Talk to our team Explore the setup

    datahash-api -> google-store-sales :: live

    1. ● datahash-api → google.sales :: live
    2. > POST /v1/events source=api.purchase_events count=57,761
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ 202 accepted · 51,407 forwarded

    WHAT THIS ENABLES

    Datahash API to Google Store Sales

    Datahash API to Google Store Sales: post your offline and in-store sales to one REST endpoint and Signals matches in-person transactions to Google accounts as store-sales conversions, hashed and consent-checked server-side before Google Ads sees it.

    • Signals matches in-person transactions to Google accounts as store-sales conversions, from events your backend posts server-side.
    • Counter and showroom revenue inside the same ROAS view as online orders, without a pixel, a connector, or a nightly export.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google REST event recorded in Datahash API 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, whose engineers would rather POST an event than maintain a connector.

    Backend and platform teams driving Google Store Sales matching by sending offline and in-store sales straight from their own stack.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Create an API key in the Signals console and point your backend at the endpoint that feeds Google Ads' Store Sales Direct API.

    2. Map

      Map your event payload to Google Ads' Store Sales Direct API fields once; per-request validation flags bad events instead of dropping the batch.

    3. Deliver

      Post events as they happen and Signals matches in-person transactions to Google accounts as store-sales conversions, hashing server-side, with the store-sales match rate shown 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 Datahash API records the event.
    ON THE WIRE

    What Store Sales actually receives.

    signals :: datahash-api.google-store-sales :: wire

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=api.purchase_events
    3. transaction_time 2026-07-18T02:16:03 · transaction_amount_micros 28908000000
    4. currency_code SAR
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=89%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Datahash API

    Datahash API to Google OCI

    Datahash API to Google Offline Conversions: post your offline and in-store sales to one…

    Learn more

    from Datahash API

    Datahash API to Meta Offline CAPI

    Datahash API to Meta Offline CAPI: post your offline and in-store sales to one REST…

    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.

    Which backends can send to Google Store Sales through the Datahash API?

    Any backend that can make an HTTPS request. You POST offline and in-store sales as JSON to one documented endpoint and Signals forwards the offline conversions to Google Ads' Store Sales Direct API; identifiers are hashed at ingestion or sent pre-hashed, and omnichannel retailers reconciling point-of-sale against Google spend track the store-sales match rate in the debugger.

    How fresh are Google Store Sales events sent over the API?

    As fresh as you post them. The API accepts events in near real time, so counter and showroom revenue inside the same ROAS view as online orders reaches Google Ads moments after your backend fires the call, with per-event status returned inline. There is no batch window and no scheduled read, which keeps the store-sales match rate current for the teams driving Google Store Sales matching.

    NEXT STEP

    Datahash API to Google Store Sales, in production this week.

    Talk to our team All Datahash API use cases