How should I track usage of individual tools on a web-based tools website?

Support & Bugs
1

I’m working on a website that provides several browser-based tools, and I’m trying to improve the way user interactions are measured.

At the moment, I’m mainly interested in understanding which individual tools receive the most usage, how long users stay on a tool page, and whether visitors actually interact with the tool rather than simply viewing the page.

For example, if a visitor opens a calculator, converter, or text utility, I would like to distinguish between a simple pageview and an actual interaction with the tool. I’m also interested in tracking repeated usage without creating an excessive number of events.

Would you recommend using custom events for each tool interaction in Matomo? If so, is there a preferred structure for naming actions/categories when a website contains many different tools?

I’d also appreciate any advice on keeping the tracking lightweight so that analytics does not noticeably affect the performance of the tools.

2

Yes, Event Tracking would be a good approach for distinguishing between someone simply viewing a tool page and someone actually using the tool. Matomo Events are specifically designed to measure interactions that don’t necessarily generate another page view.

With a large number of tools, I would recommend using a consistent Event structure rather than creating completely different Events for each tool. For example:

  • Event Category: Tool
  • Event Action: Used
  • Event Name: Calculator, Converter, Text Formatter, etc.

This allows the Event Name to identify the individual tool while keeping the Category and Action consistent. You can then compare the number of Events, Visits and Unique Visitors associated with each tool.

You could also introduce a small number of additional actions where they provide useful information, for example:

Tool > Started > Mortgage Calculator
Tool > Completed > Mortgage Calculator

I would avoid tracking every keystroke, calculation or small interaction unless you genuinely need that level of detail. Apart from generating unnecessary data, it can make your reports much harder to interpret. Instead, decide what represents meaningful use of each tool and fire an Event at that point.

For repeated usage, Matomo already records the total number of Events as well as the number of Visits and Unique Visitors associated with them, so you don’t necessarily need to create additional Events solely to determine whether tools are being used repeatedly.

For time spent on the tool page, you can continue using your normal page tracking. If accurate visit duration is particularly important, Matomo’s Heartbeat Timer can also improve visit-duration measurement, especially when a visitor spends a long time interacting with a single page without generating additional page views.

From a performance perspective, keeping the implementation to a small number of meaningful Events should remain lightweight. A structure such as Category = Tool, Action = interaction type, Name = tool name will also scale much better as you add more tools in the future.

3

This is a very practical way to structure tracking when you have a large collection of tools. I especially like keeping the Category and Action consistent while using the tool name to identify the individual utility.

For a site with calculators, converters, image tools, and text utilities, this approach should make it much easier to see which tools are actually being used rather than just receiving page views. I also like the idea of tracking meaningful actions such as “Started” or “Completed” instead of every individual interaction.

I’m working with a similar collection of online utilities on the DailyToolkit platform, so this kind of scalable event structure is something I’ve been thinking about as well. Keeping the tracking simple should make the data much more useful as the number of tools grows.