Start with the End - Tip for Journey's

Most teams are lazer focused on how users arrive at an important CTA, whether you're a Ecommerce site, SaaS, or other.

But what happens after is also equally as revealing.  

Consider this:
I'm part of an Ecommerce team that is trying to understand ways in which the user is having issues at important CTA's.  Lets say its a Purchase or Revenue Event.


If I use the Journey tool, and start with the Revenue Event, I can see what users are doing afterwards.  Most will likely have their next step be some sort of Purchase Confirmation page visit, which is to be expected.  But what if there is a subset of users that arrive at a 404 page, or Rage click on something, or do anything other than arrive at the confirmation page?  

(these are the sessions I would be interested in understanding further) 

The Journey tool makes it easy to investigate those small outliers that may be experiencing issues and allows you to isolate them as a Segment of users easily (through the integrated feature-set!). Now, you can further break down that cohort by device/platform/location/etc or any number of other dimension to help isolate the issue at hand.

Hope this helps!