How Apple’s iOS 27 Tracking Changes Affect Advertisers

Apple’s iOS 27 release introduces a more dynamic approach to blocking the digital connections that support advertising identity, measurement, and delivery. Beginning September 14, Apple blocked requests to domains associated with several prominent programmatic identity and data providers, including The Trade Desk, UID2, LiveRamp, ID5, Permutive, and Audigent. The initial effects vary by provider and function, and recent industry reporting suggests Apple may extend this approach to a broader range of customer data, advertising technology, marketing technology, and identity providers.

This analysis explains what’s changing, how it may affect active campaigns, and what advertisers can do next. At PMG, we are combining industry developments with campaign-level and aggregate delivery data to help our customers distinguish immediate disruption from longer-term signal loss.

Apple Is Moving Toward More Dynamic Tracking Controls

Apple is changing how WebKit, the browser engine that powers Safari and most browsers on iOS, governs connections associated with cross-site tracking. In practice, this could give Apple more flexibility to update which tracking connections are restricted as the advertising ecosystem evolves. While parts of the technology are visible in public WebKit commits, Apple has not published a complete list of affected vendors or fully documented how the controls will evolve. Connected TV, authenticated environments such as YouTube, retail media networks, and direct publisher deals are less directly exposed, although downstream measurement and identity effects may still extend across channels. 

The most immediate exposure is in open-web display and video inventory accessed through affected browsers on Apple mobile devices.

• A More Flexible WebKit Blocking Mechanism: Historically, major changes to Intelligent Tracking Prevention (ITP) were closely associated with iOS or Safari software updates. Public WebKit code now indicates that Apple may be able to identify and block connections to known cross-site trackers without waiting for a major software release. Industry reporting also suggests the affected-domain list may be maintained separately, allowing restrictions to evolve more quickly than traditional ITP rules. Apple has not publicly documented the complete architecture, vendor criteria, or update cadence. 

• Broad Reach Across iOS Browsers: On iOS and iPadOS, most third-party browsers, including Chrome, Edge, and Firefox, use Apple’s WebKit engine, with limited regional exceptions. As a result, affected tracking restrictions can extend beyond Safari across mobile browsing on iPhones and iPads. This does not mean that all browsers on Macs use WebKit; macOS browsers can use other engines and may not be affected in the same way.

What Advertisers Should Expect

The most likely near- and medium-term effects for active campaigns include the following.

Gradual Erosion of iOS Addressability

As iOS 27 adoption increases, addressable inventory on affected Apple mobile traffic may decline, reducing match rates for some third-party audience segments. The pace and scale of that decline will depend on adoption, Apple’s evolving block list, and the endpoints each vendor uses.

Active Monitoring of iOS and Safari Delivery

PMG is monitoring aggregated campaign data to distinguish changes in media delivery from changes in identity and measurement quality. Across the period analyzed, PMG observed no evidence of an aggregate collapse in iOS and Safari programmatic delivery. Separately, TelemetryDeck estimated iOS 27 adoption at approximately 16% at the end of September across its predominantly American and European global dataset. Because most observed Apple traffic remained on earlier operating-system releases, the effects may become clearer as adoption grows. 

Apple’s Blocking Disrupted Affected Bids

The initial loss of The Trade Desk activity on affected Safari inventory appears to have resulted from Apple blocking the company’s ad-serving domain, which prevented requests from completing, rather than from DSPs voluntarily suppressing bids. As of October 14, public reporting indicated that Apple had removed The Trade Desk’s ad-serving domain from the iOS 27.2 beta block list, although the UID2-related endpoint remained affected. Because the situation is evolving quickly, advertisers should evaluate impacts on serving, identity, and measurement separately and confirm the latest status before making campaign changes.

Frequency Capping and Pixel Degradation

Without durable cross-site identifiers, frequency management on affected iOS and Safari web inventory can fragment, increasing the risk of ad fatigue. Client-side conversion pixels may also lose signal, making standalone last-touch and multi-touch attribution increasingly unreliable.

How Advertisers Should Respond 

At PMG, we recommend focusing on four practical actions that strengthen resilience without requiring advertisers to overhaul their media strategies prematurely:

1. Establish an iOS and Safari Baseline: Start by quantifying the share of programmatic display and online video delivery, audience matching, and conversion attribution associated with affected Apple traffic. Although aggregate delivery has remained steady across PMG’s portfolio, a campaign-level baseline can help identify changes early and distinguish a delivery issue from an identity or measurement issue. PMG teams can help advertisers assess that exposure and prioritize adjustments where the data indicates a meaningful impact.

2. Accelerate Conversions API Implementation: Prioritize consented server-to-server integrations with the highest-volume media platforms. These connections reduce reliance on browser-based tags and can make conversion-event delivery more reliable as privacy restrictions evolve. They do not restore identifiers that WebKit has limited or blocked, so advertisers should distinguish between receiving a conversion event and being able to attribute it fully to an earlier ad interaction.

3. Expand Private Marketplace and Contextual Strategies: Consider shifting appropriate iOS and Safari open-exchange prospecting investment toward authenticated publisher private marketplaces and high-intent contextual targeting. Through Alli, PMG helps advertisers identify more direct, brand-suitable supply opportunities and align placements with relevant content without relying as heavily on cross-site identity signals.

4. Center Measurement on Incrementality: As browser-based attribution becomes less complete, place greater weight on whether advertising caused an incremental business outcome. Geo-experiments, holdout tests, and cross-channel modeling can provide a more durable view of performance than click-based or view-through pixel metrics alone. At PMG, we recommend using these approaches alongside platform reporting rather than treating any single measurement method as definitive.

Advertisers Should Prepare for Gradual Signal Loss, Not an Immediate Delivery Collapse

Apple’s reported changes point to a more flexible system for updating browser tracking restrictions. The immediate evidence does not suggest that iOS and Safari delivery has collapsed, but identity matching, frequency management, and attribution may become less reliable as adoption grows and the affected-domain list evolves.

Brands can prepare by strengthening consented first-party data, improving server-to-server conversion tracking, expanding contextual and direct-publisher strategies, and adopting measurement methods that are less dependent on browser identifiers. Through Alli and our relationships with media and technology partners, PMG helps advertisers determine whether an observed change reflects a delivery, identity, or measurement issue and choose an evidence-based response without overcorrecting prematurely.