Skip to main content
Intempt
Coming soon

Funnel drop off by source

Runs the same acquisition to retention funnel separately for each traffic source, so you can see which channels bring people who actually stick.

Authored by Intempt Technologies

Recipe curators

Agentic workflow

Coming soon

1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Run one funnel per source

    Coming soon

    Blu builds a step

About this recipe

When to use it

Two channels can drive identical traffic volume and convert completely differently. This runs your funnel separately per utm_source, so the channel that just brings clicks stops looking the same as the channel that brings customers.

What it delivers

Runs the same conversion funnel independently for each acquisition source (Users.utm_source), surfacing per-channel conversion rate instead of one blended funnel that hides source-level differences.

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

“Runs the same acquisition to retention funnel separately for each traffic source, so you can see which channels bring people who actually stick.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. 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.

    1. 01Run one funnel per sourceCreate a Funnel report called "Funnel Drop-off by Acquisition Source". This is a configurable funnel: the user specifies which canonical events make up the funnel. Defaults if unspecified: 1. Event "User created": "Acquired" 2. Event "Completed a journey goal" (configurable journey_id): "Activated" 3. Event "Subscription started" (saas) OR "Placed order" (ecommerce): "Converted" 4. Event "Session start" with date 30+ days after the conversion event: "Retained 30 days" Conversion window: 60 days Breakdown: By Users.UTM source (top 8 sources by Step 1 volume) Compare: Previous period (prior 60 days) Render as small-multiples: one funnel per source, sorted by end-to-end conversion rate descending. Also include a summary table: - Source · Volume at Step 1 · End-to-end conversion % · Volume at final step · Per-source revenue (sum of Subscription started.amount or Placed order.total_price for users who reached Step 3+) Annotations: - Flag the source with highest end-to-end conversion AND volume above the 33rd percentile. - Flag any source where Step 1 to 2 conversion is below 50% of the average across sources (lead-quality issue). - Flag any source where Step 3 to 4 conversion is below average (conversion fine but customers don't retain). - Highlight the largest gap between sources at any single step. Surface the actual revenue-weighted ROI per source. Taxonomy notes: - All steps reference canonical events. Users.UTM source is a real first-touch attribution attribute. - Note: this recipe does NOT compute CAC because ad-spend is not in the canonical taxonomy. Per-source revenue is the closest proxy.

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /funnel-dropoff-attribution-by-source in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Intempt TechnologiesDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Intempt TechnologiesPost 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 Intempt TechnologiesReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Intempt Technologies

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post 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 Product swap in a sceneReplaces the product in a shot you already have with a different one, keeping the scene, lighting and shadow the same.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe