iOS 26 Didn't Break CTV. It Broke the Workarounds.

Table of Contents

Clients have been asking how Apple’s iOS 26 affects their campaigns on The Trade Desk. Our answer: iOS 26 didn’t break CTV. It broke the workarounds.

The longer answer depends on two things: what you are buying, and how your identity data gets to the platform. I posted a version of this on LinkedIn in October. This is the fuller one, with the questions I would ask my agency if I were on the client side.

Connected TV: no impact, on one condition

For CTV-only campaigns, The Trade Desk remains the best DSP choice for many brands. It has the deepest CTV supply through direct publisher relationships, it is the largest independent DSP, and it offers open measurement, including brand lift through third-party partners.

iOS 26 does not affect CTV-only campaigns, provided the client uses a server-to-server integration instead of browser-based measurement. That condition is the whole story, so here is how it works.

When a new customer agrees to your privacy policy, and the requirements for your industry and their state are met (insurance and healthcare have their own), you collect their email address. That email is exchanged with The Trade Desk, under a provider agreement or through your agency, for a UID2. The UID2 is then used for targeting and attribution. Nothing in that chain touches a browser, so nothing in it is touched by iOS 26.

This was already the privacy-first practice we recommend to clients by default. iOS 26 made it the only practice.

Apple TV is not an iPhone

iOS 26 applies to iPhones and iPads. Apple TV runs tvOS, a separate operating system, and it continues to support UID2, RampID, Yahoo ConnectID and the other privacy-friendly identifiers. Streaming is a logged-in medium. That is why identity holds up on the television when it is falling apart in the browser.

This is not a happy accident. Apple is rewarding the companies that respect privacy, and telling them their technology investments will hold up.

Where CTV campaigns do get into trouble

The weak spot is UID2s captured in the browser rather than exchanged server to server. That was already a finicky approach. Client audits regularly turn up problems with it, and iOS 26 makes it worse. If your agency set up UID2 by dropping a tag on the site, the connected-TV measurement you are reading is thinner than it looks, and it got thinner in September.

Display and online video: the workarounds are over

For campaigns built on display and online video, the impact on The Trade Desk is substantial.

To get around Apple’s ban on third-party cookies in Safari and on iOS, our industry embraced probabilistic workarounds for measurement and attribution. iOS 26 ends most of them. Seed audiences are not filling. Browser-based targeting on iPhones and iPads is degraded. Pixel-based attribution, which already undercounted, now undercounts further.

Our industry spent years engineering around consent. In our view, Apple’s privacy-first message is deserved and unsurprising.

What we are telling clients

Invest in three things: consented first-party data, server-side integrations, and context.

On DSP choice, specifically:

1. Display and online video with a CPA goal. Consider DV360 or Amazon DSP, where signed-in user data is more available.
2. The Trade Desk. Use it for CTV-only campaigns with a CPA goal, or for omnichannel campaigns where a brand study is the north-star goal and you don’t have first-party audience data. Asset managers are the typical case.
3. Contextual. Overweight contextual strategies for display and online video, and factor that into platform choices.

Four questions to ask your agency this quarter

If you run a marketing team and you are not sure where you stand, these four questions settle it.

1. Where do our UID2s come from? The answer should be a server-to-server exchange of consented emails. If the answer is “a tag on the site,” ask for the match rate before and after September.
2. Which of our conversions are pixel-based, and what is the undercount? Every pixel-based conversion on iOS is now lower than the true figure. Your agency should be able to show you the gap, by channel, against your own analytics.
3. Which DSP is carrying which objective, and why? One platform is rarely right for both a CPA goal on display and a brand goal on CTV. If everything runs in one DSP, ask what that is costing you.
4. What share of our display targeting is contextual? If the answer is a shrug, the plan was built for a browser that no longer exists.

Swim with the tide

Apple has been heading in one direction for nearly a decade, since it effectively banned third-party cookies. We are encouraging clients to swim with the tide: collect consent, move identity server-side, and buy context where identity is gone.

I’d like to hear what other agencies are telling their clients. If you want to trade notes, I’m at mike@adnode.net.