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

    CONNECTIONS / Google Drive / Google Drive to Google OCI

    Your Google Drive files, wired to Google Ads offline conversion import.

    Signals reads your Google Drive files through read-only OAuth access to the Google Drive folder 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

    google-drive -> google-oci :: live

    1. ● google drive → google.oci :: live
    2. > read closed_deals rows=45,373
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 38,567 matched

    WHAT THIS ENABLES

    Google Drive to Google Offline Conversions

    Google Offline Conversions for Google Drive: Signals reconciles closed-won revenue to the Google Ads click through GCLID straight from your Google Drive files, hashed and consent-screened each time a new file lands.

    • Signals reconciles closed-won revenue to the Google Ads click through GCLID, reading your Google Drive files each time a new file lands.
    • A clean line from click to closed revenue, 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 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 Google Drive folders and shared exports.

    Teams sharing exports via Google Drive who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy 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' Offline Conversion Import (Google Ads API) and tuned for GCLID coverage.

    2. Map

      Columns from your Google Drive files 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 Google Drive files 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 Google Drive records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: google-drive.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=google-drive.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-19T16:37:59"
    5. conversion_value 39272 · currency_code SAR
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Google Drive

    Google Drive to Google Store Sales

    Google Store Sales for Google Drive: Signals matches in-person transactions to Google…

    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 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 Drive Google OCI 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 a clean line from click to closed revenue holds up on GCLID coverage. The live debugger confirms every delivery inline.

    What match rate should a Google Drive-sourced Google OCI 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 GCLID coverage, which teams sharing exports via Google Drive then raise inside your Google Drive files.

    NEXT STEP

    Google Drive to Google OCI, in production this week.

    Talk to our team All Google Drive use cases