Skip to content

Product

Every session, scored on whether it meant it.

Analytics has always been able to tell you a visit happened. Intent scoring tells you what kind of visit it was — measured against the one thing your business actually needs people to do.

In one paragraph

An intent score is a number from 0 to 100 assigned to a single website session, representing how closely that session's behaviour resembled sessions that went on to convert. It is produced by a model trained on a site's own first-party behavioural data against a single, business-defined conversion event. Unlike engagement metrics, which measure activity, an intent score measures resemblance to a commercial outcome.

01

Why counting stops working

Every analytics tool answers the question “was this traffic any good?” the same way: it counts the conversions that came from it. That works beautifully at scale and falls apart everywhere else.

Consider a channel that sent 400 sessions and produced one sale. Is that a 0.25% conversion rate, or is it one lucky sale from traffic that was worthless? With one data point you cannot tell, and you will not be able to tell next month either — you will have two data points. Meanwhile the spend continues.

The problem is that conversions are rare events, and rare events are terrible units of measurement at small sample sizes. But the sessions themselves are not rare. Four hundred sessions is a lot of behaviour. The information is there; counting just throws almost all of it away.

02

What scoring does instead

Intent scoring uses the behaviour rather than the outcome. Every one of those 400 sessions gets evaluated against the pattern your converting sessions have historically shown, and gets a number.

Now the question changes shape. Instead of “one sale from 400 sessions”, you have a distribution: perhaps 12 sessions scoring above 70 and 340 scoring below 20. That is a channel bringing a small amount of real interest. Or perhaps nothing above 30 at all — which tells you, from a single month and one sale, that this channel is not bringing buyers and the sale was incidental.

The same reasoning runs the other way. A source with no conversions at all but a healthy tail of high-scoring sessions is usually a landing-page or offer problem, not a traffic problem — and that is a completely different fix from turning the channel off.

03

What the score is built from

Only behaviour observed on your own site. There is no third-party intent data, no company identification and no cross-site profile.

  • Reading depth. How far through the page the visitor actually got, per page, rather than whether the page loaded.
  • Attention. Active time versus idle time, and whether the tab was switched away from. A page open for nine minutes in a background tab is not nine minutes of interest.
  • Path shape. Which pages, in what order. The move from a feature page to pricing means something different from the reverse.
  • Pace and depth of visit. Pages per session, session duration, and how the visit accelerated or stalled.
  • History. Whether this browser has been here before, and what its earlier sessions looked like.

The model learns which combinations of these preceded conversion on your site. That last part matters more than the signal list: the same behaviour means different things on a checkout funnel and on a considered B2B purchase, which is why a general-purpose engagement score cannot do this job.

04

Why the model is deliberately simple

The scoring model is a well-understood statistical one rather than something exotic, and that is a deliberate constraint rather than a limitation we are apologising for.

It trains reliably on the amount of data a normal business has, instead of needing the volumes a deep model would demand. Its outputs can be explained signal by signal, so you can see why a score moved. And when it is wrong, it is wrong in ways you can inspect — which is the difference between a tool you come to trust and a black box you quietly stop opening.

It is also validated before it is ever shown. Each trained model is tested against data it has not seen, and if it cannot separate converting from non-converting sessions well enough, it does not go live. The reporting says the model is not ready. That is a worse day for us and a better one for you.

What it changes

From a traffic report to a shortlist.

Scores are only useful because of what they let you rank. Once every session carries one, every channel, campaign and landing page can be graded on the intent it brings rather than the volume.

This is the same set of sources under both rankings. Nothing about the traffic changed — only the question being asked of it.

  • 01Paid social18,400sessions
  • 02Organic search12,900sessions
  • 03Paid search — non-brand9,600sessions
  • 04Direct6,200sessions
  • 05Paid search — brand3,100sessions
  • 06Email2,400sessions
  • 07Partner referral1,150sessions

Illustrative figures · not customer data

05

What an intent score is not

The category overclaims, so we would rather draw these lines ourselves than let them be assumed.

  • Not a prediction about a person. It is a comparison across a population. A session scoring 90 may never return. The number is for ranking, not fortune telling.
  • Not incrementality. A channel bringing high intent may be harvesting demand you created elsewhere. Brand search is the classic case. Scoring tells you where intent showed up, not who caused it.
  • Not identity. No cross-site tracking, no company lookup, no third-party intent feed. It cannot tell you which company visited.
  • Not causal. The model learns which behaviours accompanied conversion. It cannot tell you that manufacturing more of a behaviour would produce more conversions.
  • Not zero-data. It needs some conversion history to learn from. Far less than the alternatives, but not none.
06

Compared with what you already have

Google Analytics does have predictive metrics, and they are good at what they are for. But a property only becomes eligible once at least 1,000 returning users have triggered the event and 1,000 have not, inside 28 days — roughly 33,000 to 50,000 returning sessions a month at typical ecommerce conversion rates. It predicts purchase or churn specifically, at user level, for the next seven days, and it exists mainly to build remarketing audiences.

Privacy-first analytics — Plausible, Fathom, Umami, Matomo — report traffic accurately and cheaply and do not attempt scoring at all. If clean traffic reporting is what you need, they are the better buy and we will say so.

B2B intent platforms — 6sense, Demandbase, Bombora and others — score accounts, not sessions, using third-party intent data and company identification. Different data, different unit, enterprise pricing, and only useful if you sell to companies.

Questions

Common questions.

What exactly is an intent score?

A number from 0 to 100 assigned to a single session, representing how closely that session's behaviour resembled sessions that went on to complete your conversion event. It is a comparison against your own history, not a universal scale — a 70 on your site does not mean the same thing as a 70 on someone else's.

What signals go into it?

Observable behaviour on your site: how far through pages the visitor read, how much of their time on page was active rather than idle, whether they switched away and came back, how many pages they moved through, the order and type of pages in the path, and the pace of the visit. No personal data, no third-party data, no company identification.

Why not just use engagement rate?

Because engagement rate has no idea what your business sells. It measures whether somebody stayed. A visitor reading your careers page carefully is highly engaged and has zero buying intent. Intent scoring is trained against your conversion event, so it learns which kinds of engagement precede a sale on your site specifically.

How much conversion history do you need?

About 50 conversions is the point at which we can train a model we trust, against the 1,000 Google Analytics requires. Below 50 we say so rather than showing a score we do not stand behind. We check this on the scoping call, before quoting anything.

How do you know the score is any good?

The model is validated on data it has not seen. If it cannot separate converting from non-converting sessions better than a stated threshold, we do not ship it — the reporting says the model is not ready instead. We would rather show nothing than a confident-looking number that is noise.

Can we see why a session scored what it did?

Yes. The model is a simple, explainable one for exactly this reason. You can see which signals pushed a score up or down, which is what makes it possible to trust it, argue with it, or find a measurement bug behind it.

Does a high score mean that visitor will buy?

No, and we will not let that be implied. A score is a comparison across a population, useful for ranking and for grading traffic sources. It is not a forecast about an individual person, and anyone selling it that way is overclaiming.

See what your traffic actually scores.

Thirty minutes on your site, your conversion event, and whether you have enough history to score against.