Product Onboarding Glossary — User Activation, Retention & Analytics Terms

A/B Testing

Definition: A controlled experiment where traffic is split between two or more variants of the same element (onboarding flow, copy, feature) to measure which performs better on a chosen metric. Statistical significance testing confirms the difference is real, not noise. Why it matters: Without A/B testing, product changes rely on opinion. Every meaningful onboarding improvement claim should be backed by a test showing lift over the control. How to measure: Define a primary metric (completion rate, activation rate, click-through), assign users to variants via a stable hash (so the same user sees the same variant), measure the difference, and calculate p-value using a two-proportion z-test. See also: A/B Testing for Flows | Cohort Analysis | Conversion Rate

Activation Rate

Definition: The percentage of signups who complete your product's core value action within a defined time window. If 1,000 people sign up and 220 reach your activation milestone, your activation rate is 22%. Why it matters: Activation rate is the single strongest predictor of long-term retention. Users who never activate almost always churn. Improving this metric has a compounding effect on every downstream number. How to measure: Define your activation event (first project created, first message sent, first booking completed), then divide activated users by total signups for the period. See also: What is user activation rate? | Aha Moment | Time to First Value

Aha Moment

Definition: The specific moment a user first experiences your product's core value and understands why it exists. It is the emotional "click" that turns a curious visitor into an engaged user. Why it matters: Every product has an aha moment, but most founders cannot pinpoint exactly where it happens. Identifying it lets you redesign onboarding to get users there faster, which directly lifts activation and retention. How to measure: Analyze cohorts of retained vs. churned users. The action or page view that most strongly correlates with retention is likely your aha moment. See also: Activation Rate | Magic Moment

Audience Segment

Definition: A cohort of users defined by behavioral or attribute conditions — visit count, pages visited, time since signup, custom user properties, or any combination. Used to target in-app flows, analytics filters, and email at specific user groups. Why it matters: Broadcasting the same message to every user is lazy. Segmentation lets you show different onboarding flows to power users vs. first-time visitors, or analyze retention for users who completed activation vs. users who did not. How to measure: Define the segment using boolean logic over user properties and behavioral events. Modern tools like Onboardics accept plain-English segment descriptions and translate them to structured conditions automatically. See also: AI-Defined Audience Segments | Cohort Analysis | User Activation

Behavior-Triggered In-App Guides

Definition: Automated in-app messages (tooltips, modals, banners, tours, checklists) that fire based on what a user did or did not do inside your product. Unlike broadcast campaigns, each message is personalized to an individual user's journey state and appears inside the product itself. Why it matters: Generic onboarding sequences ignore context. Behavior-triggered guides reach users at exactly the right moment — when they stall, skip a step, or are one action away from activation. In-app delivery means users see the help where they need it, not in a separate inbox. How to measure: Track impression rate, completion rate, and the conversion rate of users who saw the guide vs. those who did not. See also: In-App Guidance

Bounce Rate

Definition: The percentage of visitors who land on a page and leave without taking any further action — no click, no scroll, no navigation. A bounce rate of 60% means 6 out of 10 visitors saw only one page. Why it matters: High bounce rates on onboarding pages signal that users are confused, unimpressed, or landing on the wrong page. It is one of the earliest warning signs of a broken funnel and the easiest to diagnose. How to measure: Divide single-page sessions by total sessions for the page. Compare across pages to find the weakest entry points. See also: Drop-Off Rate | Conversion Funnel

Churn Rate

Definition: The percentage of users (or revenue) lost during a given period. If you start the month with 500 active users and 40 stop using the product, your monthly churn rate is 8%. Why it matters: Churn is the silent killer of SaaS businesses. Even a small improvement in churn compounds over time — reducing monthly churn from 5% to 4% can double your effective user base within a year. Most churn traces back to poor onboarding. How to measure: Divide users lost during a period by users at the start of the period. Segment by cohort to see if recent signups churn faster than older ones. See also: Reduce SaaS churn in the first week | Day-N Retention

Click Heatmap

Definition: A visualization or table showing which elements on a webpage receive the most user clicks. Click heatmaps help product teams identify popular features, ignored UI elements, and rage-click patterns.

Why it matters: Click data tells you what users actually do, not what they say they do. The most-clicked element on a page often isn't the one designed to be the primary action. Onboardics goes further with AI-diagnosed click heatmaps that automatically identify which patterns indicate broken elements, dead zones, rage clicks, and CTA underperformance — and suggest specific fixes for each.

How to measure: Track every click event with element selectors and group by selector per page. Optionally weight by unique sessions vs. total clicks.

Cohort Analysis

Definition: A method of grouping users by a shared characteristic — usually signup date — and tracking their behavior over time. Each group is a "cohort" that you compare against others. Why it matters: Cohort analysis separates the signal from the noise. Without it, an improving metric might just reflect a growing user base rather than a better product. Comparing weekly cohorts shows whether your onboarding changes are actually working. How to measure: Group users by signup week, then measure retention, activation, or revenue for each group at day 1, 7, 14, and 30. Look for trends across cohorts. See also: Day-N Retention | Retention Curve

Conversion Funnel

Definition: The sequence of stages a user passes through from first visit to a desired outcome — signup, activation, payment, or any other goal. Each stage has fewer users than the one before it. Why it matters: Funnels make invisible problems visible. When you see that 80% of users complete step 2 but only 30% reach step 3, you know exactly where to focus. Without a funnel view, you are guessing where users struggle. How to measure: Define your key stages, count users at each, and calculate the conversion rate between consecutive steps. Onboardics builds this automatically from your tracking data. See also: Funnel Analysis | Drop-Off Rate

Conversion Rate

Definition: The percentage of users who complete a specific desired action divided by the total users who had the opportunity to complete it. Can measure signup conversion, activation conversion, paid conversion, or any step-to-step transition. Why it matters: Conversion rate is the universal metric for comparing funnels, testing changes, and benchmarking performance. Small improvements compound: a 5-point conversion lift at signup multiplies through every downstream metric. How to measure: (users who converted ÷ users who had the opportunity) × 100, measured over a defined window. Always pair with sample size — a 30% conversion on 10 users is not a signal. See also: Conversion Funnel | Activation Rate | A/B Testing

Custom Milestone

Definition: A success metric you define in your own words that maps to specific user actions in your product. Instead of using generic proxy metrics, you describe what matters — "activation means they booked a consultation" — and the system tracks it. Why it matters: Every product has a unique definition of success. Off-the-shelf analytics force you into generic metrics like "page views" or "session duration" that miss what actually matters. Custom milestones align your dashboard with your business reality. How to measure: In Onboardics, describe your milestones in plain English in Settings. AI maps your descriptions to trackable event conditions automatically. See also: Activation Rate | North Star Metric

Day-N Retention

Definition: The percentage of users who return to your product on a specific day after signup. Day-1 retention measures how many come back the next day. Day-7 and Day-30 are the most commonly tracked intervals. Why it matters: Day-N retention reveals the shape of your retention problem. A sharp drop on Day 1 means your onboarding fails immediately. A gradual decline through Day 7 suggests users try the product but do not find enough value to build a habit. How to measure: For each signup cohort, check how many users had at least one session on day N. Divide by total cohort size. Plot across multiple N values to see the retention curve. See also: Retention Curve | Churn Rate

Drop-Off Rate

Definition: The percentage of users who leave at a specific step in a funnel without continuing to the next step. If 500 users reach your pricing page and only 150 click "Start free trial," the drop-off rate at that step is 70%. Why it matters: Drop-off rate pinpoints exactly where your onboarding breaks. Instead of guessing, you see the precise step that loses the most users. Fixing the highest drop-off step has the single biggest impact on your overall conversion rate. How to measure: Subtract the next step's user count from the current step's user count, then divide by the current step's count. Onboardics highlights the worst drop-offs automatically with AI diagnosis. See also: SaaS onboarding drop-off patterns | Conversion Funnel

Engagement Score

Definition: A composite metric that combines multiple user activity signals — sessions, feature usage, time spent, actions taken — into a single number representing how actively a user interacts with your product. Why it matters: No single metric captures engagement fully. A user who logs in daily but only views one page is less engaged than one who uses three features per session. An engagement score gives you a holistic view that predicts retention and expansion revenue. How to measure: Weight the activities that matter most to your product (feature use, session frequency, depth of interaction), normalize to a 0-100 scale, and track over time per user and per cohort. See also: Feature Adoption | MAU

Event Tracking

Definition: The practice of capturing discrete user actions (page views, clicks, form submissions, custom actions) along with metadata (user ID, timestamp, element details) to build behavioral analytics. Foundational layer for every downstream metric. Why it matters: Without event tracking you have traffic counts, not behavior. Every funnel, activation rate, cohort analysis, and retention curve is ultimately computed from stored events. How to measure: Install a tracking snippet (Onboardics, Amplitude, Mixpanel, PostHog) that captures events automatically, or instrument specific events manually via the tool's API. Auto-capture is faster to install but harder to audit; manual instrumentation is slower but explicit. See also: Event Tracking | Funnel Analysis | Click Heatmap

Feature Adoption

Definition: The percentage of your user base that has used a specific feature at least once (or regularly). If 2,000 users have access to your export feature and 400 have used it, adoption is 20%. Why it matters: Features you build but nobody uses are wasted effort. Low adoption often means users do not know the feature exists, cannot find it, or do not understand its value. Surfacing underused features through in-app guidance is one of the highest-leverage onboarding improvements. How to measure: Count unique users who triggered the feature event, divided by total eligible users. Track weekly to spot trends. Onboardics measures this on the Adoption dashboard. See also: Activation Rate | No-code onboarding flows

First Value (Time to First Value)

Definition: The elapsed time between a user's first visit (or signup) and the moment they experience your product's core value for the first time. Also called TTFV or Time to Value. Why it matters: The longer it takes a user to reach value, the more likely they are to leave before getting there. Reducing time to first value is the most direct way to improve activation rate. Every unnecessary step, confusing screen, or slow-loading page adds friction. How to measure: Calculate the median time between signup and the first occurrence of your activation event. Segment by signup source to see which channels bring users who activate fastest. See also: Aha Moment | Activation Rate

Funnel Analysis

Definition: The practice of studying how users move through a defined sequence of steps and identifying where and why they drop off. It transforms raw event data into a visual story of your user journey. Why it matters: Funnel analysis turns a vague feeling that "users are not converting" into a specific, actionable diagnosis. It answers three questions: where do users drop off, how many are lost at each step, and what changed since last week. How to measure: Define your funnel steps, instrument each one with tracking events, and visualize the progression. Onboardics does this automatically with AI-powered drop-off diagnosis. See also: Drop-Off Rate | Drop-off patterns

In-App Guidance

Definition: Contextual UI elements — tooltips, modals, banners, guided tours, and checklists — that appear inside your product at the right moment to help users complete a task or discover a feature. Built with a no-code editor, not custom code. Why it matters: Users do not read documentation. In-app guidance meets users exactly where they are, in the moment they need help. It reduces support tickets, accelerates activation, and drives feature adoption without requiring any engineering work to deploy. How to measure: Track completion rate of each flow, time to complete, and the downstream impact on activation or feature adoption for users who saw the guidance vs. those who did not. See also: No-code onboarding flows | Behavior-Triggered In-App Guides

In-App Message

Definition: A message displayed inside a product rather than in email or push. Includes tooltips, modals, banners, guided tours, and checklists. Shown based on user behavior or context at the moment it is most likely to help. Why it matters: Users engaging with your product are already giving you attention; in-app messages reach them with zero friction. Compared to email, in-app messages have 10–50x higher engagement because they appear exactly when and where context is relevant. How to measure: Track impressions (how many users saw it), completions (how many followed through), and dismissals (how many closed without completing). Compare activation rates for users who saw the message vs. a control group. See also: In-App Guidance | Tooltip | Behavior-Triggered In-App Guides

JavaScript Error (JS Error)

Definition: An uncaught exception or unhandled promise rejection that occurs in a user's browser while using your product. Captured automatically by analytics tools that install error listeners. Usually correlates with failed conversions or churn. Why it matters: Users hitting JavaScript errors are silently churning. They rarely file support tickets — they just leave. Capturing errors automatically with PII redaction lets you find “users who hit an error before converting” as a high-intent segment to save or debug. How to measure: Install a tracking snippet that listens to window.error and unhandledrejection events. Redact sensitive patterns (tokens, emails, UUIDs, file paths) before storing. Segment error events against the funnel to identify error-correlated drop-offs. See also: Automatic JS Error Capture | Event Tracking | Rage Click

Magic Moment

Definition: A synonym for the aha moment — the instant a user "gets it" and sees why your product is valuable. The term is often attributed to early Facebook growth teams describing the moment a new user found and connected with friends. Why it matters: Naming this moment makes it concrete and measurable. Once you identify your magic moment, every onboarding decision becomes simpler: does this step move users toward the magic moment or away from it? If away, remove it. How to measure: Same as aha moment — correlate early user actions with long-term retention to find the action most predictive of staying. See also: Aha Moment | Activation Rate

MAU (Monthly Active Users)

Definition: The count of unique users who interact with your product at least once during a calendar month. It is the standard unit for measuring product reach and is used across the SaaS industry for pricing, benchmarking, and investor reporting. Why it matters: MAU tells you the size of your active audience. Growing MAU with stable retention means your product is healthy. Growing MAU with rising churn means you are filling a leaky bucket. Always pair MAU with retention data for the full picture. How to measure: Count distinct user IDs (or session IDs for anonymous products) with at least one event in the month. Onboardics pricing tiers are based on MAU. See also: Pricing | Engagement Score

Multi-App Analytics

Definition: The ability to track multiple websites, applications, or environments under a single product analytics account. Each app has its own tracking identifier but shares the parent account's dashboards, integrations, and team access.

Why it matters: Most SaaS companies have more than one customer-facing surface. Multi-app analytics gives you unified insight without forcing you to pay for separate accounts.

How to measure: Configure separate apps per surface, install distinct snippets, then filter dashboards by app or view all apps combined.

North Star Metric

Definition: The single metric that best captures the core value your product delivers to users. For Slack it might be messages sent per team per day. For Airbnb it might be nights booked. It aligns every team around one measurable outcome. Why it matters: Without a north star metric, teams optimize for different things — marketing chases signups, product chases engagement, support chases ticket closure. A north star metric unifies the company around the outcome that actually drives sustainable growth. How to measure: Choose the metric most correlated with revenue and retention. Track it weekly. Use custom milestones to make your north star metric the center of your Onboardics dashboard. See also: Activation Rate | Custom Milestone

Onboarding Checklist

Definition: A persistent UI element (usually bottom-right or dashboard-pinned) showing new users the 3–7 setup tasks they need to complete to activate. Tasks check off automatically as they're completed. The checklist stays visible until all items are done. Why it matters: Checklists work because they turn ambiguous “getting started” into concrete next-action clarity. Products with well-designed checklists consistently show 15–30% higher activation than products that rely on passive tooltips alone. How to measure: Track completion rate per checklist item (where users drop) and overall checklist-finish rate. The single most important metric: do users who finished the checklist activate at a higher rate than users who skipped it? See also: No-Code Flow Builder | User Onboarding | Activation Rate

Path Analysis

Definition: The study of the actual navigation sequences users take through your product, as opposed to the ideal funnel you designed. Path analysis reveals the real routes users follow, including detours, loops, and dead ends. Why it matters: Users rarely follow the path you expect. Path analysis uncovers surprising patterns — maybe users who convert always visit the pricing page before the feature tour, or maybe users who churn always get stuck in the settings page. These insights are invisible in a funnel view. How to measure: Aggregate user navigation sequences and group by outcome (converted vs. churned). Visualize common paths as a flow diagram. Onboardics provides this on the Paths dashboard. See also: Funnel Analysis | Rage click analysis

Paywall

Definition: A UI surface that blocks access to some functionality until the user pays, upgrades, or completes an action. Can be hard (can't continue without paying) or soft (can continue with limitations). A major drop-off cause in onboarding when unexpected. Why it matters: Paywalls encountered unexpectedly are the fastest way to lose users in the first session. Users who hit a paywall before seeing value churn at 2–3x the rate of users who hit it after activation. Position paywalls after the aha moment, not before. How to measure: Track paywall impressions, dismissal rate, and post-paywall retention. Segment users who hit the paywall by where in the funnel it appeared — pre-activation vs. post-activation drop rates are usually dramatically different. See also: Drop-Off Rate | Activation Rate | Aha Moment

Product Analytics

Definition: The discipline of measuring how users interact with a product to inform product decisions. Distinct from marketing analytics (measures what brought users in) and web analytics (measures page-level behavior). Focuses on feature adoption, activation, retention, and conversion. Why it matters: Product analytics turns the question “what's broken in our product?” from opinion into data. Every decision — which feature to prioritize, where to place a tooltip, whether to simplify onboarding — should be backed by a product analytics signal. How to measure: Install a product analytics tool (Onboardics, Amplitude, Mixpanel, PostHog, Heap) that captures user events, then build funnels, retention curves, and cohort analyses against your activation milestones. See also: Event Tracking | Funnel Analysis | Cohort Analysis

Product-Led Growth (PLG)

Definition: A go-to-market strategy where the product itself is the primary driver of acquisition, activation, and expansion. Users discover value through self-serve usage rather than through sales calls, demos, or marketing nurture sequences. Why it matters: PLG companies grow faster with lower customer acquisition costs because the product does the selling. But PLG only works if onboarding is excellent — if users cannot reach value on their own, they leave. This is why onboarding analytics is the foundation of every PLG strategy. How to measure: Track self-serve signup-to-activation rate, viral coefficient (users inviting other users), and expansion revenue from product usage (upgrades triggered by hitting plan limits). See also: User Onboarding | Activation Rate

Rage Click

Definition: A rapid sequence of repeated clicks on the same element, typically three or more clicks within one to two seconds. It signals that a user expected something to happen and it did not — a broken button, a slow-loading action, or a confusing UI element. Why it matters: Rage clicks are one of the clearest signals of user frustration. Each one represents a moment where a user almost gave up. Fixing the elements that trigger the most rage clicks has an outsized impact on user satisfaction and reduces drop-off. How to measure: Detect clusters of 3+ clicks on the same target within 1.5 seconds. Aggregate by element to find the worst offenders. Onboardics detects rage clicks automatically and surfaces them in anomaly detection. See also: Rage click analysis | Drop-Off Rate

Retention Curve

Definition: A graph showing the percentage of users who return to your product over time, plotted from signup day forward. The x-axis is time (days or weeks), the y-axis is the percentage still active. Every product's retention curve eventually flattens — the question is where. Why it matters: The shape of your retention curve tells you everything. A curve that flattens above 20% at day 30 suggests a sustainable product. A curve that approaches zero means your product has a fundamental value problem. Comparing curves before and after onboarding changes measures real impact. How to measure: For each cohort, calculate the percentage of users active on each subsequent day. Plot all cohorts on the same axes. View yours on the Retention dashboard. See also: Day-N Retention | Cohort Analysis

Scroll Depth

Definition: The maximum percentage of a page a user scrolled before leaving or navigating away. Commonly bucketed to 0%, 25%, 50%, 75%, 100% for analytics aggregation. Captured on pagehide by modern tracking snippets. Why it matters: Scroll depth is one of the strongest engagement signals. Users who scroll to the bottom are qualitatively different from users who bounce at 25% — they absorbed the content. Power audience segments like “engaged readers” on blog or marketing pages. How to measure: A tracking snippet with a passive scroll listener records the max scroll percentage per page and emits a scroll_depth event at page exit. Aggregate by path to find content that retains attention vs. content that bounces. See also: Rich Engagement Events | Bounce Rate | Engagement Score

Session Replay

Definition: A recording of a user's browser session that can be played back as a video, showing every mouse movement, click, scroll, and page transition exactly as the user experienced it. It is the closest you can get to watching over a user's shoulder. Why it matters: Quantitative data tells you what happened. Session replays tell you why. When your funnel shows a 60% drop-off on the pricing page, a replay shows you the user scrolling up and down three times looking for information that is not there. Replays turn abstract metrics into visceral understanding. How to measure: Session replays are not a metric — they are a qualitative tool. Use them to investigate specific drop-off points identified by funnel analysis or rage click detection. See also: Rage Click | Path Analysis

Time on Page

Definition: The duration (usually in seconds) a user spent viewing a specific page before navigating away or closing the tab. Measured from page load to pagehide event. Separate from session duration (which spans multiple pages). Why it matters: Time on page distinguishes “users who looked and left” from “users who read and engaged.” Low time on critical onboarding pages is a diagnostic signal — the page confused them or didn’t answer their question. How to measure: Capture timestamp on page load and pagehide, emit a time_on_page event with duration in seconds. Beware: time on page is unreliable for the final page of a session unless the snippet handles pagehide (which most browsers de-prioritize on close). See also: Bounce Rate | Scroll Depth | Engagement Score

Tooltip

Definition: A small overlay popup anchored to a specific UI element, shown on hover, click, or trigger condition. Usually contains a single sentence of guidance or explanation. The most common in-app guidance primitive. Why it matters: Tooltips work because they appear where context is highest — next to the element the user is about to interact with. Lower friction than modals (which interrupt), more targeted than banners (which are page-level). Ideal for single-action guidance like “click here next.” How to measure: Track impressions (when the tooltip appeared), hover duration, and click-through (whether the user followed the guidance). Target completion rate: 60%+ for well-targeted tooltips. Lower suggests the tooltip is appearing in the wrong place or the copy is unclear. See also: No-Code Flow Builder | In-App Message | Onboarding Checklist

User Activation

Definition: The process and moment of a new user reaching your product's first meaningful value milestone. It is not just signing up or logging in — it is completing the action that makes them understand why your product exists. Why it matters: Activation is the bridge between acquisition and retention. A user who signs up but never activates is functionally the same as a user who never signed up at all. Improving the activation process is the highest-leverage work in SaaS growth. How to measure: Define your activation milestone, then measure the percentage of signups who reach it and the time it takes. Use cohort analysis to track whether recent changes improved activation. See also: Activation Rate | Aha Moment

User Journey

Definition: The full sequence of steps a user takes through a product from first visit through activation, engagement, and potentially advocacy or churn. Includes the pages they visit, features they try, flows they complete, and drop-off points they hit. Why it matters: Analyzing journeys in aggregate reveals where users converge (common paths to success) and diverge (paths to failure). This is the foundation for identifying where to intervene with in-app guidance, better copy, or feature adjustments. How to measure: Use path analysis to visualize the sequences of pages and events users actually take. Compare journeys of activated users vs. churned users to find the divergence points where intervention can lift activation. See also: Path Analysis | Path Analysis | User Onboarding

User Onboarding

Definition: The guided process that takes a new user from their first interaction with your product to the point where they can independently extract value from it. It includes every touchpoint — welcome screens, setup wizards, tooltips, emails, and documentation. Why it matters: Onboarding is the single biggest lever for SaaS growth. A product with great features but poor onboarding will always lose to a product with good features and great onboarding. The first five minutes of a user's experience determine whether they stay for five years. How to measure: Track completion rates of each onboarding step, time to activation, and Day-7 retention for new users. Compare users who completed onboarding vs. those who skipped steps. Onboardics measures all of this automatically. See also: In-App Guidance | Product-Led Growth

Have a term we should add? Let us know →

Read the FAQ →