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

    CONNECTIONS / Google Drive / Google Drive to Google Store Sales

    Your Google Drive files, wired to Google Store Sales matching.

    Signals reads your Google Drive files through read-only OAuth access to the Google Drive folder you name, then matches in-person transactions to Google accounts as store-sales conversions so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    google-drive -> google-store-sales :: live

    1. ● google drive → google.sales :: live
    2. > read closed_deals rows=68,115
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 57,217 matched

    WHAT THIS ENABLES

    Google Drive to Google Store Sales

    Google Store Sales for Google Drive: Signals matches in-person transactions to Google accounts as store-sales conversions straight from your Google Drive files, hashed and consent-screened each time a new file lands.

    • Signals matches in-person transactions to Google accounts as store-sales conversions, reading your Google Drive files each time a new file lands.
    • Store visits reconciled to campaign spend, with no export step out of your Google Drive files.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google File drop sync recorded in Google Drive 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, working out of Google Drive folders and shared exports.

    Teams sharing exports via Google Drive who need counter and showroom revenue inside the same ROAS view as online orders out of Google Drive files.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only OAuth access to the Google Drive folder you name, mapped to Google Ads' Store Sales Direct API and tuned for the store-sales match rate.

    2. Map

      Columns from your Google Drive files align to Google Ads' Store Sales Direct API in the visual mapper, hashed as the file lands and checked for the store-sales match rate.

    3. Deliver

      Each time a new file lands, Signals reads your Google Drive files and matches in-person transactions to Google accounts as store-sales conversions, processes only the newly dropped file, 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 Google Drive records the event.
    ON THE WIRE

    What Store Sales actually receives.

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

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=google-drive.closed_deals
    3. transaction_time 2026-07-14T13:27:34 · transaction_amount_micros 17344000000
    4. currency_code GBP
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=84%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Google Drive

    Google Drive to Google OCI

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

    Learn more

    from Google Drive

    Google Drive to Meta Offline CAPI

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

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

    Delivery tracks Google Drive, run by teams sharing exports via Google Drive: a near-real-time or scheduled sync of your Google Drive files 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 Google Drive-sourced Google Store Sales batch expect?

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

    NEXT STEP

    Google Drive to Google Store Sales, in production this week.

    Talk to our team All Google Drive use cases