UA Budget Planning for a Season of Platform Risk
UA budget planning needs a platform risk line this year. Here is how to build one after a fortnight of antitrust rulings and DMA fines.
Two rulings landed in the space of eight days. A US federal judge found Google liable for illegally monopolising publisher ad server and ad exchange markets. The European Commission fined Apple and Meta under the Digital Markets Act, with Apple's penalty running to roughly EUR 500 million over anti-steering restrictions. Neither ruling changes a single campaign setting today. Both are reasons to change how a UA budget gets built for the rest of the year.
Most UA budget planning treats platform terms as fixed inputs: today's commission rate, today's attribution window, today's minimum spend threshold. That assumption has been wrong before, and it is wrong again right now. This is not a call to panic or to diversify for its own sake. UA budget planning that accounts for platform risk builds a contingency line into the budget the same way a finance team builds in currency risk or vendor concentration risk, as a named item rather than an unstated hope.
Why this fortnight is different
Platform terms have shifted before without triggering a rethink of budget process, because most shifts have been incremental: a policy tweak, a fee adjustment, a new consent flow. What makes April different is the number of live legal processes touching the platforms a typical UA budget depends on. Google faces ad tech antitrust remedies in the US and a separate injunction over Play Store practices already in force. Apple is contesting a DMA fine while its own anti-steering compliance in the US remains under active court scrutiny following Epic v Apple. Meta is appealing its own DMA penalty. None of these processes will resolve quickly, and all of them can produce interim changes before they do.
A budget that assumes the status quo through December is not being conservative. It is simply not pricing in a risk that is already visible in the public record.
What platform risk actually costs a UA team
The direct cost of a platform ruling is rarely the fine itself, since that falls on the platform's balance sheet, not the advertiser's. The cost to a UA team shows up in three places: forced migration of measurement infrastructure when an SDK or attribution flow changes with short notice, spend reallocation when a channel's economics shift mid-quarter, and opportunity cost from decisions delayed while a team waits to see how a ruling settles. Of the three, delay is the most common and the most avoidable.
Delay is expensive because it is invisible until the deadline forces a decision. A team that waits to see how the Google ad tech remedies phase resolves before touching its measurement stack loses nothing this month and next month, and then loses several weeks of engineering time in a scramble the month a change actually lands. The same pattern played out during the SKAdNetwork to AdAttributionKit transition: teams that migrated early absorbed a small, predictable cost, and teams that waited absorbed a larger, unpredictable one on someone else's timeline.
UA budget planning for platform risk: a scoring framework
A practical way to build this into quarterly planning is to score each major spend channel on two axes: how concentrated your spend is on that platform, and how many live regulatory or legal processes currently touch it.
- High concentration, high exposure: channels where a single platform accounts for more than a third of spend and is named in an active antitrust or DMA process. These need an explicit contingency allocation, typically five to ten percent of that channel's budget, held back rather than committed at the start of the quarter.
- High concentration, low exposure: channels with concentrated spend but no active legal process. These still warrant a documented fallback plan, even if no budget is set aside yet.
- Low concentration, high exposure: channels already diversified enough that a single ruling would not meaningfully disrupt total spend. Monitor but do not overreact.
- Low concentration, low exposure: standard budget process applies.
Run this scoring exercise at the same cadence as the rest of quarterly planning, not as a one-off reaction to this fortnight's news. A platform's exposure score changes as cases move through appeal, and a budget review that only looks at it once a year will miss the point where an interim ruling actually forces a change.
Building the contingency line without slowing spend down
The instinct to hold cash back against platform risk can turn into an excuse to under-deploy budget generally, which defeats the purpose. The fix is to name the contingency explicitly in the plan, with a trigger condition attached to it rather than a vague reserve. For example: five percent of Google-dependent spend held back, released automatically if no material change to Play Store terms or ad tech remedies occurs by the next quarterly review, and redirected to a named secondary channel if it does. A contingency without a release condition just becomes unspent budget, and an unspent budget line is the first thing cut when a growth target is missed. Put a named owner against the trigger too, usually whoever runs the platforms relationship, so the decision to release or extend the hold does not sit with finance alone at the point it actually needs making.
What this means for the rest of the year
None of this argues for pulling spend off Google, Apple or Meta this quarter. It argues for treating the terms those platforms operate under as a variable the budget accounts for rather than a constant it assumes. UA budget planning that keeps platform risk as a standing agenda item, reviewed every quarter rather than only after a headline, is the version that holds up. The teams that build that habit now, while the changes are still procedural rather than operational, will spend less time firefighting when one of these rulings eventually produces a change that reaches an actual campaign setting.
