Customer adoption analytics: 4 tools for usage reviews

When an account’s usage pattern is unclear, a pre-defined funnel may miss the actual steps taken. Amplitude’s documentation states that to find the paths users take without defining that sequence up front, use Journeys instead, according to Amplitude. This capability supports reviews where the expected user journey is not yet established. For customer success managers, this distinction matters when deciding whether to measure against a known workflow or explore how the account actually moves through the product.

If the review question is “what steps did the customer take?” rather than “did they complete step X after step Y?”, path exploration aligns with the documented use case. Amplitude names Journeys as the tool for this specific scenario, according to Amplitude. The documentation does not claim Journeys replaces all funnel analysis, but it specifies this feature for undefined sequences.

In practice, this means checking whether your current analytics setup offers a similar discovery mode before assuming a fixed funnel captures the account’s behavior. If the product has multiple entry points or non-linear usage, a discovery view may reveal paths that a rigid funnel would exclude. The Amplitude documentation ties this recommendation directly to the absence of a pre-defined sequence, according to Amplitude.

• Select Journeys for undefined paths. When you need to find the paths users take without defining that sequence up front, use Journeys instead, according to Amplitude.
• Distinguish retention counting methods. Return On counts a user on a single day; Return On or After counts every day up to their return, according to Amplitude.
• Check URL normalization rules. When breaking down by $current_url or $pathname, path cleaning rules automatically normalize dynamic URLs into consistent patterns, according to PostHog.
• Use readable event names. Make event names human-readable so that everyone on your team can know what they mean instantly, according to Twilio.

Choose one customer account review question, then check the corresponding path, retention, URL grouping or event-definition setting in your existing tool.

The table below lists the specific documented capability for each tool, tied to the source where that behavior is described.

Use this table to match the specific setting to your account review question. To discover user paths without specifying a sequence beforehand, use Journeys, according to Amplitude. For PostHog, the documentation states that funnels enable you to visualize your flows and understand where the friction points are so that you can improve them, according to PostHog. It also documents an "Any order" setting where steps can be completed in any sequence, according to PostHog.

For Mixpanel, the documentation asks what the most common sets of actions are taken after opening the app, according to Mixpanel. It further states that the tool transforms a high-level view of a certain flow step into a more granular, segmented analysis at any given point, according to Mixpanel.

For Twilio, the documentation states that Segment calls these "events" and recommends making event names human-readable so that everyone on your team can know what they mean instantly, according to Twilio. It also advises using unique but recognizable names like Video Recorded and Order Completed, according to Twilio.

Check the specific setting in your existing tool that matches the question you are answering for the account.

When a customer's product journey is not defined in advance, choose a path-discovery view to see how they actually move through the interface. Defined funnels serve a different purpose by visualizing flows and understanding where friction points are so that you can improve them, according to PostHog. This visualization approach allows reviewers to inspect specific product flow friction rather than guessing where users get stuck.

Amplitude documents four funnel views for reading results: conversion, conversion over time, time to convert, and frequency, according to Amplitude. These views provide distinct lenses on the same data, allowing you to match the metric to the specific account question you are answering.

PostHog offers an "Any order" setting where steps can be completed in any sequence, according to PostHog. This setting differs from a strict sequential funnel by allowing unordered completion. If your review needs to capture users who complete key actions in a non-linear way, this setting accommodates that behavior. Conversely, if the product requires a specific sequence for success, a defined funnel better reflects that constraint.

Use "Any order" for unordered completion, according to PostHog. Check whether the account's usage pattern requires strict sequencing or flexible ordering before configuring the chart. Selecting the appropriate view ensures the evidence reflects the actual user behavior you intend to analyze.

Recommendation: Select the funnel view that matches the account's expected journey structure. Use defined funnels for sequential workflows and "Any order" for flexible usage patterns.

Amplitude documents how retention counting methods alter the visual curve and the interpretation of user return behavior. The "Interpret your retention analysis | Amplitude Docs" page explains that a bar chart summarizes the Return On or After story at specific milestones: Day 0, 1, 3, 7, 14, and 30, according to Amplitude. This summary allows a quick read of drop-off milestones without scanning every day, noting that retention stays near 99% through Day 3, falls to about 69% by Day 7, holds around 60% at Day 14, and settles near 43% by Day 30, according to Amplitude.

Contrast this with the Return On method, where each user counts toward a single day rather than every day up to their return, according to Amplitude. Because of this counting difference, the curve collapses after Day 0, falling to about a third on Day 1 and roughly 14% on Day 2, then settling into a low single-to-low-double-digit band through Day 30, according to Amplitude. The distinction between Return On and Return On or After is critical for usage reviews because the same cohort can appear highly retained in one view and sharply declining in the other, depending on whether the metric counts cumulative days or single-day returns.

Amplitude also supports custom brackets for Return On charts. An example Return On (Custom) chart has a bar for each bracket: Day 0, Day 1-3, Day 4-6, and Day 7-11, according to Amplitude. Each chart can have a maximum of 100 custom brackets, according to Amplitude. This flexibility allows reviewers to align retention periods with specific product cycles or support intervals rather than relying on standard daily increments.

The documentation provides illustrative cohort return percentages to demonstrate these views. For a specific cohort, 100% of them triggered the return event on Day 1, and 72.1% triggered it on Day 7, according to Amplitude. These figures serve as examples of how the chart displays data points rather than benchmarks for any specific industry or product type. When reviewing account adoption, verify which counting method your tool applies before interpreting the slope of the retention curve. Check the retention intervals and return-counting method before interpreting the chart.

When reviewing account usage, the structure of the data often matters as much as the volume. Two distinct challenges arise: messy URL parameters that obscure user paths and cryptic event names that hide meaning. The documentation for these tools offers specific guidance on handling both.

PostHog addresses the URL issue through automatic normalization. According to PostHog, when you break down by $current_url or $pathname, path cleaning rules automatically normalize dynamic URLs. The documentation notes that this process turns specific instances, like /user/123, into consistent patterns, such as /user/:id. This means that if your review involves tracking navigation through user-specific pages, the tool groups these variations under a single pattern. You do not need to manually filter out every unique ID. Instead, the system handles the grouping so that the path data reflects the actual journey structure rather than individual account identifiers. Check whether your review requires grouped paths to see this normalization in action.

Event naming presents a different challenge. Twilio provides clear recommendations for defining events in a way that remains useful to the team. According to Twilio, Segment recommends making event names human-readable. The goal is for everyone on the team to know what the events mean instantly. The documentation suggests using unique but recognizable names, providing examples like "Video Recorded" and "Order Completed." These labels are designed to be immediately understandable without requiring a lookup table.

Check for reserved property names before defining event properties. According to Twilio, the Properties docs list reserved property names. Compare your property names with the reserved-property list.

Choose readable event names, then check property names against the reserved-property list.

These steps ensure that the evidence you gather is both structured and legible. Clear event names and normalized URLs allow you to interpret the data without ambiguity. When the data is clean, the account review focuses on behavior rather than data hygiene.

Select the analytics view that matches the specific account review question before configuring the follow-up task. If the question asks how users navigate after a specific trigger, use a flow exploration tool. Mixpanel documents a feature that asks, "What are the most common sets of actions taken after opening the app?" according to Mixpanel. This capability suits reviews where the customer's journey is not a fixed sequence but a set of observed behaviors. The tool allows the reviewer to inspect common actions after opening the app, providing a high-level view of the flow.

When the account question requires context around a specific event, check if the tool allows adjusting the surrounding steps. Mixpanel states, "Above and below your selected events, you can choose how many steps to show before and after each event, respectively," according to Mixpanel. This setting lets the reviewer see the immediate environment of a selected action. For example, select a recorded event to inspect the steps before and after it. The ability to choose the number of steps before and after each event helps isolate the context of the selected action.

If the account question involves different user groups or segments, use a tool that can segment a selected flow step. Mixpanel notes that this feature "Transforms a high-level view of a certain flow step into a more granular, segmented analysis at any given point," according to Mixpanel. This supports a more detailed, segmented analysis of the selected flow step. The segmentation capability turns a general view into a detailed analysis.

• Onboarding tools: compare 4 customer project plans
• Health score setup: 8 rules for weights and validity
• NPS survey configuration: 5 checks before launch

Which customer adoption analytics capabilities fit a usage review?

PostHog automatically normalizes dynamic URLs into consistent patterns when breaking down by $current_url or $pathname PostHog. Mixpanel allows users to choose how many steps to show before and after each selected event Mixpanel. These documented features support reviewing defined funnels, normalized path data, and granular flow steps.

How does Return On differ from Return On or After?

Return On counts each user toward a single day rather than every day up to their return Amplitude. This counting method causes the curve to collapse after Day 0, falling to about a third on Day 1 and roughly 14% on Day 2 Amplitude. The curve then settles into a low single-to-low-double-digit band through Day 30 Amplitude. Return On or After counts every day up to the return, keeping retention higher initially.

What is the maximum number of custom brackets in an Amplitude chart?

An Amplitude chart supports up to 100 custom brackets Amplitude. Reviewers should adjust their bracket settings to stay within this documented maximum when configuring charts.

How does PostHog handle dynamic URLs in my account usage breakdown?

PostHog path cleaning rules automatically normalize dynamic URLs like /user/123 into consistent patterns like /user/:id PostHog. This normalization occurs when breaking down by $current_url or $pathname PostHog. The feature ensures that variable URL segments are grouped consistently in flow visualizations.

Can Mixpanel show steps before and after a selected event?

This setting appears above and below the selected events in the flow report Mixpanel. Adjusting these counts controls how many surrounding steps appear.

This post is general operational information, not legal advice about notice periods or renewal clauses. It does not promise that any method keeps a customer. A review model checked the facts once, and that check can miss errors, so open the sources before you act.