A custom-built website, an in-house CRM, a back-office script: there is no ready integration for them. For these cases, there is a webhook. Your code sends a lead to the KO address. KO links the lead to the visit and the campaign, like a request from a regular form.
What KO takes
Terms on this page: Lead, Attribution
A lead came without a visit or tags
The source of a lead is the visit it came from. The visit ID is in the KO tracking cookie. If your code sends neither the ID nor UTM tags, the lead goes into the share with no source.
The contact is already in KO
KO does not create the same contact twice. The reply returns the ID of the known contact and marks it as a duplicate. This is normal, not an error.
The channel has its own name
KO understands a channel only if it is on the KO list. If the value is not on the list, the request still goes through. But the lead goes to an unknown channel.
Requests stopped coming
The integration settings show the latest requests. If requests stop coming while other data keeps coming, a card appears in What to do now.
In the demo, ad accounts, a CRM and a website already feed the same reports. Open them and see what you learn when spend, leads and deals are in one place.
No sign-up, no payment
See what to cut, fix, and scale — using your real data.
You'll meet the founders, not a sales rep — we built KO after years of running growth on broken numbers.
