Scenario 1: User A follows the journey path in the first session. In a subsequent session, the user has an event that matches only a later node.
Suppose that User A visits the site and completes the journey (Node 1: “Visit site” > Node 2: “View Product A” > Node 3: “Check out”). Because User A had an event that matched each node of the journey in order, an event is counted on each node of the journey.
Now, suppose that User A visits the site again in a later session. Because User A already completed the journey in a previous session by following the journey path, this means that any time User A has an event that matches any node in the journey–even if User A has not followed the path of the journey in their current session–an event is counted on the relevant node in the journey. For example, if User A checks out, then an event is counted on the “Check out” node. This can result in a higher percentage and number on the “Check out” node than on the preceding node, “View Product A.”
In this example, the journey’s container setting of “Person” plays a critical role in determining that the event on the third node (“Check out”) is counted in the subsequent session.
Alternatively, if the container setting had been set to “Session,” then the event that took place only on the third node in the subsequent visit would not have counted in the journey, because the statistics shown in the journey would be constrained to a single defined session for a given person. To learn more about the container setting, see Begin building a Journey canvas visualization in the article Configure a Journey canvas visualization