Checking out where your users are going after taking certain actions is helpful for deciding what should come next to support them on that journey. Are users jumping to a different part of your app, or leaving altogether? Is there a dropoff that indicates something can be improved with this flow? What do users need at this point that you can provide?
You can use the Paths module in Heap to see what your users did after a certain event.
To see this in Heap, complete the following steps:
1. Navigate to Analyze > More > Paths
2. Filter down what type of user activity you’d like to see by choosing between see only raw pageviews, see only defined events, or see both raw pageviews and defined events. Note that on mobile, screenview events will appear as pageviews.
In a Heap on Heap example, we may want to understand what our customers are doing after saving a chart template. We’ll select both raw pageviews and defined events to have as broad a scope as possible for our user activity.
3. On the very next drop-down, select From. This is what enables you to see where users are going or what they are doing after your goal event.
4. Select your goal event. In our example, we want to see what happens after customers save a chart template, so our full analysis looks like this:
5. Last but not least, click the View results button to generate a visual of paths from your goal event. Hover over and click on any of the paths to drill down for more details about a path.
You can update your chart to apply filters if you’d like to see only results for a specific selection of users, or group pageviews by a property. For example, you may have long site URLs and only want to see a certain section of the URL. You can set up a defined property to capture this information only, then use it in this query to make the results cleaner.
For more information and best practices on using the Paths module, see Paths.