In short
A person sees a Google Ads ad and looks at the site. A week later they read a LinkedIn post and come back. A week after that they open a newsletter email, follow the link and send a lead. Whose lead is it?
In a KO report the lead belongs to the newsletter: the person sent it during the visit from the email. In a breakdown by tags you can turn on participation. Then all three channels get the lead, and the total stays one lead.
One person's path: a Google Ads ad, a LinkedIn post, a newsletter email, then a lead
"Total" is 1 lead in both modes. The sum of rows: 1 with last touch and 3 with participation.
Last touch is the report model
A lead goes to the source of the visit where it was sent. Every report, every plan and every lead metric counts this way unless you switch something.
In KO the last touch is the last source, not the last time the person opened the site. A direct visit and time do not end a visit. So if a person clicked an ad, came back three days later from a bookmark and sent a lead, the lead stays with the ad. Why it works this way is in A visit ends when the source changes.
Participation: how many paths went through a channel
KO stores the lead’s path: the sources the person came from in this browser before the lead, in order. Each set of tags is in the path once: however many times the person came back from one campaign, the path has it once.
The Breakdown section has the “Lead attribution” option. By default it is “As in the report (last touch)”. If you choose “Show participation”, the lead goes whole to each source in its path.
- The sum of rows is bigger than the total. One lead with three channels in its path adds one to each of three rows.
- “Total” does not change. The total counts unique leads, and the model does not affect it.
- It works in a breakdown by UTM tags — by source, medium, campaign, content and term. The combined “Source” field does not depend on the model.
How to read the range
When a row’s participation is much bigger than its last-touch leads, the Breakdown section shows a range, for example “12–30”. The first number is last-touch leads, as in the report. The second is the leads whose path included this row. The hint over the number says the same in words: “Last touch: 12. Took part in the path: 30.”
The hint also shows the row’s role. If the row gets most of the leads it took part in, it mostly closes: people come from it and send a lead. If it gets fewer, it mostly assists, and a last-touch report undervalues it.
If the numbers are close, there is no range: the row shows one number as usual.
How to make a decision from the range
A last-touch report tells you which channel brings leads. The range answers another question: what you lose if you remove the channel.
- It closes: judge it by the report. A narrow range or one number means the channel brings leads by itself, and the cost per lead in the report is fair for it.
- It assists: do not cut it because of the cost per lead in the report. Such a channel has few last-touch leads, so its lead looks expensive in the report. But people from it send leads later through other channels. Turn it off, and those channels get fewer leads too.
- Zero leads in the report does not mean zero value. Before you turn off a campaign with no leads, turn on participation. If the campaign is in the leads’ paths, it works for other channels.
With participation, cost per lead and ROMI are shown as a range too. For cost per lead the ends swap: the low end is spend divided by all leads whose path included the channel, and the high end is spend divided by last-touch leads. The high end is strict: the channel gets nothing for assisting. The low end is generous: every lead the channel took part in counts for it in full. The real cost of the channel is between them.
If such a metric has a plan, a mark next to the range shows how it compares:
- Green: the plan is met already by last touch. The channel pays off by itself.
- Yellow: the plan is met only if you count participation. The channel pays off together with the channels it helps. You can cut it, but then check that other channels did not drop.
- Red: the plan is not met even with participation. Review the channel.
When the models match
- A path with one source. The person came once and sent a lead, so there is nothing to share.
- The lead has no path. The lead came from a call, a messenger or the CRM without a visit to the site. Then participation equals last touch, and switching the model does not add “(not set)” rows.
- Old leads. The path is stored for leads recorded after KO started to collect it. For earlier leads the models match.
Spend does not depend on the model
Spend, clicks and impressions have one touch by definition: a click is the touch. There is nothing to share, so these metrics have no model. The model belongs to lead metrics, not to the whole report.
If you need another model
The decision above is about the default model for all projects. If your project needs another one, for example first touch for campaigns that look for new customers, or your own rule for splitting, write to us. We will talk about which question the model should answer, and we can add it for your project. Most likely it will sit next to the report, like participation, not replace it. This way the numbers in the report and the plan stay the same.
Summary
- Reports, plans and lead metrics in KO count by the last touch: the source of the visit where the lead was sent.
- In the Breakdown section by tags you can turn on participation: the lead goes to each channel in its path, and “Total” does not change.
- A range like “12–30” shows how much a channel helps others and hints at its role.
- A closing channel is judged by the report. An assisting channel is not cut because of the cost per lead in the report, and the plan mark shows if a channel pays off by itself or together with others.
- A lead is not split into shares, and spend does not depend on the model.
- By default there are no other models on purpose: they give numbers that match neither the report nor the plan. If a project needs another model, we can discuss it and add it.
Updated