Measurement partner case study · synthetic data

FIZLY Zero: measuring a store-led drink launch

A fictional Korean drink brand launches a zero-sugar line with a heavy short-form video campaign. Three quarters of its sales happen in stores, where no pixel looks. This lab plans the measurement with the advertiser and agency, runs a brand lift survey, a conversion lift, a geo test on store sell-out data and a vendor tracker, reconciles their answers, and ends with the readout and a product feedback memo. Every number is graded against the hidden truth of the simulated world.

All data syntheticNo real brand, platform or customerOne-page summary (PDF)

How much does FIZLY's launch video return, and why does every tool give a different number?

Estimate with intervalTruth for the same questionBreak-even in shelf sales at 30% contribution

What a measurement partner did in this case

  1. Agreed the questions first. A one-page plan with the advertiser and agency before launch: which study answers which decision, read dates, and rules nobody can change once results are in (chapter 0).
  2. Sized every study from the advertiser's own history. Brand lift holdout by answers needed, conversion lift holdout by detectable lift, geo regions by detectable return and launch sales at risk (chapters 1-3).
  3. Ran four instruments in one flight without collisions. Brand lift first; conversion lift and a store-level geo test together; an independent tracker alongside, with a brief to its vendor.
  4. Reconciled the numbers instead of picking one. Each answer tied to the decision it should drive, and the gaps between them explained (chapter 4).
  5. Handed over and fed back. A readout in English and Korean, a playbook for the next launch, a program view for other advertisers, and a memo to the measurement product team (chapters 5-6).

Role-play on synthetic data, written the way the work would be done.

How to read this page
  • Chapters follow a measurement partner's work: agree a plan (0), run the studies (1-3), reconcile them (4), report and hand over (5), feed the product team (6).
  • Each tab shows the design, the readout and the truth. "Truth" exists only because the world is simulated: each person's and region's outcome with and without ads is known.
  • Methods are written in platform-neutral terms. The README maps them to named lift tools.