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

    CONNECTIONS / Close / Close to Google OCI

    Close smart-view opportunities into Google Ads, built for Google Ads offline conversion import.

    Signals reads your Close smart-view opportunities through scoped OAuth access to Close, reading only your Close smart-view opportunities, 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

    close -> google-oci :: live

    1. ● close → google.oci :: live
    2. > read closed_deals rows=70,750
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 60,138 matched

    WHAT THIS ENABLES

    Close to Google Offline Conversions

    Close to Google Offline Conversions: your Close smart-view opportunities, hashed and consent-checked, feed Google Ads as Signals reconciles closed-won revenue to the Google Ads click through GCLID as records change.

    • Signals reconciles closed-won revenue to the Google Ads click through GCLID, reading your Close smart-view opportunities as records change.
    • A clean line from click to closed revenue, with no export step out of your Close smart-view opportunities.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google CRM record sync recorded in Close 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 Close leads, calls, and smart-view opportunities.

    Inside-sales teams running Close who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy out of Close smart-view opportunities.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Close, reading only your Close smart-view opportunities, mapped to Google Ads' Offline Conversion Import (Google Ads API) and tuned for GCLID coverage.

    2. Map

      Columns from your Close smart-view opportunities align to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed as the sync runs and checked for GCLID coverage.

    3. Deliver

      As records change, Signals reads your Close smart-view opportunities and reconciles closed-won revenue to the Google Ads click through GCLID, sends only the records that changed, 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 Close records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: close.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=close.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-16T13:46:47"
    5. conversion_value 16288 · currency_code SAR
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Close

    Close to Google Store Sales

    Close to Google Store Sales: your Close smart-view opportunities, hashed and…

    Learn more

    from Close

    Close to Meta Offline CAPI

    Close to Meta Offline CAPI: your Close smart-view opportunities, hashed and…

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

    The pace follows your Close smart-view opportunities: Signals sends changes from Close 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 inside-sales teams running Close keep GCLID coverage in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    Close to Google OCI, in production this week.

    Talk to our team All Close use cases