agentleFS
sp1esp1e/claude-skills/funnel-analysis/SKILL.md

funnel-analysis

Skill1 starsChanged 31 days agoMITView on GitHub

Conversion funnel analysis with drop-off investigation. Use when analyzing multi-step processes, identifying conversion bottlenecks, comparing segments through a funnel, or optimizing user journeys.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ab-test-analysis and market-research.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • About-IntelligenceSkill

    ab-test-analysis

    Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations.

    Also in 3 projects that use this

  • birne-skSkill

    market-research

    Professional market research and competitive analysis using McKinsey/BCG/Bain consulting methodologies. Use when analyzing markets, competitive landscapes, customer insights, or strategic positioning. Generates hypothesis-driven research with PPTX presentation deliverables.

    Also in 3 projects that use this

The file

Files
SKILL.md

Funnel Analysis

When to use

  • Conversion is low and the team needs to know where users are dropping off
  • A product change may have affected a specific funnel step
  • Comparing conversion rates across channels, devices, or user cohorts
  • Designing an A/B test and needing a baseline to set a meaningful MDE
  • Building a regular funnel monitoring report

Process

  1. Define funnel steps and time window — list the ordered sequence of events or pages that constitute the funnel. Agree on how long a user has to complete the funnel (session, 24 hours, 7 days). Ambiguous definitions here will invalidate the analysis.
  2. Build the user-level funnel dataset — for each user who reached step 1, record which subsequent steps they completed and when, within the time window. Use scripts/funnel_analyzer.py to compute this from an events log.
  3. Calculate conversion rates — compute step-to-step conversion (users reaching step N ÷ users reaching step N−1) and overall conversion (step 1 to last step). Record absolute drop-off counts at each step.
  4. Analyse time-to-convert — for users who completed each step, calculate median, P75, and P95 time between steps. Long gaps can signal friction even without high drop-off.
  5. Segment the funnel — run the funnel separately by channel, device type, user cohort, or other dimensions. Rank segments by overall conversion rate and identify where the worst-performing segment diverges from the best. See references/funnel_design_guide.md.
  6. Prioritise and report — rank drop-off points by absolute users lost × estimated revenue impact. Produce assets/funnel_report_template.md with the funnel table, segment comparison, and ranked recommendations.

Inputs the skill needs

  • Event log data with at minimum: user_id, event_name, timestamp
  • Ordered list of funnel steps (event names in sequence)
  • Time window for funnel completion
  • Segmentation columns if a comparative analysis is needed (channel, device, plan)
  • Estimated revenue value of a conversion (for impact sizing)

Output

  • scripts/funnel_analyzer.py — builds user-level funnel from an event log, computes step conversions, drop-offs, and time-to-convert
  • references/funnel_design_guide.md — how to define funnels, choose time windows, and avoid common measurement mistakes
  • assets/funnel_report_template.md — report template: funnel overview table, drop-off analysis, segment comparison, time-to-convert, recommendations

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.