---
sourceDocument: Xanadu Platform Analytics
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/now-intelligence

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# How User Experience Analytics matches funnels

# How User Experience Analytics matches funnels {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Learn how User Experience Analytics matches sequences of pages you anticipate
users seeing before they reach a goal.

User Experience Analytics bases funnel matching on unique users, and not on sessions, so steps can be matched between sessions. For example, a user may start the first step of a funnel in their first session, and
continue the next step in another session. Users are counted only once for a selected time range, and step completions are only counted once per user.

A funnel measures users who complete a funnel step within 30 days, so a user can complete step #2 on January 1, then step #3 on January 30, to be counted.

Funnels steps are loosely matched. Users can perform other steps between the steps that define
the funnel. For example:

For the funnel A \> B \> C:

* A \> B \> C are matched.
* A \> B \> D \> C are also matched, where D can be any user action.
* A \> B \> E are not matched---the user is considered to have completed only step B.

When matching duplicate steps, the funnel analysis selects the first occurrence that progresses
the funnel, and ignores duplicate occurrences. For example, for the funnel A \> B \> C: With
a user who performs A \> B \> B \> C, the second B is ignored.

When selecting a time range, the analysis shows only users who complete the entire funnel
within the time range. If a user starts the first step before or after the selected time range,
they are not counted.

Funnel analysis respects duplicate funnel entrances. For example, for the funnel A \> B \>
C, a user performs the following actions:

<kbd class="ph userinput">A (Sunday) &gt; B (Monday) &gt; A &gt; (Tuesday) &gt; B (Wednesday) &gt; C (Thursday)</kbd>

The user is returned when selecting Sunday-Thursday, Monday-Thursday, Tuesday-Thursday, but not
if they select Wednesday-Thursday.

This behavior is true both for reviewing individual
sessions, and for the aggregated user count.


User Experience Analytics shows all sessions that
progress through the funnel for the selected step, excluding ignored occurrences, and can show
multiple sessions of a user.

When filtering by application versions, the analysis shows only the users who performed their
first action from the selected version.