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

    CONNECTIONS / Microsoft Excel / Microsoft Excel to Google OCI

    Your Excel workbook rows, wired to Google Ads offline conversion import.

    Signals reads your Excel workbook rows through read-only access to the Excel workbook you name, then reconciles closed-won revenue to the Google Ads click through GCLID so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    microsoft-excel -> google-oci :: live

    1. ● microsoft excel → google.oci :: live
    2. > read closed_deals rows=66,441
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 57,804 matched

    WHAT THIS ENABLES

    Microsoft Excel to Google Offline Conversions

    Microsoft Excel to Google Offline Conversions: your Excel workbook rows, hashed and consent-checked, feed Google Ads as Signals reconciles closed-won revenue to the Google Ads click through GCLID each time a new file lands.

    • Signals reconciles closed-won revenue to the Google Ads click through GCLID, reading your Excel workbook rows each time a new file lands.
    • A clean line from click to closed revenue, 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 Offline Conversion Impo… delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers whose Google-sourced deals close days after the click, working out of Excel worksheets and named ranges.

    Finance and ops teams working in Excel who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy 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' Offline Conversion Import (Google Ads API) and tuned for GCLID coverage.

    2. Map

      Columns from your Excel workbook rows align to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed as the file lands and checked for GCLID coverage.

    3. Deliver

      Each time a new file lands, Signals reads your Excel workbook rows and reconciles closed-won revenue to the Google Ads click through GCLID, processes only the newly dropped file, with GCLID coverage 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 OCI 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 OCI actually receives.

    signals :: microsoft-excel.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=microsoft-excel.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-17T16:54:37"
    5. conversion_value 22609 · currency_code USD
    6. ✓ accepted · batch=nightly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Microsoft Excel

    Microsoft Excel to Google Store Sales

    Microsoft Excel to Google Store Sales: 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 OCI

    ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…

    Learn more

    generic

    Google Offline Conversion Import

    Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Microsoft Excel Google OCI 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, Smart Bidding trained on booked revenue instead of a mid-funnel proxy keeps pace and finance and ops teams working in Excel watch GCLID coverage. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Microsoft Excel-sourced Google OCI 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 Offline Conversion Import (Google Ads API) pinpoints GCLID coverage, the number finance and ops teams working in Excel tune against.

    NEXT STEP

    Microsoft Excel to Google OCI, in production this week.

    Talk to our team All Microsoft Excel use cases