Funnel Audit Template Checklist
A structured funnel audit template that records conversion rates, drop-off points, session-replay evidence and suspected friction at every stage — the artifact your test-design team actually needs.
Funnel Audit Template
A structured document that maps conversion, drop-off and friction stage by stage so the test-design team has evidence, not guesses.
A funnel audit template is the standardised artifact a CRO team fills in before designing experiments. For each stage of the purchase journey — landing, category, product, cart, checkout, thank-you — it records the conversion rate into and out of the stage, the absolute drop-off, links to session-replay clips that illustrate the leak, and a shortlist of suspected friction sources.
The template exists so hypotheses come from evidence rather than opinion. Once filled, it is handed to whoever designs the next round of A/B tests, ranked by impact and ease.
Most stores already have the data to run an audit — GA4 funnels, a heatmap tool, a checkout report inside Shopify or WooCommerce. What is usually missing is a single document that forces those sources to agree on where the money is actually leaking.
A good template does three things: it fixes the funnel definition so two analysts compute the same number, it pairs every quantitative drop-off with a qualitative replay clip, and it ends with a prioritised friction list the test-design team can take straight into hypothesis writing.
Audit the funnel you actually have, not the one in the slide deck
The most common mistake is auditing an idealised linear funnel — home → category → product → cart → checkout — when real traffic skips stages (paid social lands directly on product pages, returning customers go straight to cart). Pull the top three real entry paths from GA4 first, then audit each separately. A single blended funnel hides where mobile paid traffic is haemorrhaging.
What to capture at each stage
Stage 1 — Acquisition and landing. Record sessions, bounce rate, scroll depth and engaged-session rate split by device and top three traffic sources. Flag any landing page where mobile bounce exceeds desktop bounce by more than 15 points; that gap is almost always a load-speed or above-the-fold problem worth a replay clip.
Stage 2 — Category and product. Capture product-detail-page view rate, add-to-cart rate per PDP, and the share of sessions that use site search. Note any PDP where add-to-cart rate is below half the store average, and link two replay clips: one user who converted, one who bounced. The contrast usually reveals the friction faster than the metric alone.
Stage 3 — Cart and checkout. This is where most stores recover the largest share of revenue. Record cart-to-checkout rate, checkout-start-to-purchase rate, and field-level abandonment if your platform exposes it. Tag every input that triggers an error or a long pause on replay — phone formatting, postcode validation and discount-code fields are repeat offenders on Shopify and Woo.
Stage 4 — Post-purchase and returning visitors. Audit thank-you-page completion of cross-sell or newsletter prompts, repeat-purchase rate at 30 and 90 days, and refund or return rate by SKU. A high return rate on a hero SKU is a funnel leak even if checkout looks healthy — it eats the LTV the rest of the audit is optimising for.
Funnel audit template FAQ
A first pass on a single funnel takes a CRO specialist roughly one to two days: half a day pulling metrics from GA4 and the store backend, half a day watching session replays, and the rest writing up suspected friction. Subsequent audits on the same store are faster because the funnel definition is already locked.
At minimum: an analytics source with funnel reports (GA4 or equivalent), a session-replay tool, your platform's native checkout report, and a spreadsheet or doc to consolidate findings. If you import historical GA4 into Metricuno the first three collapse into one view, which is the main reason day-one audits are realistic.
Run a full audit quarterly, and a lightweight checkout-only audit monthly. Also trigger an ad-hoc audit whenever conversion rate moves more than two standard deviations from its 30-day baseline — that usually means a tracking break, a checkout regression, or a traffic-mix shift worth investigating before launching new tests.
Whoever designs the next round of experiments should own it, because the audit is the input to hypothesis writing. In-house CRO specialists usually own it directly; agency leads typically own it on behalf of the client and review findings with the brand before recommending tests.
A heuristic review evaluates pages against UX principles without necessarily looking at data. A funnel audit is data-led: it starts from where users actually drop off, then uses heuristics and replays to explain why. The two complement each other, but the audit is what justifies test prioritisation.
Score each friction by potential revenue impact (drop-off volume × average order value) and implementation ease (dev hours, risk to checkout). The top of the list is high-impact, low-effort items — usually copy, form-field or trust-signal changes on cart and checkout. Reserve dev-heavy fixes for items with proven impact.
You can, but the output is weaker. Quantitative data tells you where users leave; replay tells you why. Without replay you fall back on heuristics and guesses, which produces lower-quality hypotheses. If budget is tight, even a free-tier replay tool covering 1–2% of sessions is enough to make the audit meaningful.
A dashboard surfaces metrics continuously; an audit interprets them at a point in time and turns them into a prioritised action list. Dashboards are passive monitoring; the audit is the deliverable. Most teams keep both — the dashboard flags when an audit is overdue.
Yes. On most stores in the €1M–€15M range mobile traffic share exceeds 70% but mobile conversion rate is roughly half of desktop. Auditing them together hides the gap. Split the template by device from stage one and you will almost always find your highest-impact fixes are mobile-specific.
Metricuno imports historical GA4 so the audit has 12+ months of context on day one, ties replay clips directly to drop-off events, and auto-generates hypotheses from the friction list. It replaces the analytics-plus-replay-plus-test-tool stack the audit normally pulls from, so the template fills itself in faster.
Get an AI expert review of your site
Paste your URL — Metricuno's AI runs the same heuristic checks a senior CRO consultant would, scoring your page and prioritising the fixes that'll move conversion fastest.