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

    CONNECTIONS / Copper / Copper to Google OCI

    From Copper account pipelines to Google Ads offline conversion import.

    Connect Copper and point Signals at your Copper account pipelines; it reconciles closed-won revenue to the Google Ads click through GCLID as records change, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    copper -> google-oci :: live

    1. ● copper → google.oci :: live
    2. > read closed_deals rows=30,554
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 24,443 matched

    WHAT THIS ENABLES

    Copper to Google Offline Conversions

    Copper to Google Offline Conversions: your Copper account pipelines, hashed and consent-checked, feed Google Ads as Signals reconciles closed-won revenue to the Google Ads click through GCLID as records change.

    • Offline and in-store sales from your Copper account pipelines 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 Copper account pipelines by Google Workspace sales teams on Copper.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google CRM record sync recorded in Copper 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 Copper people, companies, and account pipelines.

    Google Workspace sales teams on Copper activating Google Ads offline conversion import straight from Copper account pipelines.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Copper, reading only your Copper account pipelines to feed Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      Signals reads your Copper account pipelines, 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 Copper account pipelines, reconciles closed-won revenue to the Google Ads click through GCLID, and sends only the records that changed, 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 Copper records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: copper.google-oci :: wire

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

    Adjacent moves on the same stack.

    from Copper

    Copper to Google Store Sales

    Copper to Google Store Sales: your Copper account pipelines, hashed and consent-checked,…

    Learn more

    from Copper

    Copper to Meta Offline CAPI

    Copper to Meta Offline CAPI: your Copper account pipelines, 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 Copper Google OCI sync run?

    You set the cadence, from near-real-time to a nightly Copper sync of your Copper account pipelines into Google Ads. Since Signals sends only the records that changed, Smart Bidding trained on booked revenue instead of a mid-funnel proxy keeps pace and Google Workspace sales teams on Copper watch GCLID coverage. One scoped connection sets it up, cadence adjustable later.

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

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

    NEXT STEP

    Copper to Google OCI, in production this week.

    Talk to our team All Copper use cases