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

    CONNECTIONS / Kommo / Kommo to Meta Custom Audience

    Your Kommo messenger pipelines, wired to Meta lookalike and suppression seeds.

    Connect Kommo and point Signals at your Kommo messenger pipelines; it keeps Meta audiences synced as adds and removals so lists never drift as records change, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    kommo -> meta-custom-audience :: live

    1. ● kommo → meta.audience :: live
    2. > read segments rows=55,940
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 43,633 matched

    WHAT THIS ENABLES

    Kommo to Meta Custom Audience

    Kommo to Meta Custom Audience: your Kommo messenger pipelines, hashed and consent-checked, feed Meta as Signals keeps Meta audiences synced as adds and removals so lists never drift as records change.

    • Customer segments from your Kommo messenger pipelines activated for Meta, as Signals keeps Meta audiences synced as adds and removals so lists never drift.
    • Lookalike seeds and suppression lists that track your live customer base, drawn from your Kommo messenger pipelines by conversational-sales teams on Kommo.

    WHAT FLOWS WHERE

    Kommo to Custom Audience, mapped.

    Each sync hands the customer segments from your Kommo messenger pipelines to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs the match-ready audiences for audience refresh cadence.

    Each sync hands the customer segments from your Kommo messenger pipelines to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs the match-ready audiences for audience refresh cadence.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Performance teams running first-party suppression and lookalike seeds, with the records already in Kommo leads and messenger-driven pipelines.

    Conversational-sales teams on Kommo activating Meta lookalike and suppression seeds 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 Meta's Custom Audiences API, sized for audience refresh cadence.

    2. Map

      Signals reads your Kommo messenger pipelines, and its columns map to Meta's Custom Audiences API in the visual mapper, hashed and checked for audience refresh cadence.

    3. Deliver

      On each run, Signals pulls your Kommo messenger pipelines, keeps Meta audiences synced as adds and removals so lists never drift, and sends only the records that changed, with audience refresh cadence in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lookalike seeds and suppression lists that track your live customer base on every run, as Signals reads your Kommo messenger pipelines and sends only the records that changed.

    Always-current lookalike seeds and exclusions from your Kommo messenger pipelines, with API call volume steady because Signals sends only the records that changed.

    A per-run match report from Meta's Custom Audiences API on audience refresh cadence, straight out of your Kommo messenger pipelines.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: kommo.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=kommo.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 55,940 · num_invalid_entries -3
    5. audience_id "1666535" · session "upsert"
    6. ✓ accepted match=78%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Kommo

    Kommo to Google Customer Match

    Kommo to Google Customer Match: 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 Meta Custom Audience

    ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Custom Audience

    Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Kommo Meta Custom Audience 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 Meta on that cadence. Each run sends only the records that changed, so always-current lookalike seeds and exclusions holds up on audience refresh cadence. The live debugger confirms every delivery inline.

    What match rate should a Kommo-sourced Meta Custom Audience 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 Meta; one missing both cannot. First-run feedback from Custom Audiences API pinpoints audience refresh cadence, the number conversational-sales teams on Kommo tune against.

    NEXT STEP

    Kommo to Meta Custom Audience, in production this week.

    Talk to our team All Kommo use cases