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

    CONNECTIONS / Wasabi / Wasabi to Google Store Sales

    Wasabi objects into Google Ads, built for Google Store Sales matching.

    Connect Wasabi and point Signals at your Wasabi objects; it matches in-person transactions to Google accounts as store-sales conversions each time a new file lands, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    wasabi -> google-store-sales :: live

    1. ● wasabi → google.sales :: live
    2. > read closed_deals rows=23,935
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 20,345 matched

    WHAT THIS ENABLES

    Wasabi to Google Store Sales

    Wasabi to Google Store Sales: your Wasabi objects, hashed and consent-checked, feed Google Ads as Signals matches in-person transactions to Google accounts as store-sales conversions each time a new file lands.

    • Offline and in-store sales from your Wasabi objects activated for Google Ads, as Signals matches in-person transactions to Google accounts as store-sales conversions.
    • Counter and showroom revenue inside the same ROAS view as online orders, drawn from your Wasabi objects by teams archiving to Wasabi.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google File drop sync recorded in Wasabi 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 records already in Wasabi hot-storage buckets and objects.

    Teams archiving to Wasabi activating Google Store Sales matching straight from Wasabi objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only key scoped to the Wasabi bucket you name to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.

    2. Map

      Signals picks up your Wasabi objects, 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

      On each run, Signals pulls your Wasabi objects, matches in-person transactions to Google accounts as store-sales conversions, and processes only the newly dropped file, with the store-sales match rate 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 Wasabi records the event.
    ON THE WIRE

    What Store Sales actually receives.

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

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=wasabi.closed_deals
    3. transaction_time 2026-07-18T07:01:11 · transaction_amount_micros 40858000000
    4. currency_code SAR
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=85%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Wasabi

    Wasabi to Google OCI

    Wasabi to Google Offline Conversions: your Wasabi objects, hashed and consent-checked, feed…

    Learn more

    from Wasabi

    Wasabi to Meta Offline CAPI

    Wasabi to Meta Offline CAPI: your Wasabi objects, hashed and consent-checked, feed Meta as…

    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 Wasabi Google Store Sales sync run?

    Delivery tracks Wasabi, run by teams archiving to Wasabi: a near-real-time or scheduled sync of your Wasabi objects feeds Google Ads on that cadence. Each run processes only the newly dropped file, so store visits reconciled to campaign spend holds up on the store-sales match rate. The live debugger confirms every delivery inline.

    What match rate should a Wasabi-sourced Google Store Sales batch expect?

    Match rate follows identifier coverage in your Wasabi objects, which teams archiving to Wasabi control, not Wasabi itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Store Sales Direct API pinpoints the store-sales match rate, the number teams archiving to Wasabi tune against.

    NEXT STEP

    Wasabi to Google Store Sales, in production this week.

    Talk to our team All Wasabi use cases