On August 27, Apple changed how much money you keep from a sale in three countries. On September 14, it changes what customers pay in four. Neither event appears anywhere in Apple Ads — and both of them move the most you can rationally bid.
The Apple Ads news feed has published nothing since August 21. The Apple Developer news feed has published at least three items in the same window that change the revenue side of every advertiser’s bid math. Those are two different feeds, read by two different people inside most companies, and the gap between them is where this article lives.
The high-ARPU case for Apple Ads has never rested on cheap taps. It rests on the fact that the App Store audience spends far more per head than any comparable install channel, and that search placement intercepts intent a user has already declared by typing. Both halves of that argument are statements about net revenue per user. When Apple changes net revenue per user by decree, the case changes with it — quietly, on a date published somewhere the media buyer never looks.
01What actually changed on August 27
Apple’s developer notice, titled “Tax and price updates for apps, In-App Purchases, and subscriptions” and dated August 27, 2026, does two separate things in one page.
First, effective immediately, it modified proceeds in three places: a value-added tax introduction of 20% in Morocco, a VAT introduction of 18% in the Republic of the Congo, and a digital sales tax increase from 2% to 3% in Tanzania. Apple’s wording is flat and past-tense: “Your proceeds from the sale of eligible apps and In-App Purchases have been modified in…”. It also notes that Exhibit B of the Paid Applications Agreement will be updated to record that Apple collects and remits applicable taxes in Morocco and the Republic of the Congo.
Second, beginning September 14, pricing for apps and In-App Purchases will be updated in Israel, Indonesia, Morocco and the Republic of the Congo — a partly overlapping, partly different list. Two of those four countries are on the list for tax reasons; the other two are there for foreign-exchange equalisation.
Apple frames all of this as routine housekeeping — the same page notes the App Store supports 43 currencies across 175 storefronts and that prices adjust “from time to time” against published exchange rates. The routine is the point: it happens on a rolling schedule, and nothing in the advertising stack observes it.
02Why a VAT introduction is a proceeds cut, not a price rise
The mechanism matters, and it is not obvious.
App Store customer prices in VAT jurisdictions are tax-inclusive. The shopper sees one number and pays it. Apple’s App Store Connect documentation defines the developer’s share precisely: proceeds are “the amount you’ll receive on sales of your apps and In-App Purchases,” calculated as the customer price minus applicable taxes and then Apple’s commission, per Schedule 2 of the Paid Applications Agreement. Tax comes off first. Commission applies to what remains.
So when a 20% VAT arrives on a price that already includes it, the tax is not 20% of what you were getting. It is 20 ÷ 120 of the gross — about 16.7% — and the ex-tax base falls by that proportion before Apple takes anything. Derived, and flagged as derived: a product previously sold untaxed at 100 units of local currency with a 30% commission netted 70. After the VAT introduction, the same headline price yields an ex-tax base of 83.3, and 70% of that is 58.3. The developer keeps roughly 16.7% less from an identical transaction at an identical price.
Apple does not publish that percentage. It publishes the rate and the order of operations, and the arithmetic follows. The 18% Congolese VAT works out to roughly 15.3% of gross on the same basis; Tanzania’s one-point digital sales tax increase is far smaller, removing roughly one additional percentage point of gross.
→ THE COMMON MISREADING
“A 20% tax means 20% less revenue”
It means about 16.7% less, because the tax is carved out of a price that already contained it. Three and a half points is the difference between a bid ceiling that holds and one that quietly stops paying back.
03The scope test: which of these countries you can actually buy
Here is the discipline most coverage skipped. A change to developer proceeds only reaches your bidding if you can run a campaign in that storefront at all.
Apple’s own countries and regions page for Apple Ads, accessed September 2, 2026, lists Morocco under Africa, Middle East and India, Israel in the same group, and Indonesia under Asia Pacific. It does not list Tanzania. It does not list the Republic of the Congo. Morocco became buyable in the October 2024 expansion that added 21 markets including Türkiye, Kenya, Ghana and Algeria.
That splits the announcement cleanly:
| Country | What changed | Effect on Apple Ads bidding |
|---|
| Morocco | 20% VAT introduced Aug 27; price update Sept 14 | Direct — buyable storefront, proceeds cut, partial repricing |
| Israel | Price update Sept 14 only (FX equalisation) | Direct — buyable storefront, no tax change |
| Indonesia | Price update Sept 14 only (FX equalisation) | Direct — buyable storefront, no tax change |
| Rep. of the Congo | 18% VAT introduced Aug 27; price update Sept 14 | None — not an Apple Ads storefront |
| Tanzania | Digital sales tax 2% → 3% | None — not an Apple Ads storefront |
Three of the five matter to a media buyer. Two are organic-only economics. Note also the direction of the surprise: Israel and Indonesia are on the September 14 list with no tax event at all, purely because the currency moved. Exchange-rate repricing changes your revenue per install just as effectively as a tax does, and it arrives with no policy announcement attached.
04September 14 repairs the price — except where it doesn’t
Apple’s price update is a repair mechanism. It raises local prices so that, after the new tax, the ex-tax proceeds line up again with the base storefront you chose. If it worked universally, the August 27 cut would be a two-and-a-half-week inconvenience.
It does not work universally, and Apple lists the exclusions itself. Prices update only if you have not selected that storefront as your base — if Morocco is your base storefront, its price stays put and every other storefront moves around it. They do not update where you manage prices manually instead of using automated equalised pricing. And, in Apple’s exact words: “Prices won’t change in any region if your In-App Purchase is an auto-renewable subscription.”
Read that last exclusion against who actually buys Apple Ads. Subscription apps are the heaviest and most sophisticated spenders on the platform — the category with the payback models precise enough to bid to a ceiling in the first place. They are the one group Apple’s automatic repricing does not reach.
≈16.7%
The proceeds reduction a Moroccan sale takes from the 20% VAT introduction — derived from Apple’s stated order of deductions on a tax-inclusive price. For an auto-renewable subscription, Apple’s September 14 price update will not restore any of it, because Apple states subscription prices do not change.
A subscription business selling into Morocco therefore woke up on August 27 with materially less revenue per acquired user and no scheduled remedy. Raising the price is available, but it is a manual decision with its own conversion consequences — and it is a decision nobody makes if they never read the notice.
05What this does to the maximum you can pay for a tap
The bid ceiling we use in the high-ARPU argument for Apple Ads is arithmetic, not opinion:
Maximum cost per tap = (net revenue per download × tap-to-download conversion rate) ÷ payback multiple
Every term on the right is something you can observe. Net revenue per download is what Apple actually pays you. Conversion rate is what your campaign reports. The payback multiple is a policy choice about how fast the money has to come back.
Derived illustration, flagged as derived. Take an app netting the equivalent of $1.00 per download in Morocco, converting taps to downloads at 60%, run at a 1.0× payback multiple. Before August 27 the ceiling was $0.60 per tap. After a 16.7% cut to net revenue, the same formula gives $0.50. A 16.7% revenue cut produces a 16.7% ceiling cut, because the relationship is linear — which is the useful property, and also the dangerous one. Nothing warns you. The campaign keeps spending at the old bid, and the payback period silently stretches by a fifth.
Two caveats, stated plainly. Conversion rates vary enormously by category and market, and the published benchmark sets disagree with each other by a factor of two or more, so the 60% above is a round number for illustration, not a recommendation. And no public dataset breaks out Moroccan Apple Ads cost per tap at all — there is no benchmark for this storefront, from any vendor.
→ FREE 10-POINT AUDIT
Is your bid ceiling built on last quarter’s net revenue?
We rebuild the max-CPT calculation storefront by storefront, using your actual proceeds rather than gross price, and show you where the ceiling has drifted. One hour. Senior strategist. No pitch.
Book my free audit →
06The tax on the other side of the ledger
Tax does not only reduce what you earn. In many jurisdictions it increases what you pay for the media, and Apple is unusually direct about the consequence.
The Apple Ads billing help page states that your purchase of Apple Ads services could be subject to VAT, sales and use tax, GST or consumption tax depending on where your business sits. Then the operative sentence: “Tax will not be accounted for in your campaign budget. You may see any applicable taxes added as a new line on your invoice.”
That is a real gap. Apple’s daily budget behaves as a monthly cap — its glossary says monthly spend will not exceed the daily budget multiplied by 30.4 — and, as we set out in the piece on why campaigns underdeliver, that arithmetic is what most teams plan against. The tax sits outside it. Your invoice can therefore exceed your modelled monthly spend by the local rate, every month, structurally.
Apple’s separate tax obligations page shows how uneven this is. Advertisers in Australia, Brazil, India, New Zealand, the Philippines, South Korea and Taiwan must supply a valid tax identifier. In Cambodia, Indonesia, Ireland, Laos, Malaysia, Nigeria, Singapore, Switzerland and Vietnam, tax applies regardless of registration status. In Canada, Colombia, the United States and a list of European and other countries, it applies only if you fail to provide a valid tax ID. Apple publishes no rates on that page. So an Indonesian advertiser can face both ends at once — a repriced storefront on one side, unmodelled VAT on the media on the other.
07Two news feeds, one business
Here is the structural finding, and it is the reason this article exists.
Apple maintains a news feed for advertisers at ads.apple.com/news. Accessed on September 2, 2026, its most recent item is dated August 21 — the Apple Maps ads announcement. Nothing since. Apple maintains a separate news feed for developers, and in the same window it carried the August 27 tax and price notice, alongside the year’s earlier commission and currency changes.
The two feeds have never cross-referenced each other. The advertiser feed announces bidding strategies, placements and creative formats. The developer feed announces the things that determine whether any of those are worth buying. In most organisations, one person subscribes to each, and they are not the same person.
Aug 21
Most recent Apple Ads news item
Aug 27
Proceeds cut in three countries
Sep 14
Four storefronts repriced
0
Cross-references between the feeds
None of Apple’s bidding systems close the gap either. Manual bids are numbers you typed. A Target CPA in Maximize Conversions is also a number you typed — Apple optimises toward the target you set, weekly, and has no view of what a download is worth to you after tax and commission. Neither does the Platform API, whose reporting endpoints return spend and conversions, never proceeds. The only system that knows both sides of the equation is yours.
08The China precedent, pointed the other way
A tax and a commission are the same instrument with different owners, and 2026 has already run the experiment in the opposite direction.
On March 12, 2026, Apple announced that from March 15 the commission on the China mainland storefront would fall from 30% to 25% for standard In-App Purchase and paid app transactions, and from 15% to 12% for qualifying Small Business Program and Mini Apps Partner Program transactions and for subscription auto-renewals after the first year. Apple attributed the change to “discussions with the Chinese regulator” and committed to rates “no higher than overall rates in other markets.” Notably, it added that signing the updated terms by March 15 was not required to receive the benefit.
Derived: for a standard-terms developer, net revenue per download in China rose from 70% to 75% of the ex-tax base — an increase of about 7.1% — and the bid ceiling rose with it in exactly the same linear way, on a date announced three days in advance and only in the developer feed.
The pattern holds across the year. The EU’s unified business terms take effect October 1, replacing the per-install Core Technology Fee with a 5% Core Technology Commission — what that swap does to install economics, in detail. Bulgaria’s euro adoption dropped Apple’s supported-currency count from 44 to 43. Four instruments — tax, commission, currency, price tier — each moving net revenue per install, none coordinated, none surfaced to advertisers.
09The $1.4 trillion number and what it hides
Apple Newsroom, June 4, 2026, reported that the App Store ecosystem generated $1.4 trillion in billings and sales in 2025, with over 90% going entirely to developers with no Apple commission, across more than 850 million average weekly users in 175 countries and regions. The breakdown: $1.1 trillion in physical goods and services, $149 billion in digital goods and services, $151 billion in in-app advertising. The study was conducted by economists at Analysis Group. That weekly-user figure supersedes the 800 million Apple previously cited, and it is the denominator behind every claim about App Store search intent.
AppleInsider’s same-day analysis raised an objection worth carrying: the total includes digital goods bought outside the App Store, on which Apple earns nothing, and the methodology is vague about which transactions qualify — data sources are given only as “data from Apple, app analytics companies, market research firms, and individual companies.” For an advertiser, the relevant slice is the $149 billion in digital goods, the money that actually passes through the commission and tax machinery described above. That is roughly a tenth of the headline, and the gap between the two numbers is the gap between ecosystem storytelling and the arithmetic that sets your bid.
10What to do before September 14
Four things, in order, none of which require a bid change today. If none of the five countries is a live market for you, file this and move on.
- Check your base storefront and your pricing method. If an affected country is your base storefront, or you manage prices there manually, September 14 does nothing for you and the August 27 cut stands.
- Separate subscription revenue from one-off purchases. Apple has said subscription prices will not change. That exclusion, not the tax rate, is the decisive fact for most serious advertisers.
- Capture a clean pre-change baseline now. Split reporting by storefront before September 14 while the old revenue-per-install series is still uncontaminated. You cannot reconstruct this later, and the same discipline applies to the October 1 European transition.
- Rebuild the ceiling from proceeds, not price. Use what Apple actually pays you, after tax and commission, and remember that the tax on your ad spend sits outside the campaign budget entirely.
11What we still don’t know
Several things in this analysis are genuinely unresolved, and it is better to name them than to paper over them.
Apple publishes no percentage effect on proceeds — every figure of that kind here, including the 16.7%, is arithmetic derived from Apple’s stated order of deductions and should be treated as such. No public Apple Ads benchmark set covers Morocco, Israel or Indonesia, so there is no cost baseline against which to measure whether these changes move auction prices; the datasets that exist are US and global aggregates. Apple has not stated how much the September 14 repricing will actually raise local prices, only that it will happen. There is no published evidence either way on whether developers pass tax changes through to price, or absorb them. And Apple’s help pages carry no publication dates or changelogs, so none of the billing and tax pages cited here can be aged against the 2026 changes.
What is not in doubt is the shape of the thing. Apple sets the rates that determine what an acquired user is worth, publishes them on its own schedule in a feed aimed at engineers, and offers no mechanism anywhere in its advertising stack that notices. The advertisers who keep buying the highest-value iOS users profitably are the ones who read both feeds — and who understand that what Apple reports back to you is a separate question from what a conversion was worth. If you want a second pair of eyes on the arithmetic, our free 10-point audit starts with exactly this calculation.