Tee Studio: make the revenue denominator explicit before scaling a channel
Tee Studio's hybrid-monetisation case is a reminder that a percentage can look actionable while leaving the operator unsure what has actually been counted.
Tee Studio's hybrid-monetisation case is a reminder that a percentage can look actionable while leaving the operator unsure what has actually been counted.
What the public case establishes
AppsFlyer describes Tee Studio seeking better cross-channel attribution and combined visibility into advertising revenue and purchases. Its case reports changes in acquisition and revenue metrics after adopting its measurement suite. One result describes purchases moving from 5% to 10% without sufficiently defining that percentage's denominator for a reusable benchmark. AppsFlyer case study.
This debrief analyses a public customer case published by a commercial supplier. It is not an original UA Ledger interview. The chronology below follows the supplier’s account; we did not inspect the advertiser’s dashboards or interview its staff.
The decision worth examining
An operator cannot safely transfer a percentage until its unit is clear. It could refer to a share of revenue, a share of players or another rate, each with different implications. The useful response is to request a definition and preserve the uncertainty. Turning an ambiguous result into a confident purchase-conversion benchmark would add precision the source does not supply.
The proposed metric contract records numerator, denominator, qualifying period, revenue streams and aggregation method. It keeps a channel's install cost separate from its total acquired-player value. A blended portfolio improvement should also remain distinguishable from improvement within each channel, because changing the media mix alone can alter the aggregate.
A usable next check
Choose a current growth report and ask the owner to reconstruct every percentage from explicit raw totals. Flag ratios that cannot be reproduced, and show both channel-level and blended results where the data permits. For any future scaling experiment, freeze those definitions first. This exercises reporting clarity rather than proving that a vendor integration caused a business outcome.
| Test element | Proposed specification |
|---|---|
| Control | Headline ratios without reproducible numerator and denominator |
| Variant | Same report with metric contracts and channel-level decomposition |
| Readout | Reproducible ratios and explained blend changes |
| Stop or reject | Do not use an undefined percentage as a target or forecast input |
Download the populated case worksheet. Its control, variant and decision rules are a proposed experiment, not an account of results already measured. Keep the source URL with the worksheet when circulating it so reported findings cannot become unattributed team benchmarks.
Evidence boundary
The draft does not generalise the case's SDK-update language into a claim that mobile SDK releases never require app updates. No current vendor capability or private advertiser result was independently verified.
For background, see reading an mmp dashboard without fooling yourself and cohort quality checklist ua spend. No first-hand campaign result is asserted.
