Required Datapoints
- List of Activated Users
- Session History (≥ 2 sessions)
- Activation Milestone Completion Timestamp
Multi-Session Activation Completion Rate measures the percentage of users who complete the full activation flow across more than one session. It helps track long-path engagement and sustained activation behavior.
Multi-Session Activation Completion Rate is a key indicator of onboarding effectiveness across time, reflecting how many users return to complete setup, team invites, or critical actions after their initial session.
Its meaning shifts depending on complexity:
A rising rate signals motivated users and clear value paths, while a low rate may reveal setup friction or unclear progression.
By segmenting by persona, plan type, or signup source, you can optimize multi-step UX, activation reminders, and lifecycle support.
Multi-Session Activation Completion Rate informs:
These are the main factors that directly impact the metric. Understanding these lets you know what levers you can pull to improve the outcome
Actionable ideas to optimize this KPI, from fast, low-effort wins to strategic initiatives that drive measurable impact.
Activities commonly tied to improving or operationalizing this KPI.
| Activity | Description |
|---|---|
| Onboarding Optimization | Onboarding Optimization is a strategic process focused on refining and streamlining the experience new customers have when adopting a product or service. It improves performance by removing friction, testing changes, and scaling what works. Relevant KPIs include Action-to-Activation Time Lag and Activation Cohort Retention Rate (Day 7/30). |
| Activation Campaigns | Activation Campaigns is a targeted initiative designed to motivate new or existing users to experience key value moments within a product or service. It coordinates execution across touchpoints so teams can move users or accounts toward the target outcome. Relevant KPIs include Multi-Session Activation Completion Rate and Percent of Users Engaging with Top Activation Features. |
| Product Education | Product Education is a strategic process focused on equipping go-to-market teams—including sales, customer success, and support—with the essential knowledge, skills, and resources to effectively position, demonstrate, and support a product. It helps teams translate strategy into repeatable execution. Relevant KPIs include Feature Adoption Rate (Early) and Feature Adoption Velocity (Top 3 Features). |
| Session Design | Session Design is a structured process focused on defining objectives, content, flow, and participant engagement strategies for interactive meetings or workshops within a Go-To-Market (GTM) framework. It gives teams a clear plan for where to focus, how to sequence work, and what to measure. Relevant KPIs include Multi-Session Activation Completion Rate. |
1,000 new users
470 completed activation after >1 session
Formula: 470 ÷ 1,000 = 47% Multi-Session Activation Completion Rate
This KPI is associated with the following stages in the AAARRR (Pirate Metrics) funnel:
This KPI is classified as a lagging Indicator. It reflects the results of past actions or behaviors and is used to validate performance or assess the impact of previous strategies.
This role is directly accountable for the KPI and is expected to drive progress and decisions around it.
These roles contribute directly to performance and typically partner on execution, reporting, or optimization.
These leading indicators influence this KPI and act as early signals that forecast future changes in this KPI.
These lagging indicators confirm, quantify, or amplify this KPI and help explain the broader business impact on this KPI after the fact.
How this KPI is structured in Cube.js, including its key measures, dimensions, and calculation logic for consistent reporting.
cube('ActivatedUsers', { sql: `SELECT * FROM activated_users`, measures: { activatedUserCount: { sql: `user_id`, type: 'countDistinct', title: 'Activated User Count', description: 'Count of unique users who have been activated.' } }, dimensions: { userId: { sql: `user_id`, type: 'string', primaryKey: true, title: 'User ID', description: 'Unique identifier for each user.' }, activationMilestoneCompletionTimestamp: { sql: `activation_milestone_completion_timestamp`, type: 'time', title: 'Activation Milestone Completion Timestamp', description: 'Timestamp when the user completed the activation milestone.' } }});cube('SessionHistory', { sql: `SELECT * FROM session_history`, measures: { multiSessionUserCount: { sql: `user_id`, type: 'countDistinct', title: 'Multi-Session User Count', description: 'Count of unique users with two or more sessions.' } }, dimensions: { userId: { sql: `user_id`, type: 'string', primaryKey: true, title: 'User ID', description: 'Unique identifier for each user.' }, sessionId: { sql: `session_id`, type: 'string', title: 'Session ID', description: 'Unique identifier for each session.' }, sessionStartTime: { sql: `session_start_time`, type: 'time', title: 'Session Start Time', description: 'Timestamp when the session started.' } }});cube('MultiSessionActivationCompletionRate', { sql: `SELECT * FROM ( SELECT au.user_id, COUNT(DISTINCT sh.session_id) as session_count FROM activated_users au JOIN session_history sh ON au.user_id = sh.user_id GROUP BY au.user_id HAVING COUNT(DISTINCT sh.session_id) >= 2 ) as multi_session_users`, measures: { multiSessionActivationCompletionRate: { sql: `user_id`, type: 'countDistinct', title: 'Multi-Session Activation Completion Rate', description: 'Percentage of users who complete the activation flow across more than one session.' } }, dimensions: { userId: { sql: `user_id`, type: 'string', primaryKey: true, title: 'User ID', description: 'Unique identifier for each user.' } }, joins: { ActivatedUsers: { relationship: 'belongsTo', sql: `${CUBE}.user_id = ${ActivatedUsers}.user_id` }, SessionHistory: { relationship: 'belongsTo', sql: `${CUBE}.user_id = ${SessionHistory}.user_id` } }});Note: This is a reference implementation and should be used as a starting point. You’ll need to adapt it to match your own data model and schema