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.eapi :: live
- > read closed_deals rows=9,644
- hash sha256(email,phone) consent=filtered
- route tiktok deliver
- ✓ 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.
The click, the conversion, and the credit.
The conversion happens off TikTok, away from any pixel. Here is how Kommo closes the loop.
Built for the teams that own the number.
Conversational-sales teams on Kommo activating TikTok's Offline Events API straight from Kommo messenger pipelines.
From kickoff to verified events.
-
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.
-
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.
-
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 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. |
What Offline eAPI actually receives.
- ● signals :: event payload
- > POST /event/track source=kommo.closed_deals
- event "CompletePayment" · event_time 1784655207
- user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
- properties.value 36088 · properties.currency SAR
- ✓ accepted · dedupe=event_id
Adjacent moves on the same stack.
from Kommo
Kommo to Google OCI
Kommo to Google Offline Conversions: your Kommo messenger pipelines, hashed and…
Learn morefrom Kommo
Kommo to Google Store Sales
Kommo to Google Store Sales: your Kommo messenger pipelines, hashed and consent-checked,…
Learn moresame use case
ActiveCampaign to TikTok Offline eAPI
ActiveCampaign to TikTok Offline Events API: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
TikTok Offline eAPI
Move your in-store and call-centre conversions to TikTok server-side, so TikTok can…
Learn moreAsked 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