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

    CONNECTIONS / Attio / Attio to Google OCI

    Your Attio workspace lists, wired to Google Ads offline conversion import.

    Connect Attio and point Signals at your Attio workspace lists; 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

    attio -> google-oci :: live

    1. ● attio → google.oci :: live
    2. > read closed_deals rows=40,921
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 36,010 matched

    WHAT THIS ENABLES

    Attio to Google Offline Conversions

    Google Offline Conversions for Attio: Signals reconciles closed-won revenue to the Google Ads click through GCLID straight from your Attio workspace lists, hashed and consent-screened as records change.

    • Offline and in-store sales from your Attio workspace lists 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 Attio workspace lists by RevOps teams running Attio.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google CRM record sync recorded in Attio 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 Attio records, lists, and workspace objects.

    RevOps teams running Attio activating Google Ads offline conversion import straight from Attio workspace lists.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Attio, reading only your Attio workspace lists to feed Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      Signals reads your Attio workspace lists, 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 Attio workspace lists, 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 Attio records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: attio.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=attio.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-20T21:25:26"
    5. conversion_value 31740 · currency_code GBP
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Attio

    Attio to Google Store Sales

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

    Learn more

    from Attio

    Attio to Meta Offline CAPI

    Meta Offline CAPI for Attio: 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 Attio Google OCI sync run?

    The pace follows your Attio workspace lists: Signals sends changes from Attio to Google Ads as records change. Because it sends only the records that changed, Smart Bidding trained on booked revenue instead of a mid-funnel proxy stays current while RevOps teams running Attio keep GCLID coverage in view. Delivery needs no export and no manual upload.

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

    Coverage of hashed identifiers across your Attio workspace lists decides it, and RevOps teams running Attio own that inside Attio. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags GCLID coverage, which RevOps teams running Attio then raise inside your Attio workspace lists.

    NEXT STEP

    Attio to Google OCI, in production this week.

    Talk to our team All Attio use cases