What each signal can see, and when
Every rule signal but Pages Visited is decided on the first request; page views and time on site are not rule signals at all.
Nearly everything a rule can read is known the instant a visitor's first request lands. One rule signal isn't — and three things editors reach for as signals turn out not to be rule signals at all.
Decided on the first request
UTM Source, Medium, Campaign, Term and Content, any other query parameter, Referrer Domain and Referrer Source Type, Is Known Visitor, Entry Page and self-ID answers are all read on the server before the page is ever sent to the browser. A rule built only from these matches on someone's very first request — a link like /pricing?from=marketer is matchable the moment it's clicked, not on a second visit.
Pages Visited is the one that needs the browser
Pages Visited — the paths someone has looked at this session — is the only rule signal the server can't work out for itself. It's collected by Kywi's browser runtime, and that runtime is optional and off unless your site has explicitly turned it on.
With it off, Pages Visited is empty for every visitor on every page, so a rule on it matches nobody. With it on, the current page is recorded before the first evaluation runs, so the page a visitor is standing on is already in the list — there's no one-page delay to design around.
Page views and time on site are not rule signals
There is no rule condition for page-view count, total page views or time on site. They aren't in the signal list, and no operator will get you one. They exist only as score triggers, where they contribute points toward an audience's threshold rather than deciding whether a condition passes. If what you want is "someone who has read three pages," that's a score audience, not a rule — see Score-based audiences, which also covers why those triggers depend on the same optional browser runtime.
Entry Page looks like session data and isn't
Entry Page reads a cookie set on the first request of a session, but when that cookie doesn't exist yet — on the landing request itself — it falls back to that same request's own path and query. That isn't a degraded mode, it's the mechanism: a a cookie written on this request can’t be read until the next one, so a campaign link has to be matchable against the page it points at or it couldn't personalize anything without a reload. A rule on Entry Page is immediate, like the URL-based signals above.
Self-ID keeps working on every later page
Once a visitor submits a self-ID answer, it resolves server-side on every render after that — not only in the browser — because the arm a visitor sees is always chosen and pruned on the server. A rule built on self-ID doesn't lose its footing after the page that collected the answer.