Case Study · Product Analytics Enablement

Giving Vodafone a trustworthy view of ~19.5M app users.

Vodafone's legacy analytics implementation was inflating app penetration metrics by 30-40%, with no performance baseline and no way to personalize. In a 2-month sprint, I rebuilt the tracking foundation on Adobe Analytics, embedded on-site with the app team in Egypt.

Role Led the Adobe Analytics rebuild — gap analysis, data schema contracts, and on-site delivery with the app team

2017-2018 30-40% metric error fixed 36% digital adoption · ~19.5M 2 months to go-live 5-person agile team

The app's analytics couldn't be trusted

A legacy tracking implementation was inflating Vodafone's app penetration metrics by 30-40%, undermining every downstream product decision.

ACCURACY

App penetration was overstated 30-40%

The legacy implementation systematically inflated user counts, distorting the picture of true app adoption.

Faulty metrics = product decisions based on wrong numbers
VISIBILITY

No performance metrics

Without reliable performance metrics, the product team had no baseline to measure improvements against.

No performance metrics = no way to measure improvement
PERSONALIZATION

No A/B testing or personalization

The app had no product analytics layer capable of supporting A/B testing or personalized experiences.

No personalization layer = every user sees the same app

What had to happen before any test could run

Before any test could run, the new tracking had to be specified, built into the app, and shipped — all inside a two-month window.

SCHEMA

No agreed data contracts

Without a shared data schema, Adobe Analytics couldn't be wired into the app's event structure.

No agreed schema = Adobe Analytics had nothing to wire into
DELIVERY

Remote team, on-site delivery needed

Coordinating agile delivery with a 4-developer app team required on-site presence in Egypt to keep pace.

Remote-only delivery = too slow for a 2-month deadline
TIMELINE

Two-month go-live window

The gap analysis, schema design, and implementation all had to land inside a 2-month deadline.

Audit to go-live = one fixed runway, no slack

Gap analysis, data contracts, embedded delivery

A single data consultant embedded with a 4-developer app team in Egypt, running an iterative cycle from gap analysis to A/B-ready tracking.

1
Gap analysis legacy tracking → accuracy gaps

Performed a gap analysis to quantify how the legacy implementation was inflating app penetration metrics.Adobe Analytics · audit

2
Data schema contracts

Set up data schema contracts defining the events and properties the app team would implement.Data schema · contracts

3
Embedded agile delivery

Traveled to Egypt to coordinate agile delivery directly with the 4-developer app team, closing feedback loops in person.On-site · agile

4
Go-live and A/B enablement

Went live within 2 months and enabled A/B testing on top of the new accurate tracking foundation.A/B testing · go-live

Accurate measurement, behavioral targeting unlocked

30-40%
Metric inflation fixed
Adobe Analytics accuracy
36%
Digital adoption
~19.5M total users
2
Months to go-live
Full rebuild
5
Person delivery team
1 consultant + 4 devs

From inflated numbers to a measurement foundation for 19.5M users

⚡

A measurement foundation for ~19.5M users

Standardized data and analytics tracking now gives Vodafone a trustworthy view of digital adoption across its ~19.5M user base, with A/B testing and behavioral targeting built on top.

⊕

Behavioral targeting enabled

Accurate event data opens the door to segment-based, behavior-driven app experiences.

↻

Standardized tracking contracts

The data schema established with the app team becomes the standard for future instrumentation work.

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 →