In SaaS, trends are the difference between “we think users like this feature” and “the chart is waving a tiny flag and shouting, yes, please build more of this.” The Trends report in Userpilot helps product teams visualize how users, companies, sessions, events, pages, and in-app content engagement change over time. In plain English, it turns scattered product behavior into a readable story: who did what, when they did it, how often they did it, and whether that behavior is growing, shrinking, or quietly ghosting your roadmap.
The Userpilot Knowledge Base positions Trends as a flexible product analytics report for spotting patterns and compositions inside product data. That sounds technical, but the idea is very practical. If users are suddenly engaging with a new dashboard, completing onboarding faster, clicking a checklist item more often, or abandoning a key page, a Trends report can help you see it before the problem becomes a quarterly “surprise.” And as every product manager knows, surprises are fun at birthday parties, not in retention meetings.
What Is the Trends Report in Userpilot?
The Userpilot Trends report is a product analytics tool designed to help SaaS teams monitor user behavior over time. It can analyze different kinds of product data, including events, page views, feature tags, tracked actions, custom events, and engagement with Userpilot content such as flows, checklists, and in-app experiences.
Instead of looking at one isolated metric, Trends helps teams compare activity across time periods, user segments, companies, platforms, and properties. For example, a team could track how many users triggered a “Create Project” event each week, compare adoption between free-trial and paid users, and then break the results down by plan type or region. That gives the product team something far more useful than a vanity metric. It gives context.
Why Trend Analysis Matters for SaaS Product Teams
Product analytics is not just about collecting numbers. It is about turning behavior into decisions. Trend analysis helps product managers, growth teams, customer success leaders, and UX researchers answer questions such as:
- Are users adopting the features we just launched?
- Which user segments are becoming more active?
- Where is engagement dropping?
- Are onboarding flows improving activation?
- Do mobile users behave differently from web users?
- Is usage growing steadily or only spiking after campaigns?
Without trend reporting, teams may rely on anecdotes, loud customer feedback, or whoever speaks most confidently in the meeting. With trend reporting, decisions become easier to defend. If the data shows enterprise accounts are using a workflow twice as often as small-business accounts, the next step is not “let’s guess.” The next step is to investigate why.
Core Use Cases of Userpilot Trends
1. Tracking User Growth and Engagement
Userpilot Trends can help teams measure daily active users, weekly active users, and monthly active users. These metrics are useful because they show whether the product is becoming part of a user’s routine. A healthy SaaS product is not simply opened once and forgotten like that fitness app everyone downloaded on January 2. It earns repeat usage.
By monitoring DAU, WAU, and MAU, teams can identify whether growth is consistent, seasonal, campaign-driven, or tied to specific product releases. If weekly active users increase after a new onboarding checklist launches, that may suggest the checklist is helping users reach value faster.
2. Analyzing Feature Adoption
Feature adoption is one of the strongest reasons to use a Trends report. A product team can compare multiple features and see which ones users actually touch. This matters because shipped features do not automatically become valuable features. A feature that nobody uses is not a feature; it is decorative furniture in the product interface.
For example, a B2B SaaS company might compare usage of “Invite Team Member,” “Export Report,” and “Create Automation.” If “Create Automation” grows steadily among high-retention customers, that feature may deserve more onboarding attention, better in-app prompts, or a place in upgrade messaging.
3. Measuring the Impact of In-App Experiences
Userpilot is often used for in-app onboarding, flows, checklists, tooltips, resource centers, surveys, and product experiences. Trends can help measure whether those experiences influence behavior. Did a new checklist increase activation? Did a tooltip drive users toward a hidden feature? Did a product tour cause more users to complete setup?
This is where Trends becomes especially powerful. Instead of only asking whether people saw a flow, teams can evaluate what happened afterward. The best in-app experience is not the one users admire politely. It is the one that helps them do something meaningful.
4. Building and Monitoring Custom Metrics
Userpilot Trends supports formulas, which means teams can create custom calculations from product events. For example, a SaaS team could calculate an activation rate by dividing users who completed a key action by users who started onboarding. That makes Trends useful not only for observing raw activity but also for building KPIs that match the company’s growth model.
Custom metrics are helpful because every product has a different definition of success. For one app, activation might mean creating a project. For another, it might mean inviting a teammate, publishing a page, connecting an integration, or completing a workflow. A good analytics setup respects that difference.
5. Segmenting and Breaking Down Product Data
Averages can be sneaky. They can make a product look healthy while important user groups quietly struggle. Userpilot Trends lets teams break down reports by user properties, company properties, segments, event properties, and other dimensions. That means teams can compare behavior by plan, role, industry, region, device, company size, or lifecycle stage.
For example, total feature usage may look stable. But when broken down by plan type, the report might show that enterprise users are increasing while starter-plan users are dropping. That insight changes the conversation. The issue is not “feature adoption is flat.” The issue is “starter-plan users are not finding value.” Much better. Much less fog.
How to Build a Trend Report in Userpilot
Step 1: Choose User-Level or Company-Level Analysis
The first decision is whether to analyze users or companies. User-level analysis is ideal for understanding individual behavior, such as how many users completed onboarding or clicked a feature. Company-level analysis is useful for B2B SaaS products where account behavior matters more than individual activity.
For example, if five users from the same account use a reporting feature, a company-level view can show whether the account is adopting the product broadly. This is especially valuable for customer success teams watching expansion signals or churn risk.
Step 2: Select the Metrics to Analyze
Userpilot Trends allows teams to choose metrics from several categories, including events, pages, and content engagement. Events may include tracked events, labeled events, custom events, or feature tags. Pages can show activity based on tagged page views. Content engagement can reveal how users interact with Userpilot-created experiences.
A practical report might include metrics such as “Session Started,” “Checklist Completed,” “Feature Used,” “Report Exported,” or “Upgrade Button Clicked.” The key is to choose metrics tied to a real product question. A Trends report should not become a junk drawer full of every event the team has ever tracked.
Step 3: Pick the Measurement Type
Userpilot provides several ways to measure selected metrics. Teams can view total event count, unique users or companies, total sessions, active users, count per user, or aggregate properties. Each measurement answers a different question.
Total event count shows activity volume. Unique users shows reach. Total sessions shows how often the metric appeared within sessions. Active users helps measure DAU, WAU, or MAU. Count per user reveals intensity, such as average or median usage. Aggregate properties summarize numeric properties like revenue, seat count, or usage limits.
Step 4: Add Filters for Focus
Filters help remove noise. Userpilot Trends supports filtering by user properties, company properties, segments, event properties, event frequency, and page frequency. Teams can apply filters globally across the whole report or inline to a specific metric.
For example, a product manager might create a report that only includes users on paid plans, then compare feature usage by role. Or they might filter one event to show only first-time usage while keeping another event unfiltered for comparison. This flexibility helps teams avoid comparing apples, oranges, and one suspicious pineapple.
Step 5: Apply Breakdowns
Breakdowns let teams compare groups side by side. A Trends report can be broken down by properties such as plan type, country, device type, company size, lifecycle stage, or segment. This is useful for identifying which groups are driving a trend.
For example, if feature usage increased in the past 30 days, a breakdown may reveal that most of the growth came from mobile users. That could validate a mobile UX improvement or suggest that the team should invest more in mobile onboarding.
Choosing the Right Chart Type
Visualization matters because the wrong chart can make good data look like spaghetti. Userpilot Trends supports multiple chart types, including line charts, stacked line charts, column charts, stacked columns, bar charts, stacked bars, pie charts, metric views, and scatterplots.
Line charts are great for watching change over time. Column charts make period-by-period comparisons easy. Stacked charts show how multiple events contribute to a total. Bar charts work well for comparing totals across categories. Metric views are useful when one big number tells the story. Scatterplots help visualize distribution when numeric breakdowns are involved.
Userpilot also supports linear and cumulative views. A linear view shows activity within each time interval, such as daily or weekly counts. A cumulative view adds activity over time, which is helpful for tracking long-term growth, adoption, or total completions.
Advanced Features That Make Trends More Useful
Formulas
Formulas allow teams to calculate custom metrics using arithmetic operations. This is valuable for building ratios, conversion rates, adoption rates, and engagement scores. For instance, a team could divide the number of users who completed onboarding by the number of users who started onboarding to calculate an onboarding completion rate.
Templates
Userpilot provides templates such as Top 10 Events, Top 10 Pages, Top 10 Users, and Top 10 Companies. Templates are useful when teams want a fast starting point. They reduce setup time and help users find high-impact insights without building every report from scratch.
“For the First Time” Filter
The “For the First Time” filter helps teams isolate first-time behavior. This is important because first-time usage often signals activation or discovery. If 500 users clicked a feature this month, that is useful. If 300 of them clicked it for the first time, that tells a much more interesting adoption story.
Bucketing
Bucketing groups continuous numeric values into ranges. For example, a team could group customers by revenue tier, number of seats, session count, or company size. This helps reveal patterns that might be hidden in raw numeric data.
Baseline Comparatives
Baseline comparatives help teams compare segments against a specific property value or against the overall dataset. For example, a report could compare adoption in each country against the overall average or against a selected country. This makes relative performance easier to understand.
Specific Examples of Userpilot Trends in Action
Example 1: Measuring New Feature Adoption
Imagine a SaaS company launches a new AI summary feature. The product team creates a Trends report for the “AI Summary Generated” event. They measure unique users weekly, filter by paid accounts, and break down results by plan type. After two weeks, the team sees strong adoption among enterprise users but weak usage among starter-plan users.
The next action is clear: improve onboarding for starter-plan users, add an in-app tooltip, and test whether a checklist item increases first-time usage. Trends does not make the decision automatically, but it points the flashlight at the right corner of the room.
Example 2: Diagnosing Onboarding Drop-Off
A growth team notices that trial-to-paid conversion has dipped. They build a report comparing “Onboarding Started,” “Integration Connected,” and “First Project Created.” The report shows that users still start onboarding, but fewer users connect an integration. That suggests friction in the integration step.
The team can then review the integration experience, improve help content, add contextual guidance, or trigger a support message when users pause at that step. Instead of rewriting the entire onboarding journey, they focus on the bottleneck.
Example 3: Finding Expansion Signals
A customer success team tracks company-level usage of premium features. They break down accounts by company size and monitor trends in workflow creation, team invitations, and report exports. If an account shows rising usage across multiple high-value features, that may indicate expansion potential.
This kind of trend analysis helps customer success teams prioritize outreach. Rather than sending generic “just checking in” emails, they can start relevant conversations based on real product behavior.
Best Practices for Using Userpilot Trends
Start with a business question before building a report. A strong question might be, “Are new users reaching activation faster after our onboarding update?” A weak question is, “What data do we have?” The second one usually leads to a dashboard that looks impressive and answers absolutely nothing.
Use a clean event taxonomy. Trends reports are only as reliable as the data behind them. If the same action is tracked with three different event names, the report becomes confusing. Teams should define consistent event names, properties, and tagging rules.
Compare periods carefully. A seven-day spike may not mean sustainable growth. It could be caused by a campaign, a release, a seasonal pattern, or one very enthusiastic customer with too much coffee. Use comparison periods and longer time ranges to separate signal from noise.
Break data down by meaningful segments. Total usage is useful, but segmented usage is often where the gold lives. Compare new versus returning users, trial versus paid accounts, small versus enterprise customers, or web versus mobile users.
Pair quantitative trends with qualitative insight. If a chart shows that users are dropping off, surveys, interviews, support tickets, and session replays can help explain why. Numbers tell you what happened. Human feedback tells you what made users sigh dramatically at their laptops.
How Trends Supports Better Product Decisions
Userpilot Trends supports a modern product-led growth workflow. Teams can observe user behavior, identify friction, launch in-app guidance, measure the result, and keep improving. This loop is essential for SaaS businesses that want to increase activation, feature adoption, retention, and expansion revenue.
The strongest product teams do not treat analytics as a reporting chore. They use it as a decision engine. Trends can help prioritize roadmap items, validate product launches, detect churn signals, identify power-user behavior, and improve onboarding experiences.
For example, if a report shows that users who invite teammates are more likely to become active accounts, the product team can make team invitation a more prominent onboarding milestone. If another report shows that a feature is rarely used after first click, the team can investigate whether the feature lacks value, visibility, or clarity.
Common Mistakes to Avoid
One common mistake is tracking too many metrics at once. Userpilot allows teams to add many metrics to a Trend report, but more metrics do not always mean more clarity. A report should be focused enough that a stakeholder can understand the takeaway in under a minute.
Another mistake is confusing correlation with causation. If feature usage increased after a product tour launched, the tour may have helped. But the increase could also be related to a marketing campaign, pricing change, seasonal demand, or a new customer cohort. Trends helps reveal patterns, but teams still need thoughtful analysis.
A third mistake is ignoring inactive or struggling users. Product teams naturally love looking at power users because power users make everyone feel smart. But growth often comes from understanding the users who hesitate, drop off, or never reach the “aha” moment.
Experiences Related to Trends – Userpilot Knowledge Base
Working with a Trends-style analytics report feels a little like becoming a product detective. At first, the clues may look random: a drop in onboarding completion, a spike in page views, a weirdly popular feature nobody expected, or a premium workflow that only enterprise users seem to understand. But once the data is organized by time, segment, metric, and behavior, the story begins to appear.
One useful experience is starting small. Instead of building a massive dashboard on day one, create one report around one meaningful question. For example: “Are users completing the activation event within their first week?” This question is simple, measurable, and connected to growth. In Userpilot Trends, that might mean selecting an activation event, measuring unique users, choosing a weekly data point period, and comparing new users by signup cohort or plan type.
Another practical experience is using Trends after every major product change. When a team launches a new onboarding flow, redesigns a dashboard, changes navigation, or adds a feature, it should create a before-and-after view. This does not need to be complicated. A comparison period can show whether engagement improved, stayed flat, or dropped. If the chart improves, celebrate responsibly. If it drops, do not panic. A dip can be a clue that users need clearer guidance, better copy, or a less confusing path.
Trends reports are also valuable in cross-functional meetings. Product managers may care about adoption. Customer success may care about account health. Marketing may care about activation and upgrade intent. Sales may care about expansion signals. A well-built Trends report gives each team a shared language. Instead of debating opinions, everyone can look at the same behavioral evidence.
One memorable pattern in SaaS analytics is that the most important insight is often hidden in a segment. Overall usage may appear average, but when broken down by company size, one segment may be thriving while another is struggling. This is why breakdowns matter so much. They prevent teams from making broad decisions based on blended numbers. Averages are polite, but segments are honest.
A final experience: Trends becomes more powerful when paired with action. Looking at charts is not the finish line. If the report shows low first-time adoption, add an in-app prompt. If a checklist improves activation, test a better version. If enterprise accounts use a feature more often, interview them and learn what value they see. The best use of Userpilot Trends is not simply reporting what happened. It is creating a repeatable loop of observe, learn, act, and measure again.
Conclusion
The Trends report in Userpilot is a practical analytics feature for product teams that want to understand how users interact with their product over time. It helps monitor engagement, analyze feature adoption, measure in-app experiences, build custom KPIs, compare segments, and identify opportunities for growth.
For SaaS teams, this kind of trend analysis is not optional decoration. It is the instrument panel. Without it, teams are flying by instinct. With it, they can spot adoption patterns, diagnose friction, and make smarter product decisions. Trends will not magically fix retention, activation, or feature discovery on its own. But it will show where to look, what to question, and which experiments deserve a front-row seat on the roadmap.
Note: This article is original, written in standard American English, and synthesized from current public information about Userpilot Trends, SaaS product analytics, feature adoption analysis, segmentation, reporting, and knowledge-base best practices.
