Skip to content
  1. Home
  2. How KO works
  3. Leads from forms
How KO works

Leads from forms

A request and its source reach KO in two separate ways. The request must always arrive. The source is added to it by the visit ID from the tracking script. This decides which method fits your platform. It also explains why a form is still sent when a visitor says no to analytics, only without a source.

In short

  • A request and its source are two halves The form gives the contact details, the visit gives the campaign. The visit ID links them.
  • The method depends on the platform Webhook if you have access to the server or the form platform. Interception if you do not.
  • Site builders and SPAs are covered The script does not need a form tag, and it finds forms that appear later.
  • Saying no to analytics does not lose the request The request is sent, the visit and the source are not. The lead arrives without a campaign.

A request and its source are two halves

Every request has two halves. The contact details (name, email, phone) come from the form. Where the person came from (campaign, ad, keyword) comes from the visit that the tracking script recorded.

The visit ID links the two. The tracking script gives it to the visitor, and it is sent with the request. With the ID, KO finds the visit and its source. Without it, the lead still arrives, but with no campaign. How KO looks for the visit when there is no ID is explained in How a lead finds its visit.

This gives one rule: never lose a request; a source is good to have, but a lead without one is still a lead. A lead without a source still reaches the CRM and the lead reports. A lost lead reaches nothing.

Three ways to deliver a request

You choose the method in the “Website: tracking & events” connect, in the “How submissions are received” setting.

One form

A visitor sends a request

contact details + visit ID

the ID is there if the tracking script gave one

How the request reaches KO

Webhook
sent by the site's server or the form platform
server
Silent form interception
the form works as before, a copy goes to KO
browser
Standard form handling
KO takes the request and shows a message
browser
The tracking script records visits in every case. The method only decides how the request itself arrives
  • Webhook. The site’s server or the form platform sends the request. The browser is not part of it, so an ad blocker, a cookie banner or a slow page cannot stop the request.
  • Silent form interception. If you have no access to the server, the tracking script reads the form when it is sent. The form works as before and goes where it always went. KO gets a copy.
  • Standard form handling. For a simple site with no form handler of its own: KO receives the request and shows the visitor a message that it was sent.

The webhook is the most reliable, interception is the easiest. So the choice depends on what you can change. Access to the server or the form platform: use the webhook. Only the page code: use interception.

One request, one path. If the site already sends requests to a CRM and that CRM is connected to KO, a second path from the same form creates a copy of the lead.

Site builders and SPAs

On site builders (Webflow, Framer, WordPress with form plugins) and in single-page apps, a form often does not look like a textbook HTML form. Interception is built for this.

  • A form does not have to be a <form> tag. The tracking script finds forms by a CSS selector. You can change it in the “Finding forms on the site (CSS selector)” setting.
  • A button click can count as the send. Site builders often send the form with their own script, so the browser never sees a submit event. In that case a click on the button, or Enter, counts as sending. For known site-builder forms the script chooses this on its own. To set it by hand, use “How form submission is tracked”.
  • Forms that appear later are found too. A popup, the next step of a quiz, a new SPA screen: the script keeps looking for new forms while the page is open. Each form is connected once.
  • Interception cancels nothing. The script only reads the data. It does not stop the send and does not touch the site’s own handlers.

The tracking script also sees moves inside an SPA: each new address is a new page view. More in the help article Custom events from a single-page app.

Not every form sent is a lead. A newsletter signup or a site search is a form too. A send becomes a lead only if it has a contact and its form type is selected in “Form types whose submission counts as a lead”. Other sends are recorded in the visit as events. The script never reads passwords.

The cookie banner decides whether analytics is allowed. The KO tracking script does not read the banner itself: the site passes the visitor’s choice to it. Until there is a choice, the script works as usual.

Consent given, or no signal yet

What reaches KO with the form

RequestVisitSource

the lead arrives with the campaign that brought it

The visitor said no to analytics

What reaches KO with the form

RequestVisitSource

the lead arrives without a source

A no to analytics turns off visits and cookies, but not the request itself

If the visitor says no to analytics, the script stops recording visits and sets no cookies. The request is still sent. The person asked to be contacted, and losing that request is worse than losing statistics. The request reaches KO, but no visit is attached to it.

If the banner on the site blocks the KO script itself until consent, nothing is left to intercept the form: the script simply does not load. A webhook from the server is not affected.

This is a product decision, not a legal assessment. The site owner decides on what basis the site processes a request and what the banner says. How to pass the visitor’s choice to the script is in the help article The cookie banner and the KO counter — passing consent. What the script does for each answer is in Cookies and consent.

In practice

  • A request and its source are two halves. The form gives the contact, the visit gives the campaign, the visit ID links them.
  • Access to the server or the form platform: webhook. Otherwise: interception. With a webhook, send the visit ID yourself.
  • Interception works on site builders and SPAs: forms are found by selector, a button click can count as the send, new forms are picked up.
  • A no to analytics does not lose the request, but the lead arrives without a source.
  • How to connect is in the help article Connect a website — tracking script and webhook.

Updated

Demo

Imagine your project is already in KO

The demo is the project of a made-up company. Its ads, website and CRM are already connected. Reports, decisions and data checks work on its numbers just as they would on yours.

See it live

No sign-up, no payment