modeling-activation-metrics

Build retention-validated activation models on PostHog warehouse views or dbt projects.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill modeling-activation-metrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: modeling-activation-metrics
Source: https://github.com/PostHog/posthog-foss/tree/main/products/data_modeling/skills/modeling-activation-metrics
Command: npx skills add https://github.com/PostHog/posthog-foss --skill modeling-activation-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often hard-code a guessed "aha moment" event as their activation metric without evidence it predicts retention. This Skill replaces that guess with a validated activation definition — a combination of early actions and count thresholds chosen by balancing reach against retention lift — and models it as a durable per-user activated flag plus an activation-rate metric.

Core Features & Use Cases

  • Candidate discovery and validation: List early actions from the event taxonomy, then measure retention lift for each candidate, combination, and count threshold before committing to a definition.
  • PostHog HogQL recipes: SQL views that flag per-user activation within N days of the first-ever event and roll up activation rate by signup cohort, with guards against false signup dates and right-censored retention windows.
  • dbt modeling: A dim_activation_criteria table holding the definition as versioned data plus fct_user_activation with per-user flags, activated_at timestamps, and schema tests.
  • Use Case: A B2B SaaS team suspects "created a project" is their activation event. The Skill validates it against week-4 retention lift, finds "ran ≥3 queries within 7 days" predicts retention better, and models that definition as an account-level activated flag.

Quick Start

Ask the assistant to find and validate which early user actions predict retention, then build an activation-rate model for your PostHog warehouse or dbt project.

Frequently Asked Questions about modeling-activation-metrics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define an activation metric for my product?

Define activation by listing candidate early actions, measuring the retention lift of each against users who did not act, and picking the definition that maximizes predictive power while keeping reach acceptable. Validate combinations and count thresholds, not just single events, before modeling.

How do I measure activation rate in PostHog with HogQL?

Compute each user's first-ever event as signup date over full history, count qualifying key actions within the early window, then roll up activated users by signup cohort week. The Skill provides activation_flag.sql and activation_retention_lift.sql recipes for this.

Can I model user activation in dbt?

Yes. The Skill provides a dim_activation_criteria model storing the definition as versioned data and fct_user_activation producing a per-user is_activated flag and activated_at timestamp, with uniqueness and not-null tests in schema.yml.

How does B2B account-level activation differ from per-user activation?

B2C activation is measured per person, while B2B activation applies at the account grain using the group identifier, where the account activates when any user meets the criteria. The same retention-lift validation method applies at both grains.

Why is my activation metric misleading or wrong?

Common causes include computing signup dates from a filtered lookback window instead of full event history, and including cohorts too recent to have a complete retention window, which drags measured lift down. Both guards are built into the provided SQL recipes.