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

    CONNECTIONS / Microsoft Excel / Microsoft Excel to Google Store Sales

    Your Excel workbook rows, wired to Google Store Sales matching.

    Signals reads your Excel workbook rows through read-only access to the Excel workbook 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

    microsoft-excel -> google-store-sales :: live

    1. ● microsoft excel → google.sales :: live
    2. > read closed_deals rows=36,085
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 29,590 matched

    WHAT THIS ENABLES

    Microsoft Excel to Google Store Sales

    Microsoft Excel to Google Store Sales: your Excel workbook rows, 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.

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

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google File drop sync recorded in Microsoft Exc… 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 Excel worksheets and named ranges.

    Finance and ops teams working in Excel who need counter and showroom revenue inside the same ROAS view as online orders out of Excel workbook rows.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      Columns from your Excel workbook rows 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 Excel workbook rows 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 Microsoft Excel records the event.
    ON THE WIRE

    What Store Sales actually receives.

    signals :: microsoft-excel.google-store-sales :: wire

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=microsoft-excel.closed_deals
    3. transaction_time 2026-07-23T03:34:56 · transaction_amount_micros 33000000000
    4. currency_code AED
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=82%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Microsoft Excel

    Microsoft Excel to Google OCI

    Microsoft Excel to Google Offline Conversions: your Excel workbook rows, hashed and…

    Learn more

    from Microsoft Excel

    Microsoft Excel to Meta Offline CAPI

    Microsoft Excel to Meta Offline CAPI: your Excel workbook rows, hashed and consent-checked,…

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

    You set the cadence, from near-real-time to a nightly Microsoft Excel sync of your Excel workbook rows into Google Ads. Since Signals processes only the newly dropped file, counter and showroom revenue inside the same ROAS view as online orders keeps pace and finance and ops teams working in Excel watch the store-sales match rate. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your Excel workbook rows, which finance and ops teams working in Excel control, not Microsoft Excel 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 finance and ops teams working in Excel tune against.

    NEXT STEP

    Microsoft Excel to Google Store Sales, in production this week.

    Talk to our team All Microsoft Excel use cases