Ad Network Q4 Guidance and What It Signals for Buyers

Earnings calls are written for investors, not buyers. That does not make the guidance section of a Q3 call safe to skip: when a platform tells its shareholders what it expects Q4 to look like, it is also telling every buyer on that platform how the auction will feel, what inventory demand will look like and where pricing will land over the next three months. Read it that way and the call stops being investor theatre.

What the two networks reported this quarter

AppLovin's Q3 2025 results, reported November 5, showed advertising revenue of roughly 1.41 billion dollars, a beat against its own prior guidance, and the company raised its outlook for the following quarter; that continues a run which began with Q2's 1.259 billion dollars in revenue, up 77 percent year over year, and a Q3 guide at the time of 1.32 to 1.34 billion dollars at an 81 percent adjusted EBITDA margin. Its self-serve e-commerce advertising push, expanding beyond the gaming roots, looks like it is scaling alongside the core gaming business rather than cannibalising it, at least judging by the guidance language management has used.

Unity's Q3 2025 update pointed to continued ad revenue growth built on its Vector ad model, following a Q2 print in which total revenue came in at 441 million dollars, down slightly year over year but ahead of expectations, with Unity Ad Network revenue up 15 percent sequentially and now representing roughly half of Grow Solutions. Vector is the rebuilt ad model Unity unveiled at GDC in March. CEO Matt Bromberg has described the transition as reaching an inflection point rather than a completed turnaround. Take that at face value: Unity has been careful about declaring victory on Vector at every earnings call this year, from the deliberately cautious tone around Q1 to the more confident but still qualified framing by mid-year.

Reading guidance as a demand signal, not just a revenue number

Headline revenue figures matter less to a buyer than what management says is driving them. AppLovin publicly attributes its raised guidance to advertiser demand scaling across both gaming and the newer e-commerce vertical, which suggests broadening rather than concentrated demand, and broadening is the healthier signal for anyone worried about a single vertical crowding out inventory. Unity's guidance language still frames Vector as a migration in progress, which tells a buyer that pricing and inventory behaviour on Unity's network may stay less stable quarter to quarter than on a platform with a fully mature model, since a system someone is still tuning tends to produce more variable auction dynamics than one settled into steady state.

A framework for translating guidance into your own assumptions

The questions worth asking of a Q3 call have almost nothing to do with the topline number.

Does management call the growth broad-based across advertiser categories, or concentrated in one vertical? Concentrated growth sits more exposed to a single category's budget cycle, and that cycle reaches your own auction pricing soon enough. Does management describe any part of the business as still migrating or transitioning? A platform mid-transition is likelier to produce inconsistent week-to-week performance than one management calls stable. Then the margin question. A platform expanding margin while it grows revenue is typically not compensating advertisers with cheaper inventory to hit its numbers, which a buyer should read as a hint that pricing pressure will persist rather than ease.

Apply that to this quarter. AppLovin's combination of broad-based growth, raised guidance and a stated margin around 81 percent points toward continued pricing pressure on its network rather than an easing, which is useful context for anyone planning Q4 budget allocation, while Unity's continued transition language suggests more week-to-week variability on its network than on a fully mature platform, and that argues for slightly more conservative budget commitments there until Vector's rollout, discussed at length in this desk's earlier coverage of AppLovin and Unity's diverging Q2 2025 paths, settles further.

A short checklist before the December budget conversation

Before finalising December platform splits, run a quick check against each major network's most recent guidance instead of trusting your memory of the headline number: confirm whether the guidance called growth broad-based or concentrated in a single advertiser category, note whether management used transition or migration language for any part of its ad stack, check whether margin expanded alongside revenue, and compare the current quarter's guide against what the platform actually delivered against its prior quarter's own guidance. A platform that has beaten its own guidance for several consecutive quarters, as AppLovin has through 2025, is a different proposition from one still working through a multi-quarter migration, and the December split should reflect that rather than treating every network as equally predictable.

What this means heading into December budget conversations

None of this earnings-call reading replaces a buyer's own platform-level performance data, which remains the primary signal for any specific campaign. But guidance language is a leading indicator that arrives before your own dashboards show the shift it describes, and a buyer who reads Q3 guidance in early November has roughly six weeks of runway to adjust Q4 platform allocation before the holiday spend commitments become difficult to unwind. Digital Turbine's more modest fiscal Q2 2026 stabilisation commentary this quarter is a reminder that not every platform tells the same growth story, which is exactly why reading guidance platform by platform beats treating ad tech earnings season as one signal. The specific numbers will change again once Q4 results land in February; the habit will not.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• Reading Q3 Ad Earnings Season Signals for UA Buyers
• Android attribution reporting after Sandbox