Find where people reach value. And where they stop.

A funnel counts visitors who complete selected events in order within an analysis window. Define the important steps before you collect them. For a SaaS product, an example could be account created, project created, and teammate invited. Inspect completion between steps to see where the sequence loses participants.

Save a funnel to use the same definition again. A lower completion rate identifies a place to investigate; it does not prove why people stop.

A retention cohort groups visitors by the week when DataVisitors first sees them. Later columns show whether those visitors return in subsequent weeks. Use weekly retention to examine repeat use after an initial visit.

A segment filters an event by a property value. It reports matching visitors and events. Use a segment when one event total hides a useful distinction, such as the selected plan or application version. Send only properties that your collection rules permit.

Your collection and consent settings determine which activity can be connected across visits. Stateless daily counts are not a substitute for consented cross-day behavior.

Journeys rank the first three page views of a visit in time order. Use them to inspect common paths before you decide which funnel to save. A journey describes collected navigation; a funnel checks the event sequence you define.

Event goals and page-pattern goals give the team a consistent definition of a conversion. First-click and last-click attribution provide two different views of its source.

Choose one activation step. Review its funnel result, inspect the relevant journey, and compare the next period after your change. Use the same definitions for a meaningful comparison.

See the SaaS example. Connect events through the browser tracker or HTTP API. Funnel and retention access depend on the plan. DataVisitors does not provide a built-in experiment assignment system.