Funnel Audit Template Checklist
A repeatable funnel audit template that captures conversion rates, drop-off points, and session-replay evidence — the artifact your test-design team actually needs.
Funnel Audit Template
A structured worksheet that captures stage-by-stage conversion rates, drop-off points, and friction evidence for one funnel.
A funnel audit template is the single artifact a CRO team produces before designing any test. It maps every stage of a purchase funnel — landing, product, cart, checkout, payment, confirmation — and records the conversion rate between stages, the absolute drop-off in sessions, links to representative session-replay clips, and the suspected friction source for each leak.
Done well, the template becomes the handover document to the test-design team: every hypothesis they write should trace back to a row in the audit. It is deliberately not a slide deck — it is a working spreadsheet (or shared doc) that gets updated as new data arrives and as fixes ship.
Most teams skip the audit and jump straight to test ideas. The result is a backlog of hypotheses that all target the same one or two stages — usually the product page — while the real money is leaking somewhere else entirely.
A funnel audit template forces you to look at every stage with the same rigour. You quantify the leak, attach evidence, and only then write hypotheses. The work takes one to three days for a single funnel and pays back the moment your next test targets a stage that actually moves revenue.
The most common mistake
Auditing the funnel as if every visitor takes one path. A Shopify store has at least four meaningfully different funnels — paid social → PDP, organic → category → PDP, email → collection, and returning customer → cart. Audit them separately or your averages will hide the leak.
What the template captures, row by row
Section 1 — Funnel scope. One row that names the funnel (e.g. "Meta paid → PDP → checkout, mobile, last 30 days"), the date range, the device split, and the total entry sessions. This stops scope creep when someone three weeks later asks "wait, did this include returning visitors?"
Section 2 — Stage table. One row per funnel stage. Columns: stage name, entry sessions, exit sessions, stage conversion rate, drop-off in sessions, drop-off in revenue at current AOV. Sort the rows by revenue drop-off, not by conversion rate — a 60% drop on a stage that only sees 200 sessions matters less than a 12% drop on the first stage.
Section 3 — Replay evidence. For each leaky stage, link three to five representative session-replay clips with a one-line note: "rage-click on size selector", "price field empty after Apple Pay return", "shipping cost reveal triggers exit". Without clips, your friction notes are guesses; with clips, the test-design team has a brief.
Section 4 — Suspected friction. A short hypothesis-shaped sentence per stage: "checkout drop-off appears driven by unexpected shipping cost above €4.95 threshold". Section 5 — Segment cuts: mobile vs desktop, new vs returning, top-three traffic sources. Section 6 — Recommended next tests, prioritised by ICE (impact, confidence, ease) with a direct link back to the stage row.
Funnel audit template FAQ
One to three days for a single funnel on a Shopify or WooCommerce store with clean GA4 data. Add a day if you need to set up event tracking that isn't already firing, and add half a day per additional funnel variant (paid vs organic, mobile vs desktop).
Roughly 5,000 sessions through the funnel in the analysis window, or enough to put at least 200 sessions through every stage including the last one. Below that, stage conversion rates wobble too much to trust and you're auditing noise.
A heuristic review evaluates the interface against usability principles. A funnel audit starts from the numbers — where sessions actually leak — and only then looks at the interface. Heuristic reviews surface what could be wrong; funnel audits surface what is wrong.
Analytics alone gives you the where; replay gives you the why. You can run a useful audit on GA4 funnel exploration alone, but the friction-source column becomes guesswork. Pair the two — three to five clips per leaky stage is usually enough.
Yes if you're a repeat-purchase business (beauty, supplements, pet food). Add post-purchase stages for thank-you upsell, first reorder, and 60-day retention. For one-off purchase categories (furniture, electronics) the audit usually stops at order confirmation.
Quarterly as a full pass, plus a targeted re-audit any time a stage's conversion rate moves more than 15% week-over-week with no shipped change. Re-audit immediately after a checkout redesign or a payment-provider swap.
The structure works for both, but you should fill out one template per traffic source. Paid social and organic search bring visitors at very different intent levels, so their stage-conversion rates and friction patterns differ enough that averaging them hides the real story.
Three to seven test ideas, each tied to a specific stage row with the strongest revenue drop-off. Score each on impact, confidence, and ease. Avoid generic ideas like "redesign the PDP" — every recommendation should name a single element and a single stage.
The CRO or analytics lead owns it; the test-design team consumes it. Treat it as a living document — when a test ships and changes a stage's conversion rate, update the row. The audit should be the canonical source of truth for funnel state.
Yes — the template is platform-agnostic because it works off funnel stages, not platform features. The only thing that changes is event-tracking setup: GA4 event names and the exact checkout stages differ between Shopify's hosted checkout, WooCommerce's multi-step flow, and Magento's one-page checkout.
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.