| name | cro |
| description | Conversion Rate Optimization patterns beyond A/B testing. Heatmaps, session recordings, funnel analysis, form analytics, exit intent. Data-driven optimization. |
CRO (Conversion Rate Optimization) Skill
Purpose
Provides patterns for understanding user behavior and optimizing conversion funnels beyond basic A/B testing. Combines quantitative analytics with qualitative user insights to systematically improve conversion rates across the entire customer journey.
Core Rules
- Measure before optimizing — Understand current behavior first
- Qualitative + Quantitative — Numbers + user feedback
- Funnel thinking — Optimize the whole journey, not just CTAs
- Privacy first — Anonymize data, respect consent
- Continuous process — CRO is ongoing, not one-time
- Track user intent — Tag sessions by user type and behavior
- Mobile matters — Test on real devices, not just desktop
- Context over clicks — Understand why users behave, not just what they do
- Form friction kills — Monitor field-level analytics
- Iterate systematically — Weekly review cycles, documented insights
CRO Tool Stack
| Purpose | Tools | Priority |
|---|
| Heatmaps | Hotjar, Microsoft Clarity, PostHog | P0 |
| Session Recording | Hotjar, FullStory, LogRocket | P0 |
| Funnel Analysis | GA4, Mixpanel, Amplitude | P0 |
| Form Analytics | Hotjar, Formisimo, Zuko | P1 |
| Surveys | Hotjar, Typeform, SurveyMonkey | P1 |
| Exit Intent | OptinMonster, Sleeknote | P2 |
| Social Proof | Fomo, Proof, UseProof | P2 |
Key Metrics
Traffic & Engagement
- Sessions, unique visitors, bounce rate
- Scroll depth (25%, 50%, 75%, 100%)
- Time on page, pages per session
Conversion Funnel
- Landing page views → Form starts → Completions
- Conversion rate, drop-off points
- Time from entry to conversion
Form Performance
- Average completion time
- Field-level drop-offs and error rates
- Correction counts per field
Qualitative Insights
- Exit intent show/conversion rates
- Survey response themes
- Session recording patterns
References
Implementation Guides
Workflow
- Install tracking — Set up heatmap tool (Clarity recommended for free)
- Define funnels — Map critical conversion paths
- Collect baseline — 1-2 weeks of data before changes
- Identify friction — Watch recordings, review heatmaps
- Survey users — Ask about hesitations/objections
- Prioritize fixes — Impact vs effort matrix
- Implement changes — One variable at a time
- Measure impact — Compare before/after metrics
- Document learnings — Build insight repository
- Repeat weekly — Continuous optimization cycle
Forbidden
- Recording without consent notice
- Capturing sensitive form fields (passwords, CC)
- Aggressive exit popups
- Tracking PII in analytics
- Making changes without data
- Ignoring mobile users
- Testing multiple changes simultaneously
- Skipping baseline measurement
Definition of Done