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

    CONNECTIONS / Dropbox / Dropbox to Google OCI

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

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

    dropbox -> google-oci :: live

    1. ● dropbox → google.oci :: live
    2. > read closed_deals rows=12,828
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 11,160 matched

    WHAT THIS ENABLES

    Dropbox to Google Offline Conversions

    Google Offline Conversions for Dropbox: Signals reconciles closed-won revenue to the Google Ads click through GCLID straight from your Dropbox 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 Dropbox files each time a new file lands.
    • A clean line from click to closed revenue, with no export step out of your Dropbox files.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google File drop sync recorded in Dropbox 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 Dropbox folders and shared exports.

    Teams dropping exports in Dropbox who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy out of Dropbox files.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only OAuth access to the Dropbox folder you name, mapped to Google Ads' Offline Conversion Import (Google Ads API) and tuned for GCLID coverage.

    2. Map

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

    What OCI actually receives.

    signals :: dropbox.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=dropbox.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-21T16:11:13"
    5. conversion_value 15584 · currency_code USD
    6. ✓ accepted · batch=nightly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Dropbox

    Dropbox to Google Store Sales

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

    Learn more

    from Dropbox

    Dropbox to Meta Offline CAPI

    Meta Offline CAPI for Dropbox: Signals credits dealer, branch, and phone sales to the Meta…

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

    Delivery tracks Dropbox, run by teams dropping exports in Dropbox: a near-real-time or scheduled sync of your Dropbox 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 Dropbox-sourced Google OCI batch expect?

    Coverage of hashed identifiers across your Dropbox files decides it, and teams dropping exports in Dropbox own that inside Dropbox. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags GCLID coverage, which teams dropping exports in Dropbox then raise inside your Dropbox files.

    NEXT STEP

    Dropbox to Google OCI, in production this week.

    Talk to our team All Dropbox use cases