FunnelFox: in the EU, Apple fees are now a configuration problem (not a single commission rate)
A credited summary of FunnelFox’s April 2026 breakdown of Apple’s post-DMA EU fee stack: why ‘external payments’ don’t equal ‘no Apple tax’, and what changes for forecasting, attribution, and experimentation when monetization becomes region-fragmented.
Original article (source): FunnelFox - “App Store Fees and Commission Rates in 2026: Apple EU Changes” (Apr 10, 2026)
The headline
In the EU, “Apple’s cut” is no longer one number, it’s a stack of choices. FunnelFox’s core point is that the DMA forced new distribution and payment paths, but Apple’s response turned fees into a menu where your effective rate depends on what you do (and which users you monetize).
What the article claims changed (high-level)
FunnelFox frames the shift as a move from:
- a predictable 15% or 30% commission model
to:
- multiple fee components that can combine, depending on service tier and payment path.
The article also stresses a second-order effect that matters more than the headline fees: operational and reporting overhead becomes permanent, not a one-time migration.
Why app teams should care (beyond “fees”)
1) Forecasting and LTV get region-fragmented
If payment routes differ by region, your revenue model starts to splinter:
- margins vary by country
- net revenue is harder to compare across cohorts
- experiments (pricing, paywall, offers) become harder to read without region context.
2) “Link-out” UX becomes part of the growth equation
Even if the nominal fee stack is lower, the user experience cost is real:
- extra steps
- lower trust
- higher support load
That means the correct comparison is not “20% vs 30%”, it’s net revenue after conversion and support impact.
3) Measurement gets messier
When there are multiple payment rails, you also create multiple measurement realities. The article’s takeaway is directionally right even if you disagree with its specifics: your analytics definitions must keep up with your monetization setup, or you’ll argue forever about performance.
Tiny win
Make the complexity explicit, then stop arguing from memory:
- Write a one-page table for your app: where users can pay (and how) by region (EU vs US vs RoW).
- For each path, note the expected fee components + the extra UX steps.
- For one cohort, estimate: net revenue per install for IAP vs link-out, using your own conversion data (or a conservative delta).
Read the original: https://blog.funnelfox.com/apple-app-store-fees-2026-eu-dma/
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.