ux • Click tracking metrics and insights - martindubenet/wed-dev-design GitHub Wiki
- Visited sections,
- Navigation path ounce logged in,
- Used features (components),
- ⏳ Time gap between clicks can indicate confusion in the UI about what action to choose,
- ↶ « Back to previous view » actions can indicate a miss understood Call-To-Action (CTA).
These services are sometimes free, keeping the ROI features under a paid wall.
- Import API and integrate basic account metas the the
<head>of your SaaS webapp, - Wait a few weeks to gatter datas from your users,
- Analyze datas examples.
GTM is an API that allows you to inject Scripts within you web solution. It provides a unique slot, an open tunnel in your webapp’s <header> HTML tag for marketings ressources to inject their metas independently from your development cycle. But it can also be used to inject other API maximizing the loading speed by reducing the quantity of HTTP request to a single.
GTM is not the same as Google Analytics, GTM does not provides insights by itself. It is only a tunnel for GA to get to your code base.
| Product | My review | Pros | Cons |
|---|---|---|---|
| Google Analytics | ★★☆ | Powerfull. Google is always generous when you give it your datas. | If your webapp contains sensitive data from your customers Google will fetch it. |
| Pendo.io | ★★★ | Free version is generous in features | Free version is limited in user accounts. |
| Heap.io | ? | ||
| Amplitude.com | ? |
- When to Use Which UX Research Method — Youtube/NNgroup
- Creating a UX Research Plan — Youtube/2022 - Sarah Gibbsons, chief designer at NNgroup
- UX Research Cheat Sheet — Youtube/2020 - Sarah Gibbsons, chief designer at NNgroup
- Playlist The 10 Usability Heuristics — Youtube/NNgroup
Source: Susan Farrell - NNgroup 2017 Feb. 12
| Stages | Methods |
|---|---|
| Discover |
In addition to our stakeholders determining what future success metrics to look for, here are 5 methods to utilize to get to identify the issues: ✱ Field study ✱ Diary study ✱ User interview ✱ Stakeholder interview ✱ Requirements & constraints gathering. |
| Explore |
Understand the problem and how you can satisfy the user is the goal at this point. Common methods to understand how your users are grouping content: ✱ Competitive analysis ✱ Design review ✱ Persona building ✱ Task analysis ✱ Journey mapping ✱ Prototype feedback & testing (clickable or paper prototypes) ✱ Write user stories ✱ Card sorting. |
| Test |
On-going strategic activities can help you get ahead of future problems. Be transparent about the good/bad news with your stakeholders and coworkers regarding how testing is going will help creating open discussions in your group. ✱ Qualitative usability testing (in-person or remote) ✱ Benchmark testing ✱ Accessibility evaluation. |
| Listen |
Listen throughout the research helps understanding new problems that have arisen and (re)direct future efforts. ✱ Survey ✱ Analytics review ✱ Search-log analysis ✱ Usability-bug review ✱ Frequently-asked-questions (FAQ) review. |
-
Attrition Rate : Customer attrition rate measures customer loss as a percentage of the total customer base.
Calculate customer attrition rate by taking the number of lost customers in a specific time period and dividing it by the total number of customers at the beginning of the period.
-
Churn Rate is a KPI used to measure customer attrition.
Calculate churn rate by dividing the number of customers lost during the given time period by the number of customers at the beginning of the given time period, then multiplying that figure by 100 to get a percentage. Sum the churn rates: Add up all the churn rates you've calculated for each period.
-
Core Events signifies a visitor's meaningful engagement with your app. This could range from actions like following or sharing, to viewing vital pages, or completing significant workflows with actions like saving or publishing. Using these features demonstrates that visitors are realizing the value of your app, increasing the likelihood of their return and continued usage.
To distinguish your Core Events from the rest of the data, start by identifying what you believe to be your Core Events. Validate these assumptions by ensuring that engagement with these Core Events leads to above-average retention by using the Account Retention by Usage widget. Additionally, monitor user interactions with these Core Events using the Time to First Use widget.
- KPI : « Key Performance Indicator » can be loosely translate to any data that translate gathered metrics about anything. This is a common term used in « Operational Performance Management » (OPM) solutions.
-
PES : « Product Engagement Score » is a metric that provides a singular view into how users are interacting with a product. It is a composite score, made up of three elements:
- Adoption measures the average number of Core Events, or key features in your product, used by active visitors or accounts. The average number of Core Events adopted across all active Visitors or Accounts.
- Stickiness is the average of the percentage of weekly active users who return daily (DAU/WAU), or the percentage of monthly active users who return daily (DAU/MAU) or weekly (WAU/MAU).
- Growth is the sum of new and recovered Accounts or Visitors divided by dropped Accounts or Visitors (also known as the Quick Ratio).
- MAU : « Monthly Active Users ».
- NPS : « Net Promoter Score » is a common metric used in customer experience programs. Your NPS score is measured with a single-question survey and reported with a number ranging from -100 to +100, where a higher score is desirable.