The metrics that Appcues, Userpilot, and Pendo track (and what's missing)

Every onboarding platform promises "powerful analytics." But what does that actually mean once you open the dashboard?

We spent two weeks testing the analytics capabilities of Appcues, Userpilot, and Pendo across real onboarding flows. The gap between marketing claims and what you can actually measure is wider than you'd expect. Pendo tracks 40+ behavioral metrics out of the box. Appcues tracks exactly what happens inside Appcues-built flows, and nothing else. Userpilot sits somewhere in between, with solid funnel tools that occasionally freeze under load.

This guide breaks down what each tool actually measures, where the data lives, and which metrics none of them track at all.

npm install @tourkit/core @tourkit/react @tourkit/analytics

If you want analytics you fully own, User Tour Kit's analytics package lets you pipe events to any provider: Mixpanel, PostHog, Amplitude, or your own data warehouse.

What is an onboarding tool analytics comparison?

An onboarding tool analytics comparison evaluates the specific metrics, dashboards, and data capabilities that each platform provides for measuring user onboarding outcomes. Unlike feature comparisons that focus on tooltip styling or checklist templates, an analytics comparison examines what data each tool captures, how it stores that data, what queries you can run, and which business-critical metrics fall outside its tracking scope entirely.

Most vendor comparison pages skip analytics depth. They'll list "analytics included" as a checkbox without specifying whether that means basic flow completion rates (Appcues) or full retroactive behavioral analysis (Pendo). The gap matters because the analytics you can access directly determines which onboarding questions you can answer.

Why onboarding analytics matter more than flow completion

The average SaaS activation rate sits at 37.5% according to the ProductLed Benchmark Report. Improving that number requires diagnosing where users stall, not just confirming they finished your tooltip sequence. Teams that only track flow completion miss the 62.5% of users who never activate, because those users often don't encounter the onboarding flow at all.

Onboarding analytics should answer three questions: did users see the guidance, did they take the desired action, and did that action lead to lasting engagement? Appcues answers the first. Userpilot answers the first two. Pendo gets closest to all three. None of them close the loop to revenue.

What metrics does Appcues actually track?

Appcues analytics are scoped entirely to flows you build inside the Appcues editor. As of April 2026, the platform tracks flow-level completion rates, individual step progression, button clicks within flows, and NPS/survey response aggregates. That's roughly where it ends.

There's no funnel builder. No path analysis. No session replay. No retroactive analytics. If you didn't tag an event before launching a flow, you can't go back and query it later. The Appcues analytics documentation confirms that deeper behavioral analysis requires exporting data to a dedicated product analytics tool like Mixpanel or Amplitude.

For teams that only care about "did the user finish this tooltip sequence," Appcues is fine. But if you need to answer "what did the user do after the tour ended," you're writing Segment integrations.

What Appcues measures well

• Flow completion and drop-off per step
• NPS response distribution and trends
• Checklist task completion rates
• Goal tracking tied to flow exposure

What Appcues doesn't measure

• Page-level or feature-level engagement outside flows
• User paths before or after onboarding
• Session duration or frequency metrics
• Retroactive event analysis
• Cohort comparison across time periods

One Reddit user in r/ProductManagement put it bluntly: "Appcues analytics is more of a report card for your flows than actual product analytics" (source: Reddit r/ProductManagement, 2025).

What metrics does Userpilot actually track?

Userpilot offers a broader analytics surface than Appcues, positioning itself as a product analytics tool that also does onboarding. As of April 2026, it includes funnel analysis, cohort breakdowns, path analysis, session replay, and four pre-built dashboards (Product Usage, New Users, Power Users, Company Insights).

The funnel builder lets you define multi-step conversion sequences and compare them across user segments. Cohort analysis tracks retention by signup week or first-touch event. Session replay shows exactly what users clicked, scrolled, and ignored. On paper, this covers most of what a product team needs without a separate analytics subscription.

In practice, the experience has rough edges. Multiple G2 reviewers report the analytics interface "becomes unresponsive when filtering large datasets" and describe the dashboard organization as "confusing with reports scattered across different sections." The data is there, but finding it requires patience.

What Userpilot measures well

• Multi-step funnel conversion with segment comparison
• Weekly/monthly cohort retention curves
• Feature adoption rates by user segment
• Session replay with event timeline overlay
• NPS, CSAT, and CES scoring with trend tracking

What Userpilot doesn't measure

• Cross-product or cross-domain analytics (single-app scope)
• Revenue attribution tied to onboarding events
• Acquisition-channel correlation with activation
• Real-time data (processing delays vary by plan)
• Custom metric formulas beyond built-in templates

What metrics does Pendo actually track?

Pendo is the analytics heavyweight of the three. Its autocapture technology records every click, page view, and feature interaction without manual tagging. As of April 2026, Pendo offers path analysis, funnel analysis, cohort segmentation, session replay, a composite Product Engagement Score, and AI-powered Insights that surface behavioral anomalies.

Retroactive analytics is the real differentiator. Because Pendo captures everything by default, you can define a new metric today and query it against six months of historical data. Neither Appcues nor Userpilot can do this. If a PM asks "how many users clicked the export button last quarter," Pendo already has the answer even if nobody thought to tag that button.

The tradeoffs are cost and accuracy. According to Vendr's 2025 SaaS pricing data, Pendo's median annual contract sits at $48,400, roughly 3-4x what Appcues or Userpilot cost for similar MAU counts. And data accuracy is a recurring G2 complaint: hourly data refreshes mean real-time dashboards lag behind actual behavior, and some users report click counts that "don't match what we see in Amplitude for the same events."

What Pendo measures well

• Autocaptured click, page, and feature events (retroactive)
• Product Engagement Score (composite of breadth, depth, frequency, stickiness)
• Path analysis showing navigation sequences
• Friction detection: rage clicks, dead clicks, error clicks
• AI Insights flagging unusual behavior patterns
• Guide analytics (completion, dismissal, snooze)

What Pendo doesn't measure

• Real-time behavioral data (hourly refresh cycle)
• Cross-product analytics without Pendo on every product
• Revenue or billing events (no native payment integration)
• Referral or viral loop metrics
• Mobile-native analytics (web SDK only for most plans)

The full comparison: analytics features side by side

Here's every analytics capability mapped across all three tools, verified against their April 2026 documentation and our testing:

The pattern is clear: Appcues is a flow builder with basic reporting, Userpilot is a mid-range analytics tool with onboarding features, and Pendo is a full product analytics platform with onboarding bolted on. Your choice depends on whether you need analytics that covers onboarding or onboarding that covers analytics.

The metrics none of them track

After testing all three platforms across real onboarding flows, we identified six metric categories that Appcues, Userpilot, and Pendo all fail to measure. These gaps cover survey fatigue accumulation, scheduling-aware delivery, cross-mechanism correlation, HEART and AARRR framework completeness, and developer-facing performance costs.

Survey fatigue accumulation

All three tools track individual survey response rates. None of them track cumulative survey fatigue: how many prompts, tooltips, modals, and NPS requests a single user has received across their entire lifecycle. When your NPS response rate drops from 40% to 12%, is it because users are unhappy or because you've asked them 15 questions in 30 days? None of these tools can tell you.

Scheduling-aware delivery analytics

When did users actually need help versus when did they receive it? If your tour fires at 9am PST but 40% of your users are in APAC timezones, you're showing tours during end-of-day fatigue. No current tool correlates delivery timing with engagement outcomes.

Cross-package metric correlation

Did the checklist completion drive the feature adoption, or was it the announcement banner? In siloed architectures (which all three platforms use) you can't correlate engagement across different onboarding mechanisms. Each feature reports its own metrics in isolation.

HEART framework metrics

Google's HEART framework (Happiness, Engagement, Adoption, Retention, Task success) is the industry standard for measuring UX quality, described in the Google Research paper by Kerry Rodden et al.. None of these tools natively map to HEART dimensions. You can approximate some metrics manually, but there's no built-in HEART dashboard or scoring.

AARRR pirate metrics (complete)

The AARRR framework (Acquisition, Activation, Retention, Referral, Revenue) is supposed to cover the full user lifecycle. In practice, Pendo partially covers Acquisition and all three handle Activation to varying degrees. Retention gets some coverage through cohort analysis. But Referral and Revenue? Not tracked by any of them. The two metrics most directly tied to business outcomes are invisible.

Developer-facing performance metrics

How much does your onboarding tool cost in runtime performance? None of these platforms report their own bundle size impact, JavaScript execution time, or effect on Core Web Vitals. We measured this separately. Appcues adds 200-350KB to initial page load. Pendo adds 180-300KB. Userpilot falls in the 150-280KB range depending on features enabled. Our Lighthouse performance audit of onboarding tools has the full breakdown.

How to build the analytics layer these tools miss

When your onboarding tool analytics comparison reveals gaps in what the vendors track, you have two paths forward: stack another analytics tool on top of your onboarding platform, or own the analytics layer directly in your codebase where you control the event schema and data pipeline.

The Chameleon 2025 Benchmark Report found that 3-step tours have a 72% completion rate while 7-step tours drop to 16%. Around 70% of users skip traditional linear tours entirely. User-triggered tours complete at 2-3x the rate of auto-triggered ones. These are the kinds of cross-cutting insights you need, and they require correlating data across tools.

Here's what a code-owned analytics setup looks like with Tour Kit:

// src/analytics/onboarding-metrics.ts
import { TourAnalytics } from '@tourkit/analytics';
import { posthog } from 'posthog-js';

const analytics = new TourAnalytics({
  onStepView: (event) => {
    posthog.capture('tour_step_viewed', {
      tourId: event.tourId,
      stepIndex: event.stepIndex,
      timestamp: event.timestamp,
      sessionDuration: Date.now() - sessionStart,
    });
  },
  onTourComplete: (event) => {
    posthog.capture('tour_completed', {
      tourId: event.tourId,
      totalSteps: event.totalSteps,
      completionTime: event.duration,
      userTimezone: Intl.DateTimeFormat().resolvedOptions().timeZone,
    });
  },
  onTourDismiss: (event) => {
    posthog.capture('tour_dismissed', {
      tourId: event.tourId,
      dismissedAtStep: event.stepIndex,
      reason: event.reason,
    });
  },
});

export { analytics };

The difference: you own the event schema. You decide what gets tracked. When your PM asks "how does tour completion correlate with 30-day retention," you can answer that question in PostHog without begging a vendor to add the feature.

// src/components/OnboardingFlow.tsx
import { TourProvider } from '@tourkit/react';
import { analytics } from '../analytics/onboarding-metrics';

export function OnboardingFlow({ children }: { children: React.ReactNode }) {
  return (
    <TourProvider
      analytics={analytics}
      tours={[
        {
          id: 'welcome-tour',
          steps: [
            { target: '#dashboard-nav', content: 'Start here' },
            { target: '#create-button', content: 'Create your first project' },
            { target: '#settings-icon', content: 'Customize your workspace' },
          ],
        },
      ]}
    >
      {children}
    </TourProvider>
  );
}

Tour Kit's analytics package ships at under 2KB gzipped. Compare that to the 150-350KB that SaaS onboarding tools add to your page load.

Disclosure: we built Tour Kit, so take this comparison with appropriate skepticism. The analytics architecture is genuinely different (events go to your analytics provider, not ours) but we're obviously biased toward this approach. Tour Kit doesn't have a visual editor, requires React 18+, and assumes your team can write TypeScript. That's a real limitation for product-led teams without dedicated frontend developers.

Common mistakes when evaluating onboarding analytics

Teams evaluating onboarding tools based on analytics capabilities consistently fall into three patterns that lead to overspending, duplicate data pipelines, or analytics lock-in that becomes painful during vendor transitions.

Confusing flow metrics with product metrics. A 95% flow completion rate means nothing if users churn the next week. Flow completion is an output metric. Activation, retention, and revenue impact are outcome metrics. Most teams chase the wrong one because that's what the dashboard shows first.

Paying for analytics you already have. If you're already running Amplitude or Mixpanel, Pendo's analytics overlap significantly. You're paying $48K/year for a second copy of data you can get by sending 10 custom events from your onboarding code. A discussion on Hacker News captures this well. One engineering lead noted they "ripped out Pendo analytics entirely and just pipe events to our existing Amplitude instance."

Ignoring the data ownership question. When your onboarding analytics live inside a vendor, switching tools means losing your historical data. Appcues-to-Userpilot migrations don't include analytics history. If tour completion trends over 18 months matter to your team, you need that data in a system you control. Our guide on data ownership in onboarding analytics covers this in depth.

Which onboarding analytics approach fits your team?

Average SaaS activation rates sit around 37.5%, according to the ProductLed Benchmark Report. If your activation is below that, you need analytics that diagnose why, not just report what.

Choose Appcues if: You only need to know whether your Appcues flows are working, and you already have a product analytics tool handling everything else. The analytics are limited but the flow builder is good.

Choose Userpilot if: You want decent analytics and onboarding in one tool, and your team doesn't mind occasionally fighting with the dashboard UX. Good middle ground for teams at 5,000-20,000 MAU.

Choose Pendo if: You need full behavioral analytics, retroactive querying, and AI-powered insights, and your budget supports $40K+ annually. Best for enterprise teams that want one platform for everything.

Choose code-owned analytics if: You want to define your own event schema, pipe data to your existing analytics stack, and never worry about vendor lock-in. Tour Kit's analytics docs show the full setup in about 20 lines of code.

Try the interactive Tour Kit demo to see how code-owned onboarding analytics work in practice. Or jump straight in:

npm install @tourkit/core @tourkit/react @tourkit/analytics

FAQ

What's the biggest analytics difference between Appcues, Userpilot, and Pendo?

Pendo tracks behavioral data automatically across your entire product through autocapture, letting you query events retroactively. Userpilot offers funnel and cohort analysis for onboarding-specific metrics. Appcues only tracks what happens inside Appcues-built flows. For broader onboarding tool analytics comparison, Pendo covers the widest surface area by default.

Can I use Appcues analytics without a separate product analytics tool?

Not effectively for onboarding tool analytics comparison across your full product. Appcues analytics only covers events within Appcues-built flows: completion rates, step progression, and NPS scores. For page-level engagement, user paths, or feature adoption metrics, you'll need Mixpanel, Amplitude, or a similar tool running alongside it.

How much does Pendo analytics cost compared to alternatives?

As of April 2026, Pendo's median annual contract is $48,400 according to Vendr pricing data. That's roughly 3-4x the cost of Appcues or Userpilot at similar MAU levels. The premium buys you retroactive analytics, autocapture, AI insights, and a composite Product Engagement Score that neither competitor offers natively.

What onboarding metrics should I track beyond completion rates?

Track activation rate, time-to-value, feature adoption depth, and retention correlation at 30/60/90 days. The onboarding tool analytics comparison that matters most is which tool connects these outcome metrics, not just reports flow completions.

Is there an open-source alternative for onboarding analytics?

Tour Kit's analytics package lets you define your own event schema and pipe data to PostHog, Mixpanel, Amplitude, or your own warehouse. It ships at under 2KB gzipped, giving you full control without the 150-350KB overhead that SaaS onboarding tools add.

Key takeaways

• Pendo is the only tool with retroactive analytics and autocapture, but hourly data refreshes and $48K+ annual cost make it a poor fit for teams that already run a separate analytics tool.
• None of these tools track survey fatigue, scheduling-aware delivery, cross-mechanism correlation, complete AARRR/HEART metrics, or their own performance impact. These are arguably the metrics most useful for improving onboarding.
• Code-owned analytics (Tour Kit + your existing analytics provider) costs a fraction of any SaaS tool and gives you the event schema flexibility to answer questions these platforms weren't designed for.
• The right choice depends on whether you need analytics that covers onboarding or onboarding that covers analytics. Conflating the two is how teams end up paying for duplicate data.

Related articles

Metrics & AnalyticsApr 11, 2026 · 10 min read

How to A/B test onboarding flows with Statsig + Tour Kit

Set up A/B tests on your onboarding flows using Statsig experiments and Tour Kit. Includes variant switching, metric tracking, and a working React example.

Read article

Metrics & AnalyticsApr 11, 2026 · 12 min read

Building an onboarding analytics dashboard with PostHog

Build a PostHog dashboard that tracks onboarding tour completion, step drop-off, and activation correlation. Code-first tutorial with Tour Kit analytics plugin.

Read article