Apple used WWDC 2026 to open subscription bundling beyond its own apps: independent developers can now group their subscriptions together and sell them as a single offer, splitting the revenue. For any team used to a single-app subscription model, this changes what “revenue per subscriber” even means. A subscriber who joins through a bundle isn’t buying your app specifically — they’re buying a package, and your app is one of several reasons they might stick around or cancel. Without new tracking in place, that ambiguity shows up first in your churn numbers, which will look worse (or better) than reality depending on how bundle partners are performing, not your own product.
The teams caught out here will be the ones who plug bundle revenue into the same dashboards as direct subscriptions and assume the numbers mean the same thing. A bundle subscriber’s engagement with your app specifically, their likelihood of renewing based on your app’s value versus a partner’s, and the actual revenue share landing in your account after Apple’s split and any bundle-partner split are all distinct signals that get flattened if you don’t track them apart from day one.
Data Points to Track
- Acquisition channel: direct vs. bundle, tagged at the subscription-event level so every downstream report can be split or combined
- Bundle partner identifier, logged for every bundle-sourced subscriber so revenue and retention can be attributed to the specific bundle, not just “bundled vs. not”
- Revenue share received per subscriber, tracked separately from list price, since Apple’s cut plus any bundle-partner split means bundle subscribers generate different net revenue than direct ones
- In-app engagement depth for bundle subscribers, compared against direct subscribers, to see whether bundle-acquired users actually use your app or just tolerate it as part of the package
- Bundle-subscriber churn and downgrade events, tracked separately, since a bundle subscriber leaving may reflect the bundle’s overall value rather than your app specifically
Setup Steps
- Capture the acquisition source at first subscription event using App Store Connect’s transaction and bundle metadata, storing it as a permanent property on the subscriber record rather than a one-time event tag.
- Build a revenue reconciliation pipeline that maps StoreKit transaction data to actual net revenue per subscriber, accounting for Apple’s standard cut and any additional bundle-partner split.
- Segment every core engagement dashboard by acquisition source (direct vs. bundle, and by bundle partner where volume supports it) before drawing conclusions from aggregate retention or engagement numbers.
- Instrument in-app value moments separately for bundle subscribers, so you can tell whether they’re converting to genuine users of your app or riding along on the bundle.
- Set a review cadence with any bundle partners to compare notes on shared subscriber behaviour, since bundle economics only make sense with visibility both directions.
Actionable Insights
If bundle-sourced subscribers show materially lower in-app engagement than direct subscribers, that’s a signal the bundle is functioning as a discount channel rather than a genuine acquisition source — worth knowing before you renew the bundle agreement. If net revenue per bundle subscriber, after all splits, falls below your cost of serving them, the bundle is a net negative even if the top-line subscriber count looks healthy. And if churn among bundle subscribers tracks closely with a bundle partner’s own product changes rather than yours, that’s evidence the bundle relationship — not your app — is driving the outcome, which should factor into any renewal or renegotiation conversation.
Related Resources
Need help tracking this in your app?
Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.
Talk to an expert