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

    CONNECTIONS / Kommo / Kommo to Meta Offline CAPI

    Your Kommo messenger pipelines, wired to Meta's offline optimization.

    Connect Kommo and point Signals at your Kommo messenger pipelines; it credits dealer, branch, and phone sales to the Meta campaigns behind them as records change, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    kommo -> meta-offline-capi :: live

    1. ● kommo → meta.capi :: live
    2. > read closed_deals rows=32,986
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 27,049 matched

    WHAT THIS ENABLES

    Kommo to Meta Offline CAPI

    Kommo to Meta Offline CAPI: your Kommo messenger pipelines, hashed and consent-checked, feed Meta as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them as records change.

    • Offline and in-store sales from your Kommo messenger pipelines activated for Meta, as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them.
    • In-store and phone revenue joining Meta's optimization loop, 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 Meta, away from any pixel. Here is how Kommo closes the loop.

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta CRM record sync recorded in Kommo S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Considered-purchase brands closing revenue far from the browser, with the records already in Kommo leads and messenger-driven pipelines.

    Conversational-sales teams on Kommo activating Meta's offline optimization 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 Offline Conversions API, sized for Meta's 62-day event window.

    2. Map

      Signals reads your Kommo messenger pipelines, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.

    3. Deliver

      On each run, Signals pulls your Kommo messenger pipelines, credits dealer, branch, and phone sales to the Meta campaigns behind them, and sends only the records that changed, with Meta's 62-day event window 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 Offline CAPI 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 Offline CAPI actually receives.

    signals :: kommo.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=kommo.closed_deals
    3. event_name "Purchase" · event_time 2026-07-16T02:48:20
    4. value 21250.00 · currency AED
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-77100"
    6. ✓ accepted match=82%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Kommo

    Kommo to Google OCI

    Kommo to Google Offline Conversions: your Kommo messenger pipelines, hashed and…

    Learn more

    from Kommo

    Kommo to Google Store Sales

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

    Learn more

    same use case

    ActiveCampaign to Meta Offline CAPI

    ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Offline CAPI

    Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Kommo Meta Offline CAPI 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 campaign learning fed by real-world purchases holds up on Meta's 62-day event window. The live debugger confirms every delivery inline.

    What match rate should a Kommo-sourced Meta Offline CAPI 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 Offline Conversions API pinpoints Meta's 62-day event window, the number conversational-sales teams on Kommo tune against.

    NEXT STEP

    Kommo to Meta Offline CAPI, in production this week.

    Talk to our team All Kommo use cases