BitMango: measure data completeness before shortening the optimisation cycle

BitMango's case links fresher revenue and cost data with earlier decisions. The operating question is whether an earlier number is sufficiently complete for the decision being accelerated.

What the public case establishes

AppsFlyer describes BitMango adding more granular cost and advertising-revenue data through ROI360. The account says this supported a shorter optimisation cycle, moving from two or three weeks to one week. Its reported performance changes accompany several improvements in the measurement workflow. 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

A faster feed reduces waiting but does not eliminate cohort immaturity or later corrections. A team needs to distinguish arrival lag from the genuine time required for players to produce value. Otherwise a newly available early revenue number can be treated as a mature answer simply because the dashboard now refreshes more often.

The proposed latency register gives each input an expected arrival time, completeness check and revision policy. Cost, ad revenue and purchases can have different delays. When their clocks differ, a temporary ROAS change may describe the pipeline rather than player quality. Marking a snapshot provisional makes that uncertainty usable instead of hiding it in a footnote.

A usable next check

Preserve daily snapshots of an authorised cohort and compare each early estimate with its later reconciled version. Record which input caused each revision. Evaluate whether the earlier decision would have changed after normal data arrival, and establish an action gate accordingly. This is a calibration exercise for a team's own data, not a claim that one week is universally enough.

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 public case does not release raw forecasts, revisions or a controlled counterfactual. We have not validated BitMango's data or any current product latency guarantee; reported changes remain supplier claims.

For background, see reading an mmp dashboard without fooling yourself and cohort quality checklist ua spend. These are existing archive discussions, not independent certification of this case. No first-hand campaign result is asserted.