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

    CONNECTIONS / Kommo / Kommo to Google Customer Match

    Your Kommo messenger pipelines, wired to Google Customer Match.

    Connect Kommo and point Signals at your Kommo messenger pipelines; it projects your segments into Google Ads as Customer Match lists as records change, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    kommo -> google-customer-match :: live

    1. ● kommo → google.match :: live
    2. > read segments rows=55,587
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 48,917 matched

    WHAT THIS ENABLES

    Kommo to Google Customer Match

    Kommo to Google Customer Match: your Kommo messenger pipelines, hashed and consent-checked, feed Google Ads as Signals projects your segments into Google Ads as Customer Match lists as records change.

    • Customer segments from your Kommo messenger pipelines activated for Google Ads, as Signals projects your segments into Google Ads as Customer Match lists.
    • Customer Match lists that add joiners and drop lapsed members each sync, drawn from your Kommo messenger pipelines by conversational-sales teams on Kommo.

    WHAT FLOWS WHERE

    Kommo to Customer Match, mapped.

    Each sync hands the customer segments from your Kommo messenger pipelines to Signals, which hashes and filters every record, then Google Ads' Customer Match API logs the match-ready audiences for the serving-size threshold.

    Each sync hands the customer segments from your Kommo messenger pipelines to Signals, which hashes and filters every record, then Google Ads' Customer Match API logs the match-ready audiences for the serving-size threshold.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Growth teams feeding Google audiences from governed first-party data, with the records already in Kommo leads and messenger-driven pipelines.

    Conversational-sales teams on Kommo activating Google Customer Match 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' Customer Match API, sized for the serving-size threshold.

    2. Map

      Signals reads your Kommo messenger pipelines, and its columns map to Google Ads' Customer Match API in the visual mapper, hashed and checked for the serving-size threshold.

    3. Deliver

      On each run, Signals pulls your Kommo messenger pipelines, projects your segments into Google Ads as Customer Match lists, and sends only the records that changed, with the serving-size threshold in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Customer Match lists that add joiners and drop lapsed members each sync on every run, as Signals reads your Kommo messenger pipelines and sends only the records that changed.

    Lists that self-maintain across syncs from your Kommo messenger pipelines, with API call volume steady because Signals sends only the records that changed.

    A per-run match report from Google Ads' Customer Match API on the serving-size threshold, straight out of your Kommo messenger pipelines.

    ON THE WIRE

    What Customer Match actually receives.

    signals :: kommo.google-customer-match :: wire

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=kommo.segments
    3. operation ADD · user_list "segment_50067"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 55,587 · members_matched 48,917
    6. ✓ accepted match=88%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Kommo

    Kommo to Meta Custom Audience

    Kommo to Meta Custom Audience: your Kommo messenger pipelines, hashed and consent-checked,…

    Learn more

    from Kommo

    Kommo to TikTok Custom Audience

    Kommo to TikTok Custom Audience: your Kommo messenger pipelines, hashed and…

    Learn more

    same use case

    ActiveCampaign to Google Customer Match

    ActiveCampaign to Google Customer Match: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Google Customer Match

    Datahash builds and refreshes Google Customer Match audiences from your CRM, warehouse, or…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Kommo Google Customer Match 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 lists that self-maintain across syncs holds up on the serving-size threshold. The live debugger confirms every delivery inline.

    What match rate should a Kommo-sourced Google Customer Match 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 Customer Match API pinpoints the serving-size threshold, the number conversational-sales teams on Kommo tune against.

    NEXT STEP

    Kommo to Google Customer Match, in production this week.

    Talk to our team All Kommo use cases