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

    CONNECTIONS / Google Sheets / Google Sheets to Google OCI

    Your Google Sheets rows, wired to Google Ads offline conversion import.

    Connect Google Sheets and point Signals at your Google Sheets rows; it reconciles closed-won revenue to the Google Ads click through GCLID each time a new file lands, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    google-sheet -> google-oci :: live

    1. ● google sheets → google.oci :: live
    2. > read closed_deals rows=15,013
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 13,211 matched

    WHAT THIS ENABLES

    Google Sheets to Google Offline Conversions

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

    • Offline and in-store sales from your Google Sheets rows activated for Google Ads, as Signals reconciles closed-won revenue to the Google Ads click through GCLID.
    • Smart Bidding trained on booked revenue instead of a mid-funnel proxy, drawn from your Google Sheets rows by ops teams maintaining Google Sheets.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off Google, away from any pixel. Here is how Google Sheets 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 Sheets 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, with the records already in Google Sheets tabs and ranges.

    Ops teams maintaining Google Sheets activating Google Ads offline conversion import straight from Google Sheets rows.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only OAuth access to the Google Sheet you name to feed Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      Signals picks up your Google Sheets rows, and its columns map to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed and checked for GCLID coverage.

    3. Deliver

      On each run, Signals pulls your Google Sheets rows, reconciles closed-won revenue to the Google Ads click through GCLID, and processes only the newly dropped file, with GCLID coverage 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 Google Sheets records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: google-sheet.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=google-sheet.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-15T22:45:38"
    5. conversion_value 23542 · currency_code GBP
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Google Sheets

    Google Sheets to Google Store Sales

    Google Sheets to Google Store Sales: Signals reads your Google Sheets rows and matches…

    Learn more

    from Google Sheets

    Google Sheets to Meta Offline CAPI

    Google Sheets to Meta Offline CAPI: Signals reads your Google Sheets rows and credits…

    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 Google Sheets Google OCI sync run?

    You set the cadence, from near-real-time to a nightly Google Sheets sync of your Google Sheets 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 ops teams maintaining Google Sheets watch GCLID coverage. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Google Sheets-sourced Google OCI batch expect?

    In Google Sheets, match rate tracks the email and phone quality your Google Sheets rows carry. Clean identifiers land for Google Ads; blank ones never will. The first Offline Conversion Import (Google Ads API) report shows ops teams maintaining Google Sheets where GCLID coverage needs work, a data-quality task handled in Google Sheets.

    NEXT STEP

    Google Sheets to Google OCI, in production this week.

    Talk to our team All Google Sheets use cases