Case Study · Conversion Rate Optimization

Recovering a $15M conversion drop after Vodafone's iPhone launch.

A post-launch traffic surge exposed a redirect-loop bug that quietly throttled checkout — a funnel-level diagnosis traced it to a time-out error and restored conversion within weeks.

Role Led the conversion diagnosis — step-level funnel analysis, error-correlation, and recovery validation

2017-2018 $15M incremental revenue · 2 quarters 11.0% → 9.0% basket-to-order CVR drop 9.0% → 10.7% CVR recovered post-fix 5-step funnel diagnosed

Checkout conversion fell off a cliff after the iPhone launch

Basket-to-order conversion dropped from 11.0% to 9.0% following the iPhone launch and stayed depressed even after traffic volumes stabilized.

CONVERSION

Basket-to-order CVR dropped 2 points

Conversion fell from 11.0% in June to 9.0% by September, coinciding with the iPhone launch surge.

2-point CVR drop = revenue leaking at checkout
PERSISTENCE

The drop didn't recover with traffic

Conversion stayed low into October even after traffic volumes returned to normal, ruling out a simple demand spike.

Traffic recovered, conversion didn't = a product issue, not demand
SATISFACTION

Transactional NPS declined

The checkout breakdown was also dragging down post-purchase satisfaction scores.

Broken checkout = customers noticing and saying so

The cause was buried inside a 5-step funnel

Three questions stood between the symptom and the fix: which step was failing, why it lined up with the iPhone launch, and what in the code was actually broken.

DIAGNOSIS

No step-level visibility into the funnel

Basket → checkout → address → payment → review → thank-you conversion wasn't broken down by step, hiding where users dropped off.

No step-level data = drop-off location unknown
CORRELATION

Unclear link to the iPhone launch

The timing pointed to the launch, but nothing connected device traffic to a specific failure mode in checkout.

Timing pointed to the launch = but no causal link yet
ROOT CAUSE

A code-level bug was hidden in production

A redirect loop triggered by time-out errors was silently sending certain users into a dead end, with no alerting in place.

Silent redirect loop = orders failing with no alert

From funnel analysis to a code-level fix

A step-by-step funnel analysis surfaced a time-out/redirect-loop correlation, which IT traced to a specific code defect and shipped a fix.

1
Step-level funnel analysis basket → thank-you

Broke down conversion across all 5 checkout steps to isolate exactly where users were dropping off.eCommerce funnel · step analysis

2
Error correlation analysis

Found a high correlation between time-out errors and order failures that began right after the iPhone launch.Error logs · correlation

3
Root cause identified by IT

IT investigated the time-out pattern and discovered a code defect sending affected users into a redirect loop.Code review · root cause

4
Fix shipped and validated

Deployed the fix and confirmed conversion rates stabilized immediately, recovering through November and December.Fix deployment · validation

Checkout conversion recovered, revenue followed

$15M
Incremental revenue
Over 2 quarters
9.0%
Trough conversion
September low point
10.7%
Recovered conversion
December, post-fix
5
Funnel steps analyzed
Basket to thank-you

From a stubborn revenue leak to a repeatable diagnostic

⚡

$15M revenue recovered in two quarters

Pinpointing a single redirect-loop defect through funnel and error-correlation analysis turned a stubborn post-launch conversion drop into a fast, targeted engineering fix — restoring conversion above pre-launch levels.

⊕

Step-level funnel monitoring

The eCommerce journey now has visibility into conversion at every checkout step, not just the overall rate.

↻

Error-to-conversion correlation method

The approach of correlating technical error logs with funnel drop-off becomes a repeatable diagnostic for future launches.

Let's talk

Tackling something like this?

Tell me your biggest data or AI bottleneck and I'll send you how I'd approach it — the same way I worked this problem. No résumé dump, no pitch. Just a useful conversation.

Start the conversation →