The weekly UA ledger: platform moves worth watching
By UA Ledger staff — Archive date: 3 min read
Revised
Platform moves worth watching this fortnight, from Apple's EU fee chronology to Epic v Google, and what each changes for a UA operating plan.
A platform move matters when it changes an operating decision. This brief sorts the announcements from what they do to budgets, to build schedules, to measurement, to the weekly workflow, rather than relisting the fortnight.
Correction (2026-09-20): An earlier version of this article misstated Apple’s EU fee chronology. Under Apple’s June 26, 2025 update, Apple planned to move from the Core Technology Fee (CTF) to a Core Technology Commission (CTC) in a single EU business model. On August 18, 2026, Apple announced that the per-install CTF is replaced by a 5% CTC on digital transactions in apps distributed outside the App Store, with the new terms effective October 1, 2026, and that the Initial Acquisition Fee and Store Services Fee are eliminated. See Apple Developer News (June 26, 2025; August 18, 2026).
The platform moves worth watching this fortnight
Two changes clear that bar. Apple's EU fee path is one of them — but not as a finished “January 1 CTF-to-5%-CTC swap on standard terms.” Apple's June 26, 2025 update planned a single EU model transitioning from the per-install Core Technology Fee to a Core Technology Commission by January 1, 2026. Apple's August 18, 2026 announcement then stated that CTF is replaced by a 5% CTC on digital transactions in apps distributed outside the App Store, with updates effective October 1, 2026, and that the Initial Acquisition Fee and Store Services Fee are eliminated; the Coalition for App Fairness still says the terms fall short of DMA compliance. That chronology changes how EU unit economics should be modelled once the October terms apply. AppsFlyer published its State of Gaming for Marketers 2026 report with Unity and Newzoo on January 15. It found paid install share up 10% year on year, ad impressions up 20%, average creative output per advertiser rising 25 to 30%. Neither change is dramatic on its own. Both move the baseline a UA plan should assume for the rest of the year.
Keep an impact log
Record the date, the campaigns affected, the mechanism you expect, the outcome you can actually observe. Do it for the changes that look minor at the time. Epic's evidentiary hearing against Google over the proposed Play Store settlement, held on January 22 before Judge Donato, is the case in point: a previously undisclosed commercial arrangement between the two companies surfaced during the hearing, and the outcome could still reshape steering rules on Android. A team that logged the hearing date has a clean marker to check against whenever a ruling lands.
Sensor Tower's State of Mobile 2026 report, which surfaced mid-month, put gaming IAP revenue at roughly $82 billion for the prior year, alongside a strategic shift from chasing new-user volume toward extending lifetime value, and a rise in video and playable ad share.
None of that changes a campaign this week. It is the kind of context a log should hold rather than something to react to on the day. Later in the year, a team can ask whether its own account moved with the wider pattern or against it.
The UA Ledger view
The useful question is never what launched. It is what a team should test or stop because it launched, and that answer is rarely available on the day of the announcement itself.
Related archive reading
These articles provide related context and remain subject to their stated review status.
Corrections & updates
Update (): Audit remediation draft (ED-001/007/008/009). Awaiting named human publish sign-off.