Conversion rate can improve for the wrong reason
Conversion rate is conversions ÷ clicks or sessions, depending on the report. It can rise because the page improved, because traffic narrowed, because a micro-conversion became primary, or because measurement duplicated events. Track qualified rate, revenue or contribution alongside it.
Calculate the opportunity
A hypothetical campaign receives 2,000 clicks at £3, converts 3% and produces 60 leads. If 25% qualify, qualified CPA is £400 (£6,000 ÷ 15). Raising form conversion to 4% is harmful if qualification falls to 15%: 80 leads produce 12 qualified leads and qualified CPA worsens to £500.
Segment before optimising
Break conversion rate by query intent, campaign, device, location, page, new/returning customer and conversion action. Compare counts and confidence intervals, not only percentages. A segment with two conversions from ten clicks is not proven superior to one with 180 from 1,000.
Prioritise with evidence and reach
| Finding | Response |
|---|---|
| Wrong or low-quality primary action | Repair measurement and import qualified outcomes |
| Irrelevant high-spend query theme | Refine targeting or negatives with scope control |
| Mobile technical failure | Fix and regression-test directly |
| Unclear offer with no defect | Research objections, then test a specific proposition |
| Checkout drop after shipping step | Inspect delivery surprise, errors and payment options |
Write a testable hypothesis
Use: “For [segment], [evidence] suggests [mechanism]. Changing [one material element] should move [primary outcome] while [guardrail] remains acceptable.” Define the minimum effect that would justify implementation and estimate sample requirements before launch.
Google Ads experiments can test landing pages and campaign settings for Search. Google recommends holding the base steady and allowing enough data. If a result is inconclusive, report it as inconclusive; do not select the prettier variant.
A practical sequence
- Validate outcomes and values.
- Remove clearly unsuitable traffic.
- Fix functional and mobile defects.
- Resolve the largest evidenced objection in offer or page.
- Test one mechanism with quality or profit guardrails.
- Document result, segment effects and rollback decision.
Google’s Quality Score documentation includes landing-page experience but explicitly describes the score as diagnostic. A conversion test should optimise the business outcome; Quality Score can flag relevance issues but is not the test’s success metric.
Check the denominator
Google Ads conversion rate often uses ad interactions, while analytics may use sessions or users. Cross-device journeys, repeat visits, consent and attribution create differences. Name the numerator and denominator on every chart. Compare the same conversion actions and date basis before treating a discrepancy as a trend.
Traffic-quality workstream
For Search, classify actual queries by commercial intent and map them to ads and pages. For Shopping, segment product IDs by price, margin and stock. For YouTube or Display, inspect audience, placement, frequency and attribution role. Exclude clearly incompatible traffic, but do not remove a plausible segment merely because a small sample has no conversion.
Use the zero-conversion diagnostic when the account has no outcomes at all; CRO cannot rescue an invalid traffic or measurement setup.
Offer workstream
Interview customers, lost prospects, sales and support. Extract repeated questions about fit, price, delivery, risk and implementation. Compare competitors without copying their page structure. Rank objections by frequency, commercial importance and whether the page can resolve them.
A hypothesis should connect evidence to a mechanism. “Adding a guarantee will improve trust” is vague. “Qualified prospects cite implementation risk; explaining the 14-day onboarding and named support owner before the form should increase booked demos without reducing show rate” can be tested.
Sample size and stopping
Choose the baseline rate, minimum effect worth implementing, confidence approach and expected weekly volume before launching. A test designed to detect a 20% relative change needs far fewer observations than one looking for 3%. Low-volume businesses may need to test a larger change, pool comparable pages or use qualitative evidence rather than waiting indefinitely.
Do not stop when the dashboard first shows a winner. Cover representative days, allow delayed conversions, check allocation and review guardrails. Report “inconclusive” when the data cannot distinguish a useful effect.
Worked example with guardrails
A hypothetical lead page converts 6% of 5,000 monthly clicks, producing 300 forms. Thirty percent qualify, so there are 90 qualified leads. Variant B converts 7%, producing 350 forms, but qualification falls to 22%, or 77 qualified leads. Raw conversion rate improved 16.7% relative; the business outcome worsened. The correct result is a loss unless lower-quality leads have separate value.
CRO operating rhythm
- Weekly: review tracking, errors and major segment shifts.
- Fortnightly: rank evidence-backed hypotheses and implementation capacity.
- Per test: QA allocation, events and page behaviour before counting data.
- After test: record result, segment effects, limitations and decision.
- Quarterly: revisit offers, customer objections and measurement guardrails.
Decompose conversion rate changes
Account conversion rate is a weighted average of segments. It can fall because each segment converts worse or because more traffic moved into a lower-rate acquisition segment. Calculate the rate within brand/non-brand, campaign type, device and page, then calculate the mix shift. Do not “fix” a healthy expansion into colder demand by chasing the old blended rate.
For ecommerce, decompose contribution per click into purchase rate and contribution per purchase. For leads, decompose click-to-qualified into form rate and qualification rate. This tells you whether the next lever sits in traffic, page or downstream process.
Choose research methods by question
| Question | Useful evidence |
|---|---|
| Is the page broken? | QA, logs, monitoring and support tickets |
| Do visitors understand the offer? | Moderated usability and interviews |
| Where do they stop? | Validated funnel and field events |
| Why are leads poor? | CRM dispositions and call review |
| Did the change cause improvement? | Randomised or credible controlled test |
Session recordings show behaviour but rarely motivation. Surveys capture stated reasons but suffer response bias. Combine methods rather than treating one tool as truth.
Test QA checklist
- Verify control and variant differ only as intended.
- Confirm allocation and exclusions.
- Test primary and guardrail events with unique IDs.
- Check device, browser, consent and page performance.
- Exclude staff and QA traffic where appropriate.
- Record launch time, promotions and external changes.
- Wait for conversion and refund lag before decision.