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

    CONNECTIONS / Attio / Attio to Google Store Sales

    Your Attio workspace lists, wired to Google Store Sales matching.

    Connect Attio and point Signals at your Attio workspace lists; it matches in-person transactions to Google accounts as store-sales conversions as records change, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    attio -> google-store-sales :: live

    1. ● attio → google.sales :: live
    2. > read closed_deals rows=22,920
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 18,565 matched

    WHAT THIS ENABLES

    Attio to Google Store Sales

    Google Store Sales for Attio: Signals matches in-person transactions to Google accounts as store-sales conversions straight from your Attio workspace lists, hashed and consent-screened as records change.

    • Offline and in-store sales from your Attio workspace lists 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 Attio workspace lists by RevOps teams running Attio.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google CRM record sync recorded in Attio 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 Attio records, lists, and workspace objects.

    RevOps teams running Attio activating Google Store Sales matching straight from Attio workspace lists.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Attio, reading only your Attio workspace lists to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.

    2. Map

      Signals reads your Attio workspace lists, 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 Attio workspace lists, matches in-person transactions to Google accounts as store-sales conversions, and sends only the records that changed, 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 Attio records the event.
    ON THE WIRE

    What Store Sales actually receives.

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

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=attio.closed_deals
    3. transaction_time 2026-07-16T00:46:31 · transaction_amount_micros 44236000000
    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 Attio

    Attio to Google OCI

    Google Offline Conversions for Attio: Signals reconciles closed-won revenue to the Google…

    Learn more

    from Attio

    Attio to Meta Offline CAPI

    Meta Offline CAPI for Attio: Signals credits dealer, branch, and phone sales to the Meta…

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

    The pace follows your Attio workspace lists: Signals sends changes from Attio to Google Ads as records change. Because it sends only the records that changed, counter and showroom revenue inside the same ROAS view as online orders stays current while RevOps teams running Attio keep the store-sales match rate in view. Delivery needs no export and no manual upload.

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

    Coverage of hashed identifiers across your Attio workspace lists decides it, and RevOps teams running Attio own that inside Attio. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags the store-sales match rate, which RevOps teams running Attio then raise inside your Attio workspace lists.

    NEXT STEP

    Attio to Google Store Sales, in production this week.

    Talk to our team All Attio use cases