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

    CONNECTIONS / File drops / File drops to Google OCI

    Your file drops, wired to Google Ads offline conversion import.

    Connect File drops and point Signals at your file drops; 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

    files -> google-oci :: live

    1. ● file drops → google.oci :: live
    2. > read closed_deals rows=34,682
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 27,746 matched

    WHAT THIS ENABLES

    File drops to Google Offline Conversions

    File drops to Google Offline Conversions: your file drops, 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.

    • Offline and in-store sales from your file drops 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 file drops by teams landing POS and back-office exports as files.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google F File drop sync recorded in File drops 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 POS, SFTP, S3, and GCS file drops.

    Teams landing POS and back-office exports as files activating Google Ads offline conversion import straight from file drops.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only access to the SFTP, S3, or GCS drop you name to feed Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      Signals picks up your file drops, 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 file drops, 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 File drops records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: files.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=files.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-23T01:12:30"
    5. conversion_value 23443 · currency_code GBP
    6. ✓ accepted · batch=daily
    RELATED USE CASES

    Adjacent moves on the same stack.

    from File drops

    Files to Google Store Sales

    POS and SFTP files to Google Store Sales validates and hashes each nightly export the…

    Learn more

    from File drops

    Files to Meta Offline CAPI

    POS and SFTP files to Meta Offline CAPI validates and hashes each export the moment it…

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

    You set the cadence, from near-real-time to a nightly File drops sync of your file drops 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 teams landing POS and back-office exports as files watch GCLID coverage. One scoped connection sets it up, cadence adjustable later.

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

    In File drops, match rate tracks the email and phone quality your file drops carry. Clean identifiers land for Google Ads; blank ones never will. The first Offline Conversion Import (Google Ads API) report shows teams landing POS and back-office exports as files where GCLID coverage needs work, a data-quality task handled in File drops.

    NEXT STEP

    File drops to Google OCI, in production this week.

    Talk to our team All File drops use cases