Conversation
Adds a new `sequence` filter operator that lets callers express "sessions where step A was followed by step B (in order, within the same session)". When querying with event-specific dimensions the filter pins results to the immediate next event after the sequence completes; for session/aggregate queries it restricts to sessions where the sequence occurred. Also adds a simplified `event:label` computed dimension: "Visit /path" for pageviews, goal display name (or raw event name) for custom events.
Adds a 3-column waterfall journey explorer ("Explore user journeys") to
the Behaviours panel, gated behind a `funnel_exploration` feature flag.
When enabled, an "Explore" option appears first in the Funnels dropdown
and renders the FunnelExploration component that uses the new sequence
filter and event:label dimension to show what events users do next.
|
matching_toplevel_filters was populated with all site goals when no event:goal filter was applied, causing derived_name_filter to restrict events to goal-relevant names only. With scroll goals present, this included 'engagement' events while excluding pageviews, leaking engagement rows into event:label results. Now matching_toplevel_filters is only populated when event:goal is in dimensions or filters - the cases that actually need it.
Page/entry_page/exit_page filters are stripped from subsequent column queries so they only constrain the starting point of the journey.
Shows 3 columns by default; selecting an event in the last column reveals a new one, allowing exploration of arbitrarily deep journeys.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a proof of concept for funnel exploration feature. Mechanism:
event:labeldimension to be able to break down a mix of pageviews and custom events without having to create goals for them. The label isVisit <page>for pageviews and the custom event name for custom events.sequencebehavioural filterfunnel_explorationfeature flag shows a simple UIThis is mostly a demo, not production-ready by any means. Explicitly ignored concerns for now:
sequencefilter overlap withhas_done. Feels like it should be possible to find a design that unifies these behavioural filters. Requires thoughtful API design.sequencefilter. At the moment each step filters byevent:labelwhich requires scanning the whole events table and building labels for every event. Also it builds many subqueries, perhaps this can be avoided.