# Score-based audiences

URL: https://kywi-docs-production.up.railway.app/targeting/score-based-audiences
Type: docPage

A threshold changes what an audience means — and five of the six ways to earn points only work if your site runs the optional browser runtime.

A score threshold isn't a separate kind of audience — it's a property you add to an ordinary one, and adding it changes what "match" means for that audience alone.

## Check this first: does your site run the browser runtime?

It decides whether a score audience can work at all, so it isn't a footnote. Five of the six ways to earn points — Page View Count, Total Page Views, Time on Site, Category Viewed and URL Match — read behaviour collected in the visitor's browser by Kywi's optional runtime, and that runtime is off unless your site has turned it on. Only Signal Match, which reuses an ordinary rule signal, is worked out on the server.

With the runtime off, those five triggers see zeros and empty lists for every visitor on every request, and an audience that depends on them never clears its threshold. With it on, the first page already counts: the runtime records the view, the visit and the current path before the page is evaluated, so there's no waiting for a second page view.

## With rules, both have to pass. Without rules, the score decides alone

If the audience also has rule conditions, a visitor has to clear both: the rules, evaluated the normal OR-of-AND-groups way, AND the score threshold. If the audience has no rule conditions at all, the threshold is the entire test — the usual group logic doesn't come into play, because there's nothing left for it to evaluate.

## Six ways to earn points

Each scoring condition names one trigger and the points it's worth. Four of them compare against a threshold you set; two are all-or-nothing:

- **Page View Count (session)** — views this session, once it reaches your threshold
- **Total Page Views (all time)** — views across every session, once it reaches your threshold
- **Time on Site** — session duration, once it reaches your threshold
- **Category Viewed** — how much of one named category someone has read, once that reaches your threshold
- **URL Match** — a pattern matched against the pages a visitor has viewed; it matches or it doesn't, and any threshold on it is ignored
- **Signal Match (any instant signal)** — any ordinary rule signal and operator, scoring instead of gating, so a UTM value or a self-ID answer can contribute points; also all-or-nothing

## One running total, not a total per group

Points from every scoring condition, in every group on the audience, add into a single running total — there's no separate score per group and no per-group cap. That one number is compared once against the audience's threshold.

## Without the browser runtime, Signal Match is the only trigger that can score

On a site without the runtime, an audience whose scoring conditions are all drawn from those five can never reach its threshold. And because a threshold with no rule conditions *is* the whole test, such an audience matches nobody, on any page, ever — with nothing in the admin to tell you so. The rule tester won't catch it either: you supply the signal values there, so a page-view count you typed in will clear a threshold that real traffic never will. See [What each signal can see, and when](/targeting/what-each-signal-can-see-and-when/).
