Jump to a popular page, or start typing.

    CONNECTIONS / Kommo / Kommo to TikTok Offline eAPI

    Your Kommo messenger pipelines, wired to TikTok's Offline Events API.

    Connect Kommo and point Signals at your Kommo messenger pipelines; it sends register and phone sales so offline joins TikTok's web optimization as records change, hashed and consent-checked for TikTok.

    kommo -> tiktok-offline-eapi :: live

    1. ● kommo → tiktok.eapi :: live
    2. > read closed_deals rows=9,644
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 8,583 matched

    WHAT THIS ENABLES

    Kommo to TikTok Offline Events API

    Kommo to TikTok Offline Events API: your Kommo messenger pipelines, hashed and consent-checked, feed TikTok as Signals sends register and phone sales so offline joins TikTok's web optimization as records change.

    • Offline and in-store sales from your Kommo messenger pipelines activated for TikTok, as Signals sends register and phone sales so offline joins TikTok's web optimization.
    • Counter sales deduped against any TikTok web event for the same buyer, 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 TikTok, away from any pixel. Here is how Kommo closes the loop.

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

    Built for the teams that own the number.

    Brands whose TikTok conversions finish at a till, not a checkout, with the records already in Kommo leads and messenger-driven pipelines.

    Conversational-sales teams on Kommo activating TikTok's Offline Events API 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 TikTok's Offline Events API, sized for web-to-offline deduplication.

    2. Map

      Signals reads your Kommo messenger pipelines, and its columns map to TikTok's Offline Events API in the visual mapper, hashed and checked for web-to-offline deduplication.

    3. Deliver

      On each run, Signals pulls your Kommo messenger pipelines, sends register and phone sales so offline joins TikTok's web optimization, and sends only the records that changed, with web-to-offline deduplication 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 eAPI 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 eAPI actually receives.

    signals :: kommo.tiktok-offline-eapi :: wire

    1. ● signals :: event payload
    2. > POST /event/track source=kommo.closed_deals
    3. event "CompletePayment" · event_time 1784655207
    4. user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
    5. properties.value 36088 · properties.currency SAR
    6. ✓ accepted · dedupe=event_id
    FAQ

    Asked on almost every call.

    How often does the Kommo TikTok Offline eAPI 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 TikTok on that cadence. Each run sends only the records that changed, so a unified web-and-offline conversion view holds up on web-to-offline deduplication. The live debugger confirms every delivery inline.

    What match rate should a Kommo-sourced TikTok Offline eAPI 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 TikTok; one missing both cannot. First-run feedback from Offline Events API pinpoints web-to-offline deduplication, the number conversational-sales teams on Kommo tune against.

    NEXT STEP

    Kommo to TikTok Offline eAPI, in production this week.