Documentation
¶
Overview ¶
Package paths computes user flows — "what do users do after event X?" — the Flows / Pathfinder / Paths report. For each user it anchors at their first occurrence of the start event and follows the next steps in time order, then aggregates the ranked next-event at each depth. Deterministic.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Result ¶
type Result struct {
Start string `json:"start"`
Users int `json:"users"`
Levels []Level `json:"levels"`
}
Result is the flow: how many users hit the start, then what they did next.
func After ¶
After follows up to `depth` steps after each user's first `start` event and ranks what they did at each step (a user who stops contributes an implicit drop).
func Pages ¶ added in v0.17.0
Pages follows page-to-page navigation instead of event-to-event flow: anchored at each user's first $pageview of startPath, the levels rank the PATHS of the pageviews that follow (Step.Event holds the path). Autocaptured $click/$engagement noise never enters, so the answer is "where do visitors go next", not "what did the SDK record next". Consecutive repeat pageviews of the same path collapse into one — a reload is not a navigation.
Source Files