Isolate regional or platform drivers behind KPI drops

Break down aggregate product or revenue declines across platform and geographic dimensions. Use this when global numbers drop and leadership needs the root driver.

You getPrimary Contributor Summary, dimension Breakdown and ruled Out Segments

Prompt

Prompt
Act as a senior operations data analyst. Analyze the KPI decline data pasted below to pinpoint the operational, regional, or platform-level source of the drop.

- Calculate or isolate which sub-segment accounts for the largest proportion of the total missing volume.
- Separate global baseline trends from isolated local shocks (such as localized outages, broken builds, or regional holidays).
- Provide clear attribution without conflating correlation with causation.

Output format:
- Primary Contributor Summary (what drove the drop and by what percentage)
- Dimension Breakdown (table with: Dimension, Performance Change, Share of Total Loss)
- Ruled Out Segments (segments that performed normally)
- Recommended Next Investigative Steps

The performance data and context are below:

Example output

Example for: global daily active users dropping 18% week-over-week across iOS, Android, and Web

Primary Contributor Summary
The 18% global DAU decline is almost entirely concentrated in Android version 4.12.0 within Brazil and Mexico, accounting for roughly 82% of the total missing active users. iOS remained stable and Web dipped only slightly.

Dimension Breakdown

DimensionPerformance ChangeShare of Total Loss
Android (v4.12.0)-44% active sessions WoW82% of net loss
Android (Legacy versions)-2% active sessions WoW3% of net loss
iOS (All versions)+1% active sessions WoW0% (Stable)
Web Platform-3% active sessions WoW5% of net loss
Region: Brazil & Mexico-36% total active users61% of net loss
Region: North America-1.5% total active users4% of net loss

Ruled Out Segments

  • iOS users globally showed normal engagement patterns, ruling out widespread server API outages or global marketing campaign pauses.
  • North American traffic remained flat across all clients, ruling out global authentication service degradations.

Recommended Next Investigative Steps

  • Inspect crash reporting logs specifically for Android build 4.12.0 devices operating on Android OS 11 and 12 in Spanish and Portuguese locales.
  • Verify third-party CDN latency and DNS resolution times for media assets serving the Sao Paulo and Frankfurt data centers.
Written by AI from this prompt. Your results will vary.

Paste your multidimensional summary table (such as daily active users cut by OS, country, or app version) into ChatGPT, Claude, or Gemini. Ask a follow-up prompt requesting a draft incident ticket for the engineering team responsible for that platform.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Data Analysis