Paul Bannister, chief strategy officer at Raptive, wrote in a LinkedIn post on October 8, 2026 that the blocking of The Trade Desk's ad delivery domain is very likely a test of whether Apple can control advertising at the source, and sketched a scenario in which Apple blocks every demand-side platform and then unblocks them for a 20% payment.

In Short

A senior executive at a company that places ads on websites wrote on LinkedIn that Apple's new advertising terms and its blocking of one big ad company's web address in Safari may be early steps toward making other ad companies pay Apple to operate. It matters because websites, advertisers and the companies in between rely on those ad systems to buy and sell the space on the pages you read, and nothing public shows that Apple plans such a fee. For now the fee idea is one person's forecast, Apple has not explained the block, and a public bug report shows Apple and The Trade Desk testing a possible change.

What Bannister argued

The post, which carries an "edited" label, opens with a disclaimer - "I am not paranoid. But sometimes they really are out to get you." - and then builds its case in four steps.

The first concerns Apple's Services business, which Bannister describes as a major growth engine of the company over the last 10 years. He argues that it is under threat because the vast majority of the business's revenue comes from what he calls an "extortionate 30% fee on App Store sales," and that governments are finally cracking down on the fee in a way that will be hard for Apple to escape. As the arrangement is slowly shut down, he writes, Apple is looking for "their next grab." A chart attached to the post plots Apple's annual revenue by category for fiscal years 2016 to 2025. As read from the chart, the Services line climbs from the low $20 billions to above $100 billion, while iPhone revenue moves from roughly $135 billion to above $200 billion. A footnote says 2016 uses the original reporting basis and that 2017 onward reflects Apple's revised classification of bundled services, so the first year is not strictly comparable.

The second step is Apple's recent update to its advertising terms of service. Previously, Bannister says, the terms were tightly scoped to Apple's own apps. The new language, in his reading, lets Apple run ads "pretty much wherever they want," including on the web and in other companies' mobile apps.

Third, he turns to lists. Apple's maintenance of lists of companies clearly involved in the web advertising market is troubling in itself, he writes. He then puts the word "accidental" in quotation marks, noting that the marks are his own, when describing the blocking of The Trade Desk's ad delivery domain, and judges it "very likely a test of whether they can control ads at the source." Readers are asked to imagine a world 18 to 24 months ahead, "when Apple blocks all DSPs and says they'll unblock them if they pay a 20% tax to Apple." He says he would assume the same happens in the mobile app ad market. A DSP, or demand-side platform, is the software through which advertisers buy ad impressions.

The last step contests Apple's stated rationale. Apple has said for years that its actions serve privacy, Bannister writes, but "it's all been a long con": in his view the policies are a way to build new infrastructure to "extract rent from other ecosystems."

The post does not name the browser. Its description of a blocked ad delivery domain matches the adsrvr.org restrictions that were traced to a WebKit change and that AdExchanger reported in Safari 27 and iOS 27, covered below.

According to his LinkedIn profile, Bannister has been chief strategy officer at Raptive since April 2020, having served as executive vice president of strategy there from October 2006. The profile also lists a seat on the board of IAB Tech Lab since January 2021 and a limited partner role at FirstPartyCapital since July 2021. When the page was captured, the post had 61 reactions, 17 comments and four reposts, and the profile showed 7,249 followers. Raptive manages advertising for web publishers, which places the company on the supply side of the market the post describes; IAB Tech Lab is the standards body behind the Trusted Server specification that publishers are now exploring, as discussed further down.

The Apple Ads terms rewrite

Apple emailed advertisers on July 14, 2026 about an update to its Advertising Services Terms of Service, with the new version taking effect on July 28. It replaced a version dated February 1, 2024. The change sits in Section 6(a), which defines where Apple may deliver ad content. The earlier text confined delivery to relevant Apple software applications or Apple devices. The new text extends it to relevant devices, operating systems, software or web applications, and other platforms or properties - a formulation that is not limited to surfaces Apple operates. Apple groups these under the label Properties, and the definition of ad content also grew to cover items such as web pages and links.

Apple has not publicly explained the change. The notice states that continued use of the advertising services on or after July 28 counts as acceptance, and it names no launch date, market or non-Apple surface. The update also set a 150-day threshold, counted from the initial payment due date, for Apple's right to offset unpaid amounts against sums it owes advertisers, and allowed Apple to use advertiser data and business user data to develop, train and test AI and machine learning models.

The advertising business those terms govern was already growing. Apple rebranded Search Ads as Apple Ads on April 14, 2025. Chief financial officer Kevan Parekh said on the July 30, 2026 earnings call that advertising set a June-quarter revenue record. Apple disclosed no dollar figure; eMarketer estimates the year's Apple Ads revenue at roughly $8.5 billion.

The iOS 27 restrictions and the open bug report

The technical record starts on February 13, 2026, when Charlie Wolfe opened WebKit bug 307853. At 15:48 Pacific time that day the change landed as commit 307525@main, adding 11 lines and removing none in Source/WebKit/Platform/cocoa/WebPrivacyHelpers.mm. It adds a macro, IS_REQUEST_UNCONDITIONALLY_BLOCKABLE, whose public default returns false. Apple's internal builds can import a real definition from a file named WebPrivacyHelpersAdditions.mm, which is not in the public repository. The check runs before the existing tracker exemption and applies to the registrable domain, so every subdomain of a listed domain is caught. Apple has published neither the list nor a reason for it.

Apple began rolling out iOS 27 on September 14, 2026. A week later, on September 21, Ian Meyers of The Trade Desk filed WebKit bug 324771 listing nine domains: adsrvr.org, uidapi.com, id5-sync.com, eu-1-id5-sync.com, rlcdn.com, pippio.com, permutive.com, ad.gt and tainted.example. According to Meyers, the entries belong to UID2, ID5, LiveRamp, Permutive and Audigent; Apple has not verified that. John Wilander of Apple replied on September 22 that Apple was investigating and on September 28 that he would say if changes were ready to test. AdExchanger reported the block on September 29, and neither Apple nor The Trade Desk answered the outlet's requests for comment before publication.

Two of the nine domains belong to ID5, the identity provider whose co-founder and chief executive, Mathieu Roche, posted on LinkedIn on October 3 suggesting that more regulators look at Apple's business practices. AdExchanger later reported that the list may now include hundreds of companies, and says Apple has not confirmed the expansion. ID5 says its deployment is close to 100,000 sites, citing Sincera data from January 2025 that has not been independently audited. According to Cloudflare, Safari accounted for 15.1% of global browser traffic in the third quarter of 2025.

Other Safari 27 behaviors surfaced earlier. A source-code review published by Mariusz Brucki on the TAGGRS blog on July 6, 2026 found that the beta terminates connections to Microsoft's Bing event-tracking endpoint by IP address and classifies LinkedIn's Insight Tag for fingerprinting restrictions. Apple's public release notes for Safari 27 did not mention these behaviors.

On October 5, Wilander told Meyers that a new iOS 27.2 beta had shipped and asked him to test it, thanking him for the technical documentation. Meyers answered 15 minutes later that he could see changes in build 24B5099f and that his company would test and report back. As of October 8, the bug's status was still NEW and assigned to nobody, and Apple had offered no explanation of the blocks.

Services revenue and the regulatory record

Apple's Form 10-Q, filed July 31, 2026, put Services revenue for the June quarter at $30.739 billion, up 12% from $27.423 billion a year earlier. Apple attributed the growth primarily to higher net sales from advertising and cloud services, and gross margin held flat at 75.6%. The post gives no figure for the share of Services revenue that comes from App Store commissions, and none of the material reviewed for this article breaks it out, so that part of the argument rests on Bannister's characterization.

Legal pressure on the commission is documented. The same PPC Land report notes that the Ninth Circuit on December 11, 2025 upheld an injunction over App Store link-out purchases in part, allowing Apple to charge some commission on them, and that the Supreme Court on June 30, 2026 granted review of the civil contempt standard.

The privacy rationale Bannister attacks has its own history. App Tracking Transparency arrived with iOS 14.5 on April 26, 2021 and required apps to ask permission before tracking users across other companies' apps and websites. On March 30, 2025 the French competition authority fined Apple €150 million, finding an abuse of a dominant position in iOS and iPadOS app distribution. The authority accepted that privacy protection is a legitimate goal but found that the framework went beyond what was necessary and proportionate, and that Apple applied different standards to its own apps than to third-party publishers. That is a narrower finding than the "long con" Bannister describes, and it concerned ATT rather than the App Store commission.

How the comment thread reacted

Gareth Glaser, a cofounder, suggested another implementation: advertisers wanting to buy ads would do so from the Safari interface via approved partners Apple controls, "extending the Apple News model to all of safari." Bannister replied that this is "an even easier model," adding that Apple could offer advertisers better targeting than anyone else because "they've destroyed the performance model of the web in its current incarnation."

Vishveshwar Jatain, founder of And/or Labs, wrote that "Apple has strayed so far away from its founding vision." Bannister answered that "All of the giant companies are looking for any angle they can find to make money to keep growing, and most of them are just flat-out scams" - a remark that covers large technology companies generally rather than Apple alone.

Lila H., vice president of display at System1, observed that the anticompetitive attention on Google would make such a path legally interesting for Apple to pursue. Bannister replied: "I hope you are right, but I fear governments are just too slow." Jana Meron, principal at Lioness Strategies, wrote that "The death of the cookie was never about privacy. This is about who controls the pipes and what they can extract from it." Lila H. responded that "cookies were the safest form of tracking. Totally anonymous, completely within users' control." In the visible portion of the thread, none of the commenters offered evidence of a planned Apple fee.

What remains unconfirmed

Bannister framed the 20% payment as a scenario to imagine, not as a reported plan, and no source reviewed for this article reports Apple preparing a charge to unblock DSPs, or to give any ad company access to Safari or iOS users. Apple has not published the contents or scope of its block list, has not explained why it exists, and has not confirmed the reported expansion to hundreds of companies. The bug report remains open. The October 5 exchange shows engineers testing a build, which does not establish what the final behavior will be.

The claim that the Ads terms and the block list are connected is likewise Bannister's inference. The terms change widens a contractual definition without naming any product, while the WebKit change concerns request blocking in the browser. Whether the two serve a single strategy is something the public record does not settle.

Why it matters to buyers and publishers

The more immediate effects are already visible on the supply side. Digiday reported on October 8 that the block list has pushed publishers back toward Trusted Server, which IAB Tech Lab unveiled in March 2025 and which moves ad tech processing from the reader's device to publisher-controlled servers. Rowena Lam, IAB Tech Lab's product lead for Trusted Server, described a large influx of publishers reaching out but gave no number, and Tech Lab is preparing to go live with a first publisher. Paradium, the owner of Men's Journal and Parade, rerouted Permutive code through Trusted Server and is testing whether audience data flows again in Safari. Its head of revenue and data, Stephanie Mazzamaro, said most of the remaining work lies in viewability, verification and getting buyers to accept the numbers. Justin Wohl of Aditude said that those who control the operating system hold great control.

For identity providers and the DSPs that depend on them, the exposure turns on Safari's share of traffic, 15.1% globally on Cloudflare's measure, and on how many sites run the affected domains. For publishers, the question is whether server-side routes can replace what a browser-side script provided. For advertisers, the practical issue is whether audience data and measurement signals keep flowing on iOS devices while the bug stays open.

Beyond those mechanics sits the structural point Bannister raises, and which Jana Meron put in different words: a browser and operating system vendor that also sells advertising, and whose Services revenue rose in the June quarter mainly on advertising and cloud, decides which third parties may operate on its platform. Apple's terms now permit it to deliver ads on properties beyond its own. Whether that permission becomes a product, and whether the block list becomes a gate with a price attached, are questions the next iOS 27.2 build and any Apple statement on bug 324771 would begin to answer.

Timeline

  • January 2021: Bannister joins the board of IAB Tech Lab, according to his LinkedIn profile.
  • April 26, 2021: Apple releases App Tracking Transparency with iOS 14.5.
  • February 1, 2024: Prior version of Apple's Advertising Services Terms of Service takes effect.
  • March 2025: IAB Tech Lab unveils Trusted Server.
  • March 30, 2025: French competition authority fines Apple EUR 150 million over ATT.
  • April 14, 2025: Apple rebrands Search Ads as Apple Ads.
  • December 11, 2025: Ninth Circuit upholds an App Store link-out injunction in part.
  • February 13, 2026: WebKit bug 307853 opened and commit 307525@main merged.
  • June 30, 2026: Supreme Court grants review of the civil contempt standard.
  • July 6, 2026: TAGGRS blog publishes a source-code review of Safari 27 blocking behavior.
  • July 14, 2026: Apple emails advertisers about updated Ads terms.
  • July 28, 2026: Updated Advertising Services Terms of Service take effect.
  • July 30, 2026: Apple reports a June-quarter advertising revenue record; Services revenue of $30.739 billion follows in the Form 10-Q filed July 31.
  • September 14, 2026: iOS 27 rollout begins.
  • September 21, 2026: Ian Meyers of The Trade Desk files WebKit bug 324771.
  • September 22 and 28, 2026: Apple's John Wilander says Apple is investigating, then that he will report when changes are ready to test.
  • September 29, 2026: AdExchanger reports the block.
  • October 3, 2026: ID5 chief executive Mathieu Roche posts on LinkedIn about the block.
  • October 5, 2026: Wilander asks Meyers to test an iOS 27.2 beta; Meyers reports changes in build 24B5099f.
  • October 8, 2026: Digiday reports publishers turning to Trusted Server.
  • October 8, 2026: Bannister publishes the LinkedIn post.

Summary

  • Who: Paul Bannister, chief strategy officer at Raptive and IAB Tech Lab board member; Apple; The Trade Desk, whose ad delivery domain is blocked in Safari 27; identity and data companies such as ID5, LiveRamp and Permutive; commenters including Gareth Glaser, Vishveshwar Jatain, Lila H. and Jana Meron.
  • What: Bannister argued that Apple's rewritten Ads terms, its lists of web advertising companies and the blocking of The Trade Desk's ad delivery domain may be groundwork for controlling ads at the source, and described a hypothetical in which Apple blocks all DSPs and unblocks them for a 20% payment. No source reports that Apple plans such a charge.
  • When: The post was published on October 8, 2026. The related events run from the July 14 and July 28, 2026 terms change to the October 5, 2026 iOS 27.2 beta test request.
  • Where: On LinkedIn; the underlying changes affect Apple's advertising terms, Safari 27 and iOS 27, and the ad tech and publisher markets that depend on Safari traffic.
  • Why: Bannister ties the moves to pressure on Apple's 30% App Store commission, arguing that Apple is seeking new revenue from other ecosystems. Apple has not explained the block list or the terms change, and its public bug-tracker exchanges show only that it is investigating and testing a build.