Skip to content
cccskills
FreePublished on GitHub

funnel-analysis

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md2.7 KB
  • assets/funnel_report_template.md1.6 KB
  • references/funnel_design_guide.md2.9 KB
  • scripts/funnel_analyzer.py5.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Rigorous A/B test statistical analysis. Use when analyzing experiment results, calculating statistical significance, checking for sample ratio mismatch, or validating test design before launch.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

Track and document analytical assumptions and decisions. Use when making analytical choices, documenting trade-offs, ensuring transparency, or creating audit trails for analytical work.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

Structured, reproducible analysis documentation. Use when documenting analysis findings, creating analysis notebooks, ensuring reproducibility, or building analysis archives for future reference.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

Structure analysis approach before starting work. Use when receiving new analysis requests, breaking down complex questions into steps, or planning iterative analysis workflows.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

Pre-delivery quality assurance for analysis work. Use when reviewing analysis before sharing with stakeholders, checking for completeness, validating assumptions, or ensuring clarity of recommendations.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

Post-analysis learning and process improvement. Use when completing major analysis projects, documenting lessons learned, or improving team analytical practices.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

See all skills by nimrodfisher

Report a problem with this skill