How it works

Visits and outcomes

How requests become visits, and how a closed visit gets one outcome from recorded facts.

Parlox counts visits, not only page views: a merchant asks how many agents came, not how many pages they loaded. Each visit ends with one outcome (a fetcher's or UCP visit gets it when you open it), and the outcome is issued only when the facts that define it are in the visit's events.

What a visit is

VisitorA visit isGrouped by
A browser (a person or a browser agent)One browser tab, until 30 minutes pass with no activityA random id the browser part keeps in the tab's sessionStorage. Never a cookie, never shared across tabs or sites
A fetcher reported by your serverThe same client's requests within the same 30-minute windowThe user agent and a daily hash of the address, computed on your server
An order posted without a visit idOne per orderThe order id. Stored, never attributed to a visit it cannot prove

Shopify's pixel and an order posted with the browser's sessionId() join the browser visit they belong to.

Limits that follow from these rules: an agent that uses several tabs is several visits, and a fetcher's run that crosses a half-hour boundary is two.

The visit in sentences

Open a visit in the dashboard's Visits view and it is described in plain sentences, built from its recorded events and nothing else: where it arrived from, the pages it opened, the products it viewed, what it added to the cart and from which source, the CAPTCHAs and card forms on its pages, clicks that had no effect, the fields it filled and how long the slow ones took, what was rejected, how long it waited, and the outcome. No AI model writes any of it.

Agent visits also have a recording of your page as the agent saw it.

Outcomes

A visit closes 30 minutes after its last event, and then gets exactly one outcome (a fetcher's or UCP visit, when you open it). The rules run in this order; the first that matches wins.

OutcomeThe evidence it needs
Completed the purchaseA purchase from your server or from Shopify's pixel
Blocked by a CAPTCHAA CAPTCHA appeared, the visitor interacted with it, nothing was submitted after, and nothing was reached beyond that page. A CAPTCHA merely present on the page is not evidence, since many pass visitors silently
Rejected at a fieldA validation error or an on-page error message after the last progress, and nothing reached after it. Names the field or the message's element
Stuck on a controlA rage click, or two or more clicks with no effect on the same control, with nothing reached after. Names the control
Stopped at paymentCard fields were focused or filled, then nothing
Left the checkoutThe checkout was reached, payment never touched
Left with items in the cartAdd to cart was reached, checkout never
Browsed onlyPages, perhaps a product view, nothing more
UnknownNone of the above

Invisible CAPTCHAs. A CAPTCHA that scores visitors silently, such as reCAPTCHA v3, is recorded as present on every page that loads its script, but it shows no challenge to interact with, so its silent checks do not make a visit "Blocked by a CAPTCHA". If your page shows an error for a low score, and marks it as one (see the signals), the visit shows as "Rejected at a field", naming that message's element; if it fails silently, the visit ends with whatever step it reached.

"Unknown" is a real answer: a visit that matches no rule with enough evidence is never given a guessed outcome. The events behind each outcome are highlighted in the visit's timeline, and the dashboard counts outcomes for people and agents side by side.

Agents that shop through a store's own UCP API (the Universal Commerce Protocol) have outcomes of their own, read from the store's last answer: completed, handed to the buyer by the store, rejected at a field, left the checkout, browsed only.

The signals behind them

The browser part records what the outcome rules read, without reading what anyone typed:

  • Fields: which field was focused or changed (its name, type and autocomplete attribute), how often, how long, and the browser's validation reason (valueMissing, patternMismatch), never the value.
  • Errors shown: an element announced as an error (role="alert", aria-invalid, a common error class) appearing within two seconds of a click or submit. Its presence and position, never its text.
  • Clicks: "no effect" when nothing changed within a second; "rage" for three or more clicks within a second in one spot.
  • CAPTCHAs and payment forms: which one appeared (reCAPTCHA, hCaptcha, Turnstile, Arkose; Stripe, PayPal, Adyen, Braintree, Shopify, Klarna, or a plain card form).

Alerts

When closed agent visits keep ending in the same failure (the same field rejecting them for the same reason, the same control doing nothing, a CAPTCHA, the payment form), the dashboard raises it under Needs attention once the count reaches the threshold you set in Settings. Each alert opens the visits behind it.