Activation Definition

Why it matters

Activation is not "logged in." It's the first measurable moment of value that correlates with retention. A strong definition makes onboarding measurable and turns "improve activation" into an engineering-ready spec.

Template

Activation event: activation_completed
Window: 24h from signup_completed (use 7d for longer setups)
Rules (workspace-level):
1. workspace_created
2. primary_object_created (project/app/dashboard)
3. key_feature_used(feature="X") or integration_connected

Metrics

Activation Rate: activated_workspaces / signup_completed_workspaces
TTV: median(signup_completed → activation_completed)

Funnel breakdown

Step completion: onboarding step conversion + time per step

Common mistakes

Too easy (doesn't represent value).
Too hard (too many steps → drop-off).
No segmentation (source/plan/role) → you can't diagnose what works.

Example output (Devtool)

Activation = workspace created + app created + first deploy/publish or integration connected + teammate invited.

Dashboard Pack Implementation — Includes a detailed Activation Dashboard section with funnel stages, SQL queries, and implementation checklists.