Payment Attribution Analysis
Payment rate shifted? Decompose the numerator and denominator and drill down dimension by dimension to pinpoint exactly which user segment, product stage, or version change drove the payment change.
Segment breakdown
by groupPayment Attribution Analysis is a monetization-analysis capability in ThinkingAI's industry Skill library. When payment rate or revenue shifts significantly, it helps analysts decompose the attribution layer by layer, from the overall trend to dimension drilldowns, identify which payment segment, product stage, or version change drove the shift, and output targeted optimization recommendations. This is ThinkingAI's decade of industry experience, packaged into ready-to-use Skills.
Live walkthrough
Found the answer. Both camps in the group are right, but each only half-right: 60% is denominator dilution from ramped-up UA, and 40% is v5.1 changing progression-item output. Here's the breakdown.
1. First nail down which end is moving
| Item | Last month | This month | Change |
|---|---|---|---|
| Payment rate | 5.20% | 4.80% | −0.40pp |
| Active users (denominator) | 826,431 | 867,752 | +5.0% |
| Paying users (numerator) | 42,974 | 41,642 | −3.1% |
Payment rate is a composite metric, and both ends are moving: the denominator is +5.0% (UA ramped up this month) and the numerator is −3.1%. Split by contribution, about 60% of the drop comes from denominator dilution and 40% from a real decline in paying users. Reading only "the payment rate fell" would blend two things into one.
2. Whom the numerator's 40% falls on
| Payment segment | Share of paying users | Change in payers |
|---|---|---|
| High spenders (VIP8+) | 15% | −0.4%, flat |
| Mid spenders (VIP4–7) | 35% | −11.8% |
| Low spenders (VIP1–3) | 50% | +2.1% |
The numerator's decline comes almost entirely from the mid-spender segment. One level deeper: the mid-spender drop concentrates in the mid-game band of levels 20–40 (−19.0%, 60% of the mid-spender segment), while above level 40 is essentially flat (−1.2%). This is a classic "specific progression band" problem, not a global drop in willingness to pay.
3. Version attribution and the full chain
The chain, linked up: v5.1 (launched on the 3rd this month) raised the free output of the core progression item "Refinement Stones" by 40% → the progression gap for mid-game players at levels 20–40 was filled by free output → buyers of the "Refinement Stone bundle" fell −38% → mid-spender payers fell −11.8% → combined with the +5.0% denominator from ramped-up UA → the 5.2% payment rate was squeezed from both sides down to 4.8%.
On your data
That was a simulated run
Leave your work email and we will run a live walkthrough on your real business data.
The problem
Payment data changed but the cause is elusive: this is the most common bind data teams face. When payment rate drops, the team's first instinct is often to guess the payment feature broke, but a check shows the system is fine; then they guess user quality declined, but the data does not support it; and they end with a vague "maybe it's market-wide fluctuation." The issue is that payment rate is a composite metric. The numerator is paying users and the denominator is active users, so a change on either side moves the ratio, and the change may come from three entirely different combinations: fewer high-spend users, more mid-spend users, or unchanged low-spend users.
What it does
When to use it
Emergency attribution when payment rate drops suddenly
Breaking down the cause of a monthly payment-revenue change
Version attribution for payment changes after a new release
Segment attribution when ARPU or ARPPU fluctuates abnormally
Separating incremental from natural growth in payment-rate change during an event
In the field
FAQ
What is the difference between payment attribution and payment funnel analysis?
Payment attribution focuses on why the payment rate changed, a change diagnosis. Payment funnel focuses on where users get stuck in the payment flow, a process optimization.
How much data is needed for attribution?
At least 2 weeks of comparison data (before versus after the change). If the change stems from a version update, you need at least 7 days of data before and after.
How do you attribute changes in ARPU and ARPPU?
ARPU-change attribution looks at the combined effect of payment penetration and ARPPU. ARPPU-change attribution looks at how the payment-amount share shifts across payment segments.
Related Skills
Equip your Agent with Payment Attribution Analysis
Book a demo and see how it works in your own business.
