PRODUCT / USER ACQUISITION ANALYTICS
Turn an acquisition incident into a smaller search space.
When several metrics move and every team has a plausible explanation, compress the incident into one topology, a bounded scope and the next checks that can remove wrong stories.
PRIMARY BREAK
BROAD / LOCAL SCOPE
MIX / WITHIN CONTRIBUTION
NEXT FALSIFYING CHECK
OWNER / CHECKPOINT / REVERSAL
THE JOB
Do not investigate every plausible cause at once.
Validate the comparison
Separate mature signal from reporting delay, tracking disagreement and incompatible windows.
Localize the movement
Find the first material break and distinguish broad movement from local amplifiers.
Decompose contribution
Separate composition change from deterioration inside comparable segments.
Route one ordered check
Retain, weaken or park hypotheses and assign the next discriminating test to its owner.
SYNTHETIC METHOD CASE
Six metrics moved.
It was not six incidents.
Northstar Labs and its mobile product Focusly are invented. The dates, segments, metrics and values below demonstrate the method; they do not describe a client or investigation outcome.
COMPRESSION ROUTE
The same conversion break appeared across major acquisition channels. iOS Safari added a local payment-completion decline. Android in-app browser showed a separate upper-funnel episode. One creative package raised CPA while its conversion path remained stable—an acquisition follow-up, not the broad explanation.
The acquisition mix explained part of the end-to-end decline. Most of the movement remained inside comparable routes, so “the mix changed” became a partial contribution rather than a universal cause.
THE RESULT
Stop changing UA.
The first material loss starts at Paywall → Checkout.
The break is visible across major acquisition channels. This is a product-funnel incident, not six unrelated metric alerts.
Traffic mix explains roughly one quarter of the end-to-end decline. It made the result worse, but it is not the main loss.
iOS Safari adds a downstream payment-completion problem. It does not explain the broad Paywall → Checkout break.
Android in-app browser loses users before the paywall. It gets its own frontend task instead of contaminating the primary incident.
Treat the paywall release or checkout instrumentation as the lead suspect. Freeze broad bid, audience and creative changes; reconcile client checkout events, server sessions and release history first. If the break aligns with the treatment, disable or roll it back.
ORDERED CHECKS
Reconcile checkout-open events, server sessions and the paywall release.
Split payment attempts by provider, iOS Safari and error family.
Inspect feature flags and treatment allocation; pause, fix or continue.
Rerun mix/within decomposition after the next closed day.
Inspect Android in-app browser as a separate upper-funnel episode.
DO NOT RESET ACQUISITION. ISOLATE THE PAYWALL RELEASE FIRST.
The cause is not being guessed from six charts. One reversible check can now confirm or kill the leading explanation.THE PROMISE
Find the first break. Kill the wrong investigations.
Acquisition Incident Compressor tells you where the loss begins, how much is mix, which segment amplifies it and which reversible check can confirm or kill the leading mechanism.
If the incident points outside UA, it says so. The team gets a move for today—not another list of possible causes.
See the CPI contribution method ↗Bring one incident