As part of my tool agnostic analytics reporting series, I’m showing actionable reports you can build in any analytics tool to immediately improve the customer journey. Today’s report is all about showing you how to identify the buttons that are causing the most friction for your users. Although friction points on your website can present themselves a number of different ways, today I’ll highlight rage clicks. A rage click is a term that describes multiple clicks on an area of your website in a short time frame.

In order to identify these rage clicks, we’ll take important button clicks, like CTA clicks and navigation clicks, and drill down into the specifics of which button was clicked, which page it was clicked on, and the destination of the click. This is best displayed on a segmentation chart within Amplitude. Go to the upper left hand corner of your screen to create a new chart.

Because we want to select two events instead of one, you can start off by selecting the “Any Event” event. Filter by your important button clicks. In my case, I used cta_click and navigation_click.

From there, I’ll use the grouped by functionality to get my specifics. I’ll group by Event Name to see what type of button click. I’ll group by Page Path to see what page the button was clicked on. I’ll group by link_text to see what the text was on the link. Lastly, I’ll click link_url to see the destination of the button.

Since rage clicks imply that a button was clicked multiple times, I’m going to change the measurement from Uniques to Frequency. I’m subsequently going to set my bucket to start at 2 and click apply. This will help filter out the noise from buttons that are only clicked once.

You’ll see your segmentation chart populate the buttons that on average get the highest amount of rage clicks. Each will indicate the frequency at which the button was clicked, so if you notice too much noise from buttons that are only clicked twice, feel free to increase the starting number of your bucket range.

There you have it! Easily spot the rage clicks on your website within Amplitude with just one report. These rage clicks are great candidates for A/B testing and removing them will help remove friction points on your website.

As part of my tool agnostic analytics reporting series, I’m showing actionable reports you can build in any analytics tool to immediately improve the customer journey. Today’s report is all about showing whether or not you have the right words on your page. Whether it’s unintuitive text on a button or content that just isn’t robust enough to capture a user, here’s a step by step guide to building your report.

Note: The key to quick, actionable insights for your friction points is thoughtful event tracking and the right event structure. If you’re not sure whether or not you have the right event structure, dive into my event structure blog post. This post gives an actionable list of events you should track and how to update your event naming structure to build reports quicker.

The first indication that the content on your page isn’t resonating with users is finding pages that have a higher than average usage of your global navigation. I’ve demonstrated how to build out the first part of this report with Part 1. Now that you understand which pages have higher than average usage of your global navigation, your next step is to see which global navigation elements your website visitors are using.

Create a segmentation report using your navigation_click event. Group by Page Path and link_text, and count as totals, not uniques.

This should populate the report as such, with your Page Path and link_text are populated as rows. In the columns you’ll see Event Count – the number of times that link text was clicked on that particular page.

It’s especially important to view this report in conjunction with the first report because it gives context. Using only the above report, you would think that you need to focus your efforts only on the home page. However if you view our first report (screenshotted below), you’ll notice that a greater percentage of people had a difficult time on the Bath page, which is actually where we should be focusing our efforts.

There you have it! These are the pages that need the most content help and which content you should be adding on those pages.

As part of my tool agnostic analytics reporting series, I’m showing actionable reports you can build in any analytics tool to immediately improve the customer journey. Today’s report is all about showing whether or not you have the right words on your page. Whether it’s unintuitive text on a button or content that just isn’t robust enough to capture a user, here’s a step by step guide to building your report.

Note: The key to quick, actionable insights for your friction points is thoughtful event tracking and the right event structure. If you’re not sure whether or not you have the right event structure, dive into my event structure blog post. This post gives an actionable list of events you should track and how to update your event naming structure to build reports quicker.

The first indication that the content on your page isn’t resonating with users is finding pages that have a higher than average usage of your global navigation.

To do that in Amplitude, create a new data table report with the dimensions Page Viewed and navigation_click. Pull your Page Path into the rows column.

Select “Add Event or Metric” in the third column.

Define a new metric:

Your new metric should be a formula using two events, navigation_click and Page Viewed. Your formula should start with “%:” – this indicates that the metric should be formatted as a percentage. Then type in TOTALS(A)/TOTALS(B).

This will show you how many times the navigation was used compared to how many times the page was viewed. The higher the percentage, the more likely your on page content wasn’t resonating with users.

Check out part 2 to see which navigation items are being clicked.