Activation funnel with velocity
Shows where new users drop out across key onboarding steps to pinpoint activation bottlenecks.
Authored by Intempt Technologies
Recipe curators
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Time each step to activation
Coming soonBlu builds a step
About this recipe
When to use it
A normal funnel tells you conversion rate per step. It doesn't tell you that users who convert still take 6 days to do it. This adds median and p75 velocity per step, so slow steps show up even when they don't cause drop-off.
What it delivers
Builds a standard activation funnel and layers median and 75th-percentile time-to-convert on every step, distinguishing steps where users drop from steps where they simply take too long.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Shows where new users drop out across key onboarding steps to pinpoint activation bottlenecks.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Time each step to activationCreate a Funnel report called "Activation with Step Velocity". Steps: 1. Event "User created": "Signed Up" 2. Event "Session start" within 24h of User created: "First Return" 3. Event "Completed a journey goal" where journey_id matches the setup journey: "Completed Setup" 4. Event "Completed a journey goal" where journey_id matches the core-feature journey: "Used Core Feature" 5. Event "Completed a journey goal" where journey_id matches the activation journey, with frequency: Occurred date appears 3+ times in the 7 days following step 4: "Activated (Habituated)" Conversion window: 14 days Breakdown: By Users.UTM source Compare: Previous period (prior 14 days) For each step, in addition to conversion rate, surface: - Median time-to-convert from previous step - 75th-percentile time-to-convert - Stall rate: % of users at this step who have NOT advanced after 24h, after 72h, after 7 days Annotations: - Add benchmarks: median signup to setup-complete ≤ 24 hours is the activation gold standard. - Flag any step where p75 time-to-convert exceeds 7 days (long tail of stalled users). - Flag any step where the stall-rate-at-72h is above 60%. - Highlight the step where reducing time-to-convert by 50% would have the biggest downstream activation lift. Velocity is the activation lever: drop-off tells you where users die, velocity tells you where they're stuck. Taxonomy notes: - "Habituated" Step 5 requires Lovable to compute the "3+ goal completions in 7 days" rule from Completed a journey goal timestamps grouped by user.
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /activation-funnel-with-velocity in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
