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

    CONNECTIONS / Kommo / Kommo to Google OCI

    Your Kommo messenger pipelines, wired to Google Ads offline conversion import.

    Connect Kommo and point Signals at your Kommo messenger 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

    kommo -> google-oci :: live

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

    WHAT THIS ENABLES

    Kommo to Google Offline Conversions

    Kommo to Google Offline Conversions: your Kommo messenger 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 Kommo messenger 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 Kommo messenger pipelines by conversational-sales teams on Kommo.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google CRM record sync recorded in Kommo 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 Kommo leads and messenger-driven pipelines.

    Conversational-sales teams on Kommo activating Google Ads offline conversion import straight from Kommo messenger pipelines.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      Signals reads your Kommo messenger 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 Kommo messenger 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 Kommo records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: kommo.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=kommo.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-15T22:50:32"
    5. conversion_value 21067 · currency_code AED
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Kommo

    Kommo to Google Store Sales

    Kommo to Google Store Sales: your Kommo messenger pipelines, hashed and consent-checked,…

    Learn more

    from Kommo

    Kommo to Meta Offline CAPI

    Kommo to Meta Offline CAPI: your Kommo messenger 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 Kommo Google OCI sync run?

    Delivery tracks Kommo, run by conversational-sales teams on Kommo: a near-real-time or scheduled sync of your Kommo messenger pipelines 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 Kommo-sourced Google OCI batch expect?

    Match rate follows identifier coverage in your Kommo messenger pipelines, which conversational-sales teams on Kommo control, not Kommo 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 conversational-sales teams on Kommo tune against.

    NEXT STEP

    Kommo to Google OCI, in production this week.

    Talk to our team All Kommo use cases