Marketing & GrowthFree
Landing Page Funnel Drop-off Review
Every funnel step resolved to the URLs that fired it, then those pages read for the field counts and fold positions that explain the drop.
A funnel export tells you that 55.5% of paid sessions never start a quote. It does not tell you that of the fourteen pages carrying that traffic, one starts 52.4% of its sessions and another starts 8.1%, on the same ad group and the same offer copy. The pooled 44.5% describes neither page, and it is the one number the report puts on the chart. Nobody can fix a percentage, and the step it belongs to averages over pages that behave nothing alike.
This review splits every step by the URL that fired it, then opens each of those URLs. Six columns come back per page. Total inputs and required inputs. How far down the first input sits at 390 by 844, and whether the form is on the page or behind a click. Fields that ask for something a shopper does not carry, and the third-party bytes that load before an input takes a keystroke.
Rows sort by sessions lost, not by drop percentage, because those two orders disagree. On the account below the worst percentage sits fourth by traffic. The finding you can act on names a form that asks for nine inputs, five of them required, with one a policy number nobody carries. Where the page is slow rather than badly built, that belongs in a Core Web Vitals triage instead, and the copy question belongs in a page-copy rewrite.
Why a step-level drop-off cannot be fixed
On Thackeray Insurance's account, fourteen pages carried 138,400 paid sessions over ninety days. Two of them ran under the same ad group with the same offer copy. /lp/van-quote-a puts a registration-number box in the hero, 0.4 screens down, and 52.4% of its sessions start a quote. /lp/van-quote-b hides its form behind a button, then asks for nine inputs with five required, one of them an existing policy number. It starts 8.1%. Same traffic, 6.5 times the rate.
That page's 21,940 sessions are worth counting. Lifted to its sibling's rate it would start 11,496 quotes instead of 1,777. At the account's own 3.94% start-to-bound rate that is 383 more policies, or $78,942 of first-year margin on no extra media spend. Treat it as a ceiling rather than a forecast: it assumes the page can match a sibling that already works. The step-level chart never surfaced the row, because 8.1% and 52.4% average to 44.5%, a number that is accurate and useless.
Two GA4 settings will move your numbers before any page changes. Funnels can be open or closed, and in an open funnel users enter at any step, so 4,318 resumed quotes counted at step three here without ever counting at step one. Closing it moved that step's drop from 29.00% to 36.02%. Separately, thresholding withholds rows on demographic and audience breakdowns, so those segment totals will not add back to the unsegmented figure.
How it works
Send the export
The GA4 funnel rows, the landing-page URLs behind them, and whether the funnel ran open.
Split every step
Each step is broken out by URL and by device before anything is called a problem.
Read the pages
Every URL that carries traffic gets opened, measured at a phone viewport, and its six facts recorded.
Rank by traffic
Findings sort by sessions lost, each one naming the page fact behind the number.
What you get
- Every funnel step split by the URL that fired it, before any percentage is quoted.
- Six countable facts read off each page: inputs, required inputs, fold position, form placement, weight.
- Rows ranked by sessions lost rather than drop percentage, because the two orders disagree.
- Each step re-cut by device, so a mobile-only failure stops hiding inside a pooled average.
- The ad headline checked against the page, so a broken promise gets counted in sessions.
- A Sheet of drop-off by step and source, plus a Doc of page-level findings.
Common questions
Why not just fix the step with the worst drop-off?
Because on this account the worst percentage is fourth by volume. Quote-to-bind loses 84.0% and 12,738 sessions. Landing-page-to-quote-start loses 55.5% and 76,872. The first is mostly a pricing question, the second is a form. Sorting by percentage puts the pricing question on top of a list a marketer cannot action. Revenue-side gaps belong in the CRM match review.
What does reading the page actually add?
A number you can hand to a developer. Step two loses 55.5% is not a ticket. Nine inputs with five required, first one 2.1 screens down at 390 pixels, form behind a click, is a ticket. Both describe the same 21,940 sessions, and only one of them gets built.
Does this need GA4 specifically?
No. Any funnel export with a step name, a session count and the URLs behind each step works, including Adobe, Amplitude or a warehouse query. GA4 is the common case, so its two traps get called out by name. The page-reading half does not depend on the analytics tool at all. Query-level waste is a separate review, handled in the search term and negative keyword pass.
Is this the same as chasing landing page experience in Google Ads?
No, and Google is explicit that Quality Score is a diagnostic rather than an auction input. Its landing page experience component is a relative comparison against other advertisers, graded above or below average. That grade will not tell you a form asks for nine fields. This review works from your own session counts instead.
What if the problem is upstream of the page?
It often is, and the split by URL shows it. Two of the six pages under a 90-second-quote headline had no input above the fold, carrying 27,060 sessions between them. When the mismatch is in the ad rather than the page, the fix sits in the creative read by attribute. What rivals keep saying under the same headline is the competitor ad teardown.
How does the device split change the answer?
It moves which page gets the work. The vehicle-to-driver step drops 60.6% pooled, but 71.2% on mobile against 38.4% on desktop. Mobile holds 67.5% of that step, so the pooled figure sits closer to the mobile number and still understates it by over ten points. The driver-details form has eleven inputs and nine required.
What does the output look like?
A Sheet with one row per step and per source, carrying sessions, drop percentage and sessions lost side by side. Then a Doc listing page-level findings in traffic order, each naming its URL, the fact found on it, and the sessions behind it. Structural account questions stay in the Google Ads audit.
Landing Page Funnel Drop-off Review
Fill in the form and your workspace opens with the work already underway.