Completed business results: a verified purchase, confirmed lead, booked appointment, account creation, or completed call.
Strong steps toward an outcome, such as opening pricing or beginning checkout.
Useful but non-final behavior, including meaningful reading, video completion, or movement to related content.
Keeping these layers separate prevents a familiar analytics error: labeling every click a conversion. A submit-button click is not a lead if validation fails. A pricing visit is not a purchase. A deep scroll may be valuable, but it is not reported as revenue intent without evidence.
The same visible words can play different roles on different pages. “Learn more” might open a product explanation, a privacy policy, or a sales path. Outcomes by Page treats the semantic object — the page-specific business meaning — as the durable layer. Selectors, destination patterns, and regex are implementation tools underneath it.
A pageview tells you a page loaded. It does not tell you whether the page did its job. Assigning each page an explicit job, then separating outcomes, intent actions, and engagement, is what turns a traffic count into a business answer.
Coming soon.
Form start, submission attempt, validation error, and confirmed success are different events. Treating a click as a lead inflates every report built on top of it.
Coming soon.