Trial activation funnel
Shows how far trial users get through setup and core feature use before the trial ends, and which sources bring trials that activate.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Track trials through setup
Coming soonBlu builds a step
About this recipe
When to use it
Not every trial milestone matters equally. This funnels real trial-start, session, and journey-goal events together, so you can see which milestones trial users who convert actually hit.
What it delivers
Builds a trial milestone funnel from real subscription_created (trial), session_start, and journey-goal-completion events, tracking progress through the trial period.
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 how far trial users get through setup and core feature use before the trial ends, and which sources bring trials that activate.”
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.
- 01Track trials through setupCreate a Funnel report called "Trial Activation Funnel". Steps: 1. Event "Subscription started" where trial_end and trial_start are populated: "Started Trial" 2. Event "Session start" by the same user within 24h of step 1: "First Return Session" 3. Event "Completed a journey goal" where journey_id matches the integration/setup journey: "Completed Setup Goal" 4. Event "Completed a journey goal" where journey_id matches the core-feature-use journey: "Used Core Feature" 5. Event "Completed a journey goal" where journey_id matches the full-activation journey AND occurred within 14 days of trial start: "Fully Activated" Conversion window: 14 days Breakdown: By Users.UTM source Compare: Previous period (prior 14 days) For each step, also surface: - Median time-to-convert from previous step - Per-source conversion rate at each stage Annotations: - Flag if the % of trials that hit Step 3 within 24 hours is below 50%: first-day setup is a strong activation predictor. - Flag if median time from Step 1 to Step 4 exceeds 48 hours: the time-to-value benchmark for self-serve PLG. - Flag any source where Step 5 (full activation) rate is below 15%. - Highlight sources where Step 5 rate exceeds 35%. Surface the single highest-leverage step to optimize: largest drop-off × largest downstream lift on Step 5. Taxonomy notes: - "integration_connected" and "onboarding_started" as standalone events do not exist. Setup milestones are tracked via Completed a journey goal events emitted by the relevant onboarding journey. - Each onboarding milestone (setup, core-feature use, full activation) corresponds to a different journey_id in the project's journey configuration.
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 /trial-activation-funnel 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.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 