Growth Marketing skill 10 of 13

Funnel Analysis SKILL.md

The Funnel Analysis skill makes Claude, Codex or another AI agent find where and for whom value leaks between entry and goal. It defines funnel steps from events with time windows, measures step and overall conversion and time between steps, segments by device, channel, plan and cohort, sizes each opportunity, explains leaks with recordings, surveys and support tickets and turns them into experiments.

funnel-analysis/SKILL.md, version 1.0.0, 1,472 words.

A funnel shows how many people move through each step towards a goal: visit, sign up, activate, pay, renew. The point isn't the chart; it's finding the step where the most value is lost, understanding why, and choosing what to fix. Many funnel analyses stop at "conversion is low at step three", which describes the problem without explaining it.

This skill builds funnels from event data, segments them to find where and for whom value leaks, combines numbers with qualitative evidence to explain the leak, sizes the opportunity and turns it into experiments.

Operating principles

  1. Define steps from events. Each step is a tracked event with a clear definition and time window.
  2. Segment before concluding. Averages hide problems; device, channel, plan and cohort often explain differences.
  3. Size the opportunity. A small improvement at a high-volume step can beat a big one at a low-volume step.
  4. Find the why. Recordings, surveys, interviews and support tickets explain what numbers can't.
  5. End with experiments. A funnel analysis that doesn't change the backlog was a report, not an analysis.

Common funnels

BusinessFunnel
SaaS self-serveVisit, sign-up, onboarding step(s), activation, trial to paid, retained month 2
E-commerceVisit, product view, add to cart, checkout start, purchase, repeat purchase
MarketplaceSearch, listing view, contact or request, transaction, review
Mobile appInstall, open, sign-up, key action, day-7 return, subscription
B2B sales-ledVisit, lead, MQL, SQL, opportunity, won

When to use, and when not to

Use it when a conversion rate drops, when planning experiments, after a redesign, when comparing channels or segments, and in growth audits.

Don't use it for long-term retention curves (cohort-retention-analysis) or landing page tests specifically (the Performance Marketing landing-page-cro skill).

Inputs to ask for, in one message

  1. The goal and the steps between entry and goal.
  2. Event data or analytics access (GA4, Amplitude, Mixpanel, PostHog, warehouse).
  3. Segments of interest: device, channel, plan, country, new versus returning.
  4. Qualitative sources: recordings, surveys, support tickets, interviews.
  5. Recent changes (releases, campaigns, pricing).

Raw SKILL.md file

.md

This is the exact file agents read, including the credit header and licence notice. Save it as funnel-analysis/SKILL.md.

---
name: funnel-analysis
description: "Build and analyse funnels from event data to find where and for whom value leaks: step definitions with windows, step and overall conversion, time between steps, segment breakdowns by device, channel, plan and cohort, opportunity sizing, diagnosis with recordings, surveys and support tickets, evidence-based hypotheses for the backlog and weekly monitoring. Use whenever someone asks for funnel analysis, conversion drop-off, why users don't convert, sign-up or activation funnels, checkout drop-off, where the biggest leak is or how to size a funnel opportunity."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/growth-marketing/funnel-analysis/
  category: marketing
  subcategory: growth-marketing
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Funnel Analysis

A funnel shows how many people move through each step towards a goal: visit, sign up, activate, pay, renew. The point isn't the chart; it's finding the step where the most value is lost, understanding why, and choosing what to fix. Many funnel analyses stop at "conversion is low at step three", which describes the problem without explaining it.

This skill builds funnels from event data, segments them to find where and for whom value leaks, combines numbers with qualitative evidence to explain the leak, sizes the opportunity and turns it into experiments.

## Operating principles
1. **Define steps from events.** Each step is a tracked event with a clear definition and time window.
2. **Segment before concluding.** Averages hide problems; device, channel, plan and cohort often explain differences.
3. **Size the opportunity.** A small improvement at a high-volume step can beat a big one at a low-volume step.
4. **Find the why.** Recordings, surveys, interviews and support tickets explain what numbers can't.
5. **End with experiments.** A funnel analysis that doesn't change the backlog was a report, not an analysis.

## Common funnels
| Business | Funnel |
|---|---|
| SaaS self-serve | Visit, sign-up, onboarding step(s), activation, trial to paid, retained month 2 |
| E-commerce | Visit, product view, add to cart, checkout start, purchase, repeat purchase |
| Marketplace | Search, listing view, contact or request, transaction, review |
| Mobile app | Install, open, sign-up, key action, day-7 return, subscription |
| B2B sales-led | Visit, lead, MQL, SQL, opportunity, won |

## When to use, and when not to
Use it when a conversion rate drops, when planning experiments, after a redesign, when comparing channels or segments, and in growth audits.

Don't use it for long-term retention curves (`cohort-retention-analysis`) or landing page tests specifically (the Performance Marketing `landing-page-cro` skill).

## Inputs to ask for, in one message
1. The goal and the steps between entry and goal.
2. Event data or analytics access (GA4, Amplitude, Mixpanel, PostHog, warehouse).
3. Segments of interest: device, channel, plan, country, new versus returning.
4. Qualitative sources: recordings, surveys, support tickets, interviews.
5. Recent changes (releases, campaigns, pricing).

## Workflow

### Step 1. Define the funnel
List steps as events, with the time window (for example sign-up to activation within 7 days) and whether steps must happen in order.

### Step 2. Measure overall conversion
Step-to-step and overall conversion, plus median time between steps.

### Step 3. Segment
Break down by device, channel, plan, country, cohort and new versus returning. Look for segments with very different conversion.

### Step 4. Size the opportunity
For each step: users lost × value per converted user. Model what a realistic improvement (for example closing half the gap to the best segment) would add.

### Step 5. Diagnose the why
Watch session recordings at the leaking step, run a one-question survey ("What stopped you?"), read support tickets and talk to users.

### Step 6. Form hypotheses
Write evidence-based hypotheses for the biggest leaks.

### Step 7. Feed the backlog
Score hypotheses and add them to the experiment backlog.

### Step 8. Monitor
Track the funnel weekly with alerts for sudden drops.

## Opportunity sizing example
| Step | Users entering | Conversion | Best segment conversion | Users gained if gap halved | Value per user | Monthly value |
|---|---|---|---|---|---|---|
| Sign-up to activation | 10,000 | 22% | 35% (desktop) | 650 | £40 | £26,000 |
| Activation to paid | 2,200 | 18% | 24% (team plans) | 66 | £300 | £19,800 |
Illustrative; use your own values.

## Qualitative methods at the leaking step
| Method | What it shows | Effort |
|---|---|---|
| Session recordings | Where people hesitate, error out or rage-click | Low |
| One-question exit survey | "What stopped you?" in users' words | Low |
| Support ticket review | Recurring problems and confusion | Low |
| Five-user usability test | Why the step is hard | Medium |
| Customer interviews | Motivations and alternatives | Medium |
Five to ten recordings or interviews at the leaking step usually reveal the main pattern.

## Funnel health dashboard
- Step conversion and overall conversion, weekly, with last year and target.
- Segment view for device, channel and plan.
- Median time between key steps.
- Alerts when any step falls by more than its normal weekly variation.
- Annotations for releases, campaigns and tracking changes.

## Open versus closed funnels
| Type | Counts | Use when |
|---|---|---|
| Closed (strict order) | Users who complete steps in sequence | The path is fixed (checkout, sign-up form) |
| Open (any order) | Users who complete each step at any point | Users can skip or reorder steps (onboarding checklists) |
| Path analysis | The actual routes users take | You don't know the real path yet |
Choose deliberately; the same data can show very different conversion depending on the type.

## Funnel query example (SQL)
```sql
WITH s AS (
  SELECT user_id,
         MIN(CASE WHEN event = 'signed_up' THEN ts END) AS signed_up,
         MIN(CASE WHEN event = 'connected_bank' THEN ts END) AS connected,
         MIN(CASE WHEN event = 'first_transaction' THEN ts END) AS activated
  FROM events
  WHERE ts >= '2026-09-01'
  GROUP BY user_id
)
SELECT COUNT(signed_up) AS signed_up,
       COUNT(CASE WHEN connected <= signed_up + INTERVAL '14 days' THEN 1 END) AS connected_14d,
       COUNT(CASE WHEN activated <= signed_up + INTERVAL '14 days' THEN 1 END) AS activated_14d
FROM s WHERE signed_up IS NOT NULL;
```
Adapt event names and date syntax to your warehouse.

## Funnel review cadence
- Weekly: step conversion against last year and target, with alerts.
- Monthly: segment breakdowns and the largest gaps.
- Quarterly: full analysis with sizing, diagnosis and a refreshed hypothesis list.
Annotate every release, campaign and tracking change so movements can be explained.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Steps out of order | Use open funnels or path analysis instead of strict sequences |
| Long time between steps | Use cohort-based funnels with appropriate windows |
| Tracking gaps | Fix tracking before drawing conclusions (`tracking-plan`) |
| Small numbers | Combine periods; focus on large differences; add qualitative evidence |
| Sudden drop | Check releases, tracking changes and traffic mix before redesigning |

## Handoffs to related skills
- Experiments: `experiment-design`, `growth-experiment-backlog`
- Retention after the funnel: `cohort-retention-analysis`
- Event definitions: `tracking-plan`
- Weekly monitoring: `growth-reporting`
- Landing pages for paid traffic: the Performance Marketing `landing-page-cro` skill

## Worked example
A fintech app's sign-up to activation conversion (first card transaction within 14 days) was 22%. Segmenting showed Android users converted at half the rate of iOS users, mostly at identity verification. Recordings revealed the camera step failed on many older Android phones, and support tickets confirmed it. Sizing showed closing half the gap was worth more than any other funnel change. The team added a document upload fallback and clearer instructions; an experiment confirmed a large lift in Android verification completion and activation.

## Output format
```
# Funnel analysis: <funnel>, <date>
## Funnel definition (steps, events, windows)
## Overall conversion and time between steps
## Segment breakdown and biggest gaps
## Opportunity sizing
## Diagnosis (quantitative and qualitative evidence)
## Hypotheses and backlog entries
## Monitoring and alerts
```

## Common mistakes
- Concluding from averages without segmenting.
- Optimising low-volume steps first.
- Describing leaks without explaining them.
- Trusting funnels with broken tracking.
- Analyses that never become experiments.

## Questions to ask before you analyse
- What is the goal, and which events define each step?
- Which segments might behave differently?
- What changed recently in the product or traffic?

## Self-check before you answer
- Are steps defined from events with windows?
- Did I segment and size opportunities?
- Did I combine numbers with qualitative evidence?
- Did hypotheses go into the backlog?

## Further reading
- Amplitude, funnel analysis guides: https://amplitude.com/blog
- PostHog, funnels documentation: https://posthog.com/docs/product-analytics/funnels

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/growth-marketing/funnel-analysis/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

Workflow

Step 1. Define the funnel

List steps as events, with the time window (for example sign-up to activation within 7 days) and whether steps must happen in order.

Step 2. Measure overall conversion

Step-to-step and overall conversion, plus median time between steps.

Step 3. Segment

Break down by device, channel, plan, country, cohort and new versus returning. Look for segments with very different conversion.

Step 4. Size the opportunity

For each step: users lost × value per converted user. Model what a realistic improvement (for example closing half the gap to the best segment) would add.

Step 5. Diagnose the why

Watch session recordings at the leaking step, run a one-question survey ("What stopped you?"), read support tickets and talk to users.

Step 6. Form hypotheses

Write evidence-based hypotheses for the biggest leaks.

Step 7. Feed the backlog

Score hypotheses and add them to the experiment backlog.

Step 8. Monitor

Track the funnel weekly with alerts for sudden drops.

Opportunity sizing example

StepUsers enteringConversionBest segment conversionUsers gained if gap halvedValue per userMonthly value
Sign-up to activation10,00022%35% (desktop)650£40£26,000
Activation to paid2,20018%24% (team plans)66£300£19,800

Illustrative; use your own values.

Qualitative methods at the leaking step

MethodWhat it showsEffort
Session recordingsWhere people hesitate, error out or rage-clickLow
One-question exit survey"What stopped you?" in users' wordsLow
Support ticket reviewRecurring problems and confusionLow
Five-user usability testWhy the step is hardMedium
Customer interviewsMotivations and alternativesMedium

Five to ten recordings or interviews at the leaking step usually reveal the main pattern.

Funnel health dashboard

  • Step conversion and overall conversion, weekly, with last year and target.
  • Segment view for device, channel and plan.
  • Median time between key steps.
  • Alerts when any step falls by more than its normal weekly variation.
  • Annotations for releases, campaigns and tracking changes.

Open versus closed funnels

TypeCountsUse when
Closed (strict order)Users who complete steps in sequenceThe path is fixed (checkout, sign-up form)
Open (any order)Users who complete each step at any pointUsers can skip or reorder steps (onboarding checklists)
Path analysisThe actual routes users takeYou don't know the real path yet

Choose deliberately; the same data can show very different conversion depending on the type.

Funnel query example (SQL)

WITH s AS (
  SELECT user_id,
         MIN(CASE WHEN event = 'signed_up' THEN ts END) AS signed_up,
         MIN(CASE WHEN event = 'connected_bank' THEN ts END) AS connected,
         MIN(CASE WHEN event = 'first_transaction' THEN ts END) AS activated
  FROM events
  WHERE ts >= '2026-09-01'
  GROUP BY user_id
)
SELECT COUNT(signed_up) AS signed_up,
       COUNT(CASE WHEN connected <= signed_up + INTERVAL '14 days' THEN 1 END) AS connected_14d,
       COUNT(CASE WHEN activated <= signed_up + INTERVAL '14 days' THEN 1 END) AS activated_14d
FROM s WHERE signed_up IS NOT NULL;

Adapt event names and date syntax to your warehouse.

Funnel review cadence

  • Weekly: step conversion against last year and target, with alerts.
  • Monthly: segment breakdowns and the largest gaps.
  • Quarterly: full analysis with sizing, diagnosis and a refreshed hypothesis list.

Annotate every release, campaign and tracking change so movements can be explained.

Edge cases and judgement calls

SituationWhat to do
Steps out of orderUse open funnels or path analysis instead of strict sequences
Long time between stepsUse cohort-based funnels with appropriate windows
Tracking gapsFix tracking before drawing conclusions (tracking-plan)
Small numbersCombine periods; focus on large differences; add qualitative evidence
Sudden dropCheck releases, tracking changes and traffic mix before redesigning
  • Experiments: experiment-design, growth-experiment-backlog
  • Retention after the funnel: cohort-retention-analysis
  • Event definitions: tracking-plan
  • Weekly monitoring: growth-reporting
  • Landing pages for paid traffic: the Performance Marketing landing-page-cro skill

Worked example

A fintech app's sign-up to activation conversion (first card transaction within 14 days) was 22%. Segmenting showed Android users converted at half the rate of iOS users, mostly at identity verification. Recordings revealed the camera step failed on many older Android phones, and support tickets confirmed it. Sizing showed closing half the gap was worth more than any other funnel change. The team added a document upload fallback and clearer instructions; an experiment confirmed a large lift in Android verification completion and activation.

Output format

# Funnel analysis: <funnel>, <date>
## Funnel definition (steps, events, windows)
## Overall conversion and time between steps
## Segment breakdown and biggest gaps
## Opportunity sizing
## Diagnosis (quantitative and qualitative evidence)
## Hypotheses and backlog entries
## Monitoring and alerts

Common mistakes

  • Concluding from averages without segmenting.
  • Optimising low-volume steps first.
  • Describing leaks without explaining them.
  • Trusting funnels with broken tracking.
  • Analyses that never become experiments.

Questions to ask before you analyse

  • What is the goal, and which events define each step?
  • Which segments might behave differently?
  • What changed recently in the product or traffic?

Self-check before you answer

  • Are steps defined from events with windows?
  • Did I segment and size opportunities?
  • Did I combine numbers with qualitative evidence?
  • Did hypotheses go into the backlog?

Further reading

When to use this skill, and when not to

Use it when a conversion rate drops, when planning experiments, after a redesign, when comparing channels or segments and during growth audits.

The point of a funnel isn’t the chart; it’s finding the step where the most value is lost, understanding why and choosing what to fix. Many analyses stop at “conversion is low at step three”, which describes the problem without explaining it.

Don’t use it for long-term retention (use Cohort Retention Analysis) or paid landing pages specifically (use the Performance Marketing Landing Page CRO skill).

Example prompts

  • “Find where and why sign-ups fail to activate.”
  • “Our checkout conversion dropped last week. Diagnose it.”
  • “Size the opportunity at each funnel step.”
  • “Compare our funnel for iOS and Android users.”
  • “Write the SQL for a 14-day activation funnel.”

Example output

The skill returns a fixed structure. A shortened example for an imaginary site:

# Funnel analysis: fintech sign-up to activation, 10 October 2026

| Step | Conversion | iOS | Android |
| Signed up -> verified ID | 61% | 74% | 41% |
| Verified -> first transaction (14d) | 36% | 38% | 33% |

## Diagnosis
Camera verification fails on older Android phones (recordings + tickets)

## Opportunity
Closing half the Android gap = largest funnel gain

## Experiment
Document upload fallback + clearer instructions

Every leak is sized and explained with qualitative evidence before it becomes an experiment, so effort goes to the biggest real problem.

What the agent needs from you

The skill asks for the goal and steps, event data or analytics access, segments of interest, qualitative sources such as recordings, surveys, support tickets and interviews, and recent changes to the product or traffic.

How this skill hands off to related skills

Funnels feed experiments and models. Tests go to Experiment Design and the Experiment Backlog, retention after the funnel to Cohort Retention Analysis, events to Tracking Plan and monitoring to Growth Reporting.

How to run Funnel Analysis step by step

  1. Install the skill as funnel-analysis/SKILL.md.
  2. Define the goal and steps as events with windows.
  3. Export event data or connect analytics.
  4. Add qualitative sources for the leaking steps.
  5. Review segments, sizing and diagnosis.
  6. Add hypotheses to the backlog and set funnel alerts.

Situations this skill handles

Funnels differ by business and problem. The skill handles these situations:

SituationWhat the skill does
Steps out of orderOpen funnels or path analysis
Long time between stepsCohort-based funnels with longer windows
Tracking gapsFixes tracking before concluding
Small numbersCombines periods and adds qualitative evidence
Sudden dropChecks releases and tracking first
Mobile versus desktop gapSegments and watches recordings by device

What makes this skill different

Most funnel analyses describe drop-off. This skill segments it, sizes it and explains it with qualitative evidence, then ends with hypotheses in the experiment backlog, because a funnel analysis that doesn’t change what the team tests was only a report.

It also includes ready-to-adapt SQL and a monitoring setup, so funnels are watched weekly rather than examined only when something breaks.

Practical tips from real projects

  • Segment before concluding.
  • Size before fixing.
  • Explain with recordings and surveys.
  • End with experiments.

A worked example: a fintech app’s sign-up to activation conversion was 22%. Segmenting showed Android users converted at half the iOS rate, mostly at identity verification. Recordings revealed the camera step failing on older Android phones, and support tickets confirmed it. Closing half the gap was worth more than any other funnel change, so the team added a document upload fallback and clearer instructions; an experiment confirmed a large lift in Android verification and activation.

Common funnels differ by model: visit, sign-up, onboarding, activation, trial to paid and month-two retention for SaaS; visit, product view, cart, checkout and purchase for e-commerce; search, listing view, contact, transaction and review for marketplaces; install, open, sign-up, key action, day-seven return and subscription for apps; and visit, lead, MQL, SQL, opportunity and won for B2B sales.

Opportunity sizing compares steps fairly: users entering, current conversion, the best segment’s conversion, users gained if the gap halved and the value of each. A small improvement at a high-volume step often beats a big one at a low-volume step.

Qualitative methods explain the numbers: five to ten session recordings at the leaking step, a one-question exit survey asking what stopped people, a review of support tickets, a five-user usability test and a few customer interviews usually reveal the main pattern.

Monitoring keeps the gains: weekly step conversion against last year and target, segment views, median time between steps, alerts for drops beyond normal variation and annotations for releases and campaigns.

Step definitions decide whether a funnel can be trusted. Each step is a tracked event with a clear definition, such as account created on the server or first transaction completed, plus a time window, such as within 14 days of sign-up, and a rule about order. Changing any of these changes the numbers, so the skill writes them down and reuses them in every report. When teams disagree about conversion, the cause is usually different definitions rather than different data.

Hypotheses come from combining numbers and evidence: because Android verification completion is far below iOS and recordings show camera failures on older phones, adding a document upload fallback should raise Android verification. Written this way, each hypothesis is ready for the experiment backlog with its expected effect and the metric it moves.

For B2B funnels the same logic applies at account level, with stages owned partly by sales, so the analysis includes stage definitions agreed with the sales team and longer windows between steps.

Every analysis ends with backlog entries, owners and alerts.

Frequently asked questions

Measuring how many people complete each step towards a goal, finding where they drop off, understanding why and deciding what to fix.

Averages hide problems. Device, channel, plan and cohort often explain why conversion is low at a step.

Multiply users lost at a step by the value of each converted user, and model a realistic improvement such as closing half the gap to the best segment.

Closed funnels count steps in strict order for fixed paths like checkout; open funnels count steps in any order for flexible flows like onboarding checklists.

Session recordings, one-question exit surveys, support tickets, usability tests and interviews at the leaking step.

Check releases, tracking changes and traffic mix before redesigning anything.

Changelog

  • 1.0.0, 10 October 2026: first release.

Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.