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

    CONNECTIONS / Insightly / Insightly to Google OCI

    From Insightly opportunities and pipeline stages to Google Ads offline conversion import.

    Connect Insightly and point Signals at your Insightly opportunities and pipeline stages; 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

    insightly -> google-oci :: live

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

    WHAT THIS ENABLES

    Insightly to Google Offline Conversions

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

    • Offline and in-store sales from your Insightly opportunities and pipeline stages 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 Insightly opportunities and pipeline stages by RevOps teams running Insightly.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google CRM record sync recorded in Insightly 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 Insightly opportunities, projects, and pipeline stages.

    RevOps teams running Insightly activating Google Ads offline conversion import straight from Insightly opportunities and pipeline stages.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Insightly, reading only your Insightly opportunities and pipeline stages to feed Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      Signals reads your Insightly opportunities and pipeline stages, 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 Insightly opportunities and pipeline stages, 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 Insightly records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: insightly.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=insightly.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-17T08:18:58"
    5. conversion_value 14230 · currency_code GBP
    6. ✓ accepted · batch=nightly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Insightly

    Insightly to Google Store Sales

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

    Learn more

    from Insightly

    Insightly to Meta Offline CAPI

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

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

    Delivery tracks Insightly, run by RevOps teams running Insightly: a near-real-time or scheduled sync of your Insightly opportunities and pipeline stages feeds Google Ads on that cadence. Each run sends only the records that changed, 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 Insightly-sourced Google OCI batch expect?

    Match rate follows identifier coverage in your Insightly opportunities and pipeline stages, which RevOps teams running Insightly control, not Insightly itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Offline Conversion Import (Google Ads API) pinpoints GCLID coverage, the number RevOps teams running Insightly tune against.

    NEXT STEP

    Insightly to Google OCI, in production this week.

    Talk to our team All Insightly use cases