본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4812026년 9월 25일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4812026년 9월 25일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4812026년 9월 25일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4812026년 9월 25일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4812026년 9월 25일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4812026년 9월 25일 업데이트

nimrodfisher의 스킬 모두 보기

이 스킬의 문제 신고