Skip to main content
Engagement separates flows that reached a qualifying subflow, nested flow or resolved decision from traffic that only landed and left. Use it when reading funnel rates to distinguish these populations. Observe derives engagement from the classified journey. Completion, successful authentication and a minimum time on page are not required. Engagement does not necessarily indicate deliberate user interaction.

​
1. What makes a flow engaged

engaged: true means a flow’s classified path contains at least one of:
  • Subflow: a qualifying subflow, as defined in the rules below.
  • Nested flow: a nested-flow reference, regardless of the child’s outcome or engagement. Skipped, invisible and automatically skipped children also count for the parent.
  • Decision: a decision with a recorded outcome, whether explicitly reported or inferred. Showing options without resolving the decision does not count.
Otherwise, engaged is false. A flow represents the overall journey. Subflows represent operations within it. The same engagement rule applies to every flow type:

​
2. Subflow rules

These rules apply to recorded events that survive classification. A raw start event does not qualify on its own unless a row below says so.

​
Terms used in the rules

  • Operation step: a tracked step inside a subflow, such as a ceremony, an options request or a post-response call.
  • Low events: the ambient field and window signals the SDK captures next to the tracked steps, such as focus, clicks, typing, paste, autofill and window blur. The classifier turns them into UI patterns.
  • Non-ignored: the SDK did not mark the event ignoreAsInteraction. The SDK sets that flag on starts, triggers and steps that ran without user action, such as a native credential sheet fired automatically or the background cui-get-options request. A flagged event still counts toward the subflow outcome. It only stops counting as proof of interaction. Absent or false means the flag does not exclude the event.
  • Non-system start: a subflow start whose actor is not system. SSO integrations can route a user into SSO automatically, and that start does not count.
  • Qualifying input interaction: a UI pattern derived from low events that counts toward engagement. The provide-identifier row lists the qualifying interactions.
Two additional rules apply to Conditional UI: cui-get-options never counts and cui-ceremony counts only when it finished successfully. The provide-identifier classification requirements below still apply. For immediate requests, window blur and runtime are evidence used to infer whether a prompt appeared, not a direct measurement of user intent.

​
3. Use engagement in analysis

Keep engagement separate from the flow’s outcome. An engaged flow can remain incomplete, and a parent can be engaged because of a nested flow even when the child itself is not engaged. For example, a password field click recorded through low events followed by abandonment qualifies; focus or prefill alone does not. The engaged filter uses the classified-path definition above. Individual metrics can use a narrower population. The login success rate alert, for example, requires a qualifying subflow or nested flow; a resolved decision alone is insufficient for that metric. When comparing rates, keep the selected flow type, outcomes, engagement filter and other cohort filters consistent. To investigate why a particular journey qualifies, inspect its classified flow and recorded events.