CONNECTIONS / Kommo
Kommo + Datahash: chat leads become ad signals.
A Kommo lead as often starts in a WhatsApp thread as a web form, and ad platforms cannot see either side of that conversation. Signals reads pipeline status changes and contact records and turns them into conversion events and audiences on the platforms you run.
- ● kommo :: signals live
- > read leads pipeline=sales status=won rows=2,015
- > read contacts channel=whatsapp
- hash sha256(phone,email) scope=leads.read
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 74%
The signal Kommo yields, and receives.
Every kind of signal that moves between Kommo and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A pipeline status change, whether the lead started as a web form or a WhatsApp reply, posts as a conversion event the moment it moves.
- Lead conversions
- Closed-won value leaves Kommo hashed and lands back on the campaign that drove the original chat or form.
- Custom audiences
- Phone numbers, the identifier most Kommo leads actually carry, hash alongside email for matching, so a chat-only lead is not a dead end for audiences.
- Lead generation inbound
- A lead qualified out of Unsorted into a real pipeline starts flowing from that point, so unqualified chat noise never reaches a destination.
Pick your platform. Every use case for it, in one place.
Every way Kommo data moves, grouped by platform and ranked by how many use cases Kommo supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect Kommo with a scoped integration user, revocable from account settings at any time.
-
Map statuses
Match each pipeline status, custom ones included, to a platform event in the visual mapper.
-
Hash and consent
Hashing and consent checks run before a record leaves Kommo.
-
Deliver
Mapped destinations receive events on delivery, with per-status match reporting.
Kommo questions, answered.
Most of our leads arrive over WhatsApp, not a form. Does that still work?
Yes. Kommo stores a WhatsApp lead as a normal Lead and Contact record once it exists, and Signals reads that record the same way it reads one that started as a form fill. The phone number hashes alongside email, so a chat-first pipeline still matches to ad platform audiences without any special handling.
Do unqualified leads sitting in Unsorted get synced?
No, not unless you choose to. Signals reads leads once they are assigned to a pipeline, so the Unsorted inbox, where unclassified chats and form submissions land before anyone reviews them, does not flow anywhere until a person or automation moves a lead into a real stage.
Can Kommo's Digital Pipeline automations trigger a sync?
Yes. Digital Pipeline moves a lead through statuses automatically, and Signals reacts to the resulting status change exactly as it would to a manual one. The mapper does not need to know whether a human or an automation caused the move, only which status was reached and what it should mean.
NEXT STEP
See your Kommo data working in every ad platform.
Ready to enable a use case, or still mapping what Kommo data could do? Our team helps you find the right place to start.
