AppLovin has stopped allowing app publishers to create new zones for its ad network outside its own MAX mediation, according to Božo Janković, head of ad monetization at GameBiz Consulting, who described the change in a LinkedIn post today. Zones are the configured lines that let AppLovin's demand compete inside a rival mediation platform such as Google AdMob or Unity LevelPlay. Without new ones, publishers that run a mediation waterfall outside MAX are limited to the AppLovin lines they already hold.
Janković wrote that the change arrived "sometime in the past four weeks" and was made "completely quietly, without warning". PPC Land could not find any public announcement from AppLovin about it, and the integration guides that Google and Unity publish for the AppLovin network do not mention it.
In Short
AppLovin no longer lets publishers create new waterfall lines, called zones, for its ad network when they use a mediation platform other than its own MAX, according to a mobile ad monetization consultant. The hardest hit are app and game developers on Unity's LevelPlay, where AppLovin bidding is not offered, so a new LevelPlay publisher has no way to add AppLovin demand, while AdMob users can still reach it through bidding alone. Lines created before the change keep working, but their prices were already locked, which means AppLovin's presence in rival waterfalls is now frozen at whatever publishers set up in the past.
What Janković reported
The post opens with a single-sentence verdict: "AppLovin quietly locks its demand for publishers not using MAX mediation." Its central claim follows. "Sometime in the past four weeks, Applovin stopped allowing publishers to create new zones for Applovin ad network (waterfall lines to be used outside of MAX)," Janković wrote.
The manner of the change drew as much criticism in the post as its substance. "They did this completely quietly, without warning, effectively ensuring publishers cannot prepare for the change (by, for example, creating a lot of zones to have at their disposal for future use)," according to the post. Janković called it "the last step in Applovin limiting how their ad network can be used" by publishers that pick another mediator.
No exact date is given. Read literally, "the past four weeks" puts the change somewhere between about October 19 and November 16, 2026 - a PPC Land calculation from the post's publication date. The post does not say how the change was discovered.
Confirmation from a second, unconnected source arrived in the comments within hours. Faiz Agil Wirawan, a word-game developer, wrote that the next plan had been to add AppLovin to an iOS app. A check of the AppLovin dashboard after reading the post showed, in Wirawan's words, "IT'S TRUE, i can't create new zone". The zones Wirawan already used in an Android waterfall on AdMob still appeared to be working, according to the comment.
Janković, whose firm advises mobile app studios on advertising revenue, restated the point in a reply to another reader. "In general, there's simply no way you can now create new waterfall lines in Applovin, no matter what," Janković wrote.
Who is affected, and how
The post separates publishers outside MAX by the mediator they use. The table records each position as Janković describes it.
| Mediation platform | AppLovin bidding | New AppLovin zones | Result, according to Janković |
|---|---|---|---|
| Unity LevelPlay | Not available | Cannot be created | No route to AppLovin demand for publishers without existing zones |
| Google AdMob | Available | Cannot be created | Bidding only; no hybrid setup built on new AppLovin waterfall lines |
| AppLovin MAX | AppLovin's own platform | Not used | Not affected; the restriction applies outside MAX |
On LevelPlay the language is blunt. "If you are on Unity LevelPlay, you cannot use Applovin ad network AT ALL," Janković wrote. "This is because Applovin bidding is not available on LevelPlay." The capital letters are in the original. Read alongside the post's later passage on existing lines, the statement covers LevelPlay publishers that do not already hold AppLovin zones.
AdMob publishers keep one door open. "If you are on Google AdMob, you cannot use Applovin waterfall lines but you CAN still use Applovin bidding," the post states. "This way, publishers are prevented from using Applovin in a hybrid setup even though AdMob supports this, and even though data shows hybrid setups outperform bidding only setups by 10% to 20%." The post does not say whose data produced that range, which apps or formats it covers, or how the comparison was made.
Publishers already using AppLovin through a third-party waterfall are not cut off. "Publishers who were using Applovin network so far, CAN continue using Applovin by using waterfall lines that already exist in their dashboard (even for new games), but they will not be able to create new lines (for example, to create lines with new prices, based on the data they see)," according to the post.
Two earlier restrictions
Janković presents the latest change as the end of a sequence. The post lists two earlier steps, neither of them dated.
| Earlier restriction | Example given in the post |
|---|---|
| "Stopped allowing any kind of changes on previously created zones" | "you cannot change the eCPM floor price" |
| "Stopped allowing creation of multiple zones with the same price" | "to be used in different apps" |
Taken together, the three steps remove most of the levers a publisher had for managing AppLovin inside another mediator. A waterfall line is usually priced with a price floor, the minimum eCPM the network has to pay to fill an impression at that position. Once floors on existing zones could no longer be edited, the post's own example shows what remained: creating a fresh line at a new price, "based on the data they see". Duplicate prices across zones were already blocked. With new zones now blocked too, the AppLovin price points available to a publisher outside MAX are, on Janković's account, the ones it created before the change, at the floors it set at the time.
How a zone is set up in AdMob and LevelPlay
Google's AdMob integration guide for AppLovin on Android lays out the waterfall setup in four stages:
- Keys. The AppLovin SDK Key and Report Key sit under Account, then Keys, in the AppLovin dashboard. Bidding needs only the SDK Key. The waterfall integration also needs the Report Key, which AdMob uses for ad source optimization, and a Zone ID.
- Zone creation. In the AppLovin dashboard, a publisher selects Create Zone, enters a name for the Zone ID, chooses the platform and ad type, and sets pricing to either Flat CPM or Optimized by AppLovin. This is the step that, according to Janković, can no longer be completed.
- One zone per ad unit. Google recommends creating an AppLovin zone for each AdMob ad unit.
- Formats. The guide lists app open, banner, interstitial, rewarded and native formats. It states that AppLovin bidding does not support banner ads, and that the waterfall supports only 320x50 and 728x90 banners.
Unity's documentation describes a parallel structure for LevelPlay. Its AppLovin integration guides for Android and iOS tell publishers to create one instance for each ad format - interstitial, rewarded and banner - using the account's SDK Key and Report Key. Unity's API reference for LevelPlay network configuration lists the AppLovin sdkKey at app level and a zoneID field at instance level. The same reference carries a separate entry for ironSource Bidding but none for AppLovin bidding, consistent with Janković's statement that AppLovin's bidder is not offered on LevelPlay.
| Documentation point | Google AdMob guide | Unity LevelPlay guides |
|---|---|---|
| Integration types listed for AppLovin | Bidding and waterfall; waterfall marked as closed beta | Instances per ad format; no AppLovin bidding entry |
| Credentials | SDK Key (bidding); SDK Key, Report Key and Zone ID (waterfall) | SDK Key and Report Key; zoneID at instance level |
| Banners | Not supported by bidding; waterfall supports 320x50 and 728x90 | Banner listed as an instance format |
| Mention of the zone restriction | None | None |
Two details in Google's guide bear directly on the change. The guide marks the AppLovin waterfall integration on AdMob as being in closed beta, without saying since when. And because AppLovin bidding on AdMob does not serve banners, AppLovin banner demand inside AdMob runs through waterfall zones. On that reading, an AdMob publisher with no existing AppLovin banner zone now has no route to that demand. Neither Google nor AppLovin has addressed the point publicly.
The case for the change, and the objection
Not every reader saw the move as hostile. Dom Davies, who works in mobile gaming ad tech on the publisher and user acquisition side, called it commercially rational. "From a business standpoint, it actually makes a lot of sense. The bidder allows the opportunity to buy any impression. Line items pinhole you to 1 price point, which for performance buyers is no good. Limited data, no auction signal," Davies wrote.
That argument follows a long-running shift. A waterfall calls networks one at a time, ranked by historical or assigned eCPM rather than by what any of them would pay for the impression in front of it; bidding asks every source at once. On the web, the same transition ran through header bidding, which offers an impression to several exchanges at the same time before the ad server decides. Google Ads stopped sending multicall waterfall requests on October 31, 2023, and Display & Video 360 followed on October 23, 2024. AdMob still runs a hybrid model in which the winning bid is placed into the waterfall at its price, a design that lets fixed-price lines compete with live bids and one that has drawn criticism for exactly that reason.
Janković did not dispute the direction, only the order of events. "I think the sensible first step would be first allow their bidder inside LevelPlay, and then sunset the waterfall lines," Janković replied to Davies. A reply to another reader said the change "further limits the options publishers have. Especially since Applovin bidding is not available in LevelPlay."
Asked by Harry Phokou, founder of Hivemind Marketing, whether AppLovin simply wanted publishers to move to MAX, Janković offered an inference rather than evidence. "I assume this is one more push from Applovin to 'encourage' publishers to use MAX instead of alternative mediation solutions," Janković wrote. The quotation marks around "encourage" are in the original.
MAX, LevelPlay and a dispute already in court
AppLovin sits on both sides of the mobile ad market. MAX runs auctions for app publishers; AppLovin Ads, built on the company's Axon models, buys impressions for advertisers. In May, AppLovin said it would open the Axon platform to all advertisers in June. Unity's LevelPlay and Google's AdMob are the best-known rival mediators.
The money is on the demand side. AppLovin sold its mobile games business to Tripledot Studios in a deal that closed on June 30, 2025. It reported third-quarter revenue of $2.18bn, up 55%, and its quarterly filing describes AppLovin Ads as generating substantially all revenue. MAX revenue is not reported separately. On the November 4 earnings call, chief executive Adam Foroughi said the MAX market was growing at a strong double-digit rate every year, and that AppLovin's own models see only whether they won an auction and the winning and losing prices. In February, Foroughi defended the company's business model in a post stating that MAX reaches more than one billion daily active users.
The relationship with Unity is already in litigation. In late September, AppLovin went to court to stop Unity collecting data through its Ad Quality SDK, a tool bundled into LevelPlay from SDK version 8.9.0 on May 28, 2025. AppLovin alleged that the SDK read data on impressions AppLovin won, including creatives, per-impression revenue, MAX ad unit data and waterfall information. Unity said in a letter that Ad Quality does not collect any data from AppLovin. The petition was filed in San Francisco Superior Court on September 28, 2026. Janković's post does not connect the zone change with that dispute, and no public material links the two.
Google, for its part, has been widening the bidding side of AdMob. In July 2025 it added InMobi, ironSource and Unity as AdMob bidding partners and introduced bidding eCPM floors at mediation-group level. AppLovin was not among the partners named in that update.
Why it matters
For app publishers, the choice of mediator now carries a consequence that is easy to miss at setup. A studio that builds on LevelPlay or AdMob today gets less access to AppLovin demand than one that built the same stack before the change, and a studio on MAX gets all of it. Janković's closing line is addressed to that group: "So, if you are a new publisher or you are new to ad monetization, and you are considering your mediation options, there is now one more factor to be taken into account."
For advertisers buying through AppLovin, the change is about where auctions happen rather than what impressions cost. Inventory in apps mediated elsewhere reaches AppLovin's demand only through bidding, where a mediator offers it, or through legacy zones at fixed prices. Every publisher that moves to MAX to regain full access shifts more auctions onto AppLovin's own platform. Whether that happens at scale is not something the post, or any public AppLovin statement, can yet show.
The timing drew comment too. "really? at this Q4?? why," wrote Wirawan, whose plan to add AppLovin to an iOS app ran into the change in the final quarter of the year.
What remains unclear
AppLovin has not said that it made the change, when it took effect or why. The post does not date the two earlier restrictions, does not identify the source of the 10% to 20% figure for hybrid setups and does not cover mediators other than AdMob and LevelPlay. It is also unknown whether existing zones will keep serving indefinitely, and whether AppLovin intends to offer bidding inside LevelPlay.
Key facts
- Source: LinkedIn post by Božo Janković, Head of Ad Monetization, GameBiz Consulting, published November 16, 2026, opening "AppLovin quietly locks its demand for publishers not using MAX mediation. Here's what happened." URL: https://www.linkedin.com/posts/bozoj_admonetization-monetization-adnetworks-share-7528039488124579840-OP9p/
- Change reported: new AppLovin zones ("waterfall lines to be used outside of MAX") can no longer be created
- Timing: "Sometime in the past four weeks" before November 16, 2026, which is from about October 19, 2026 (PPC Land calculation)
- Platforms named: Unity LevelPlay (AppLovin bidding not available), Google AdMob (AppLovin bidding available)
- Existing zones: still usable, including in new games; cannot be edited, including the eCPM floor price
- Earlier restrictions (undated): no changes to existing zones; no multiple zones at the same price
- Unsourced figure: hybrid setups outperform bidding-only setups by 10% to 20%, according to the post, with no data source given
- Independent confirmation: a developer commenting on the post reported being unable to create a new zone
- AppLovin statement: none published
- Documentation: Google AdMob "Integrate AppLovin with mediation" (Android): bidding and waterfall listed, waterfall in closed beta, bidding does not support banners. Unity LevelPlay "AppLovin integration" guides (Android, iOS) and LevelPlay API "Naming and configurations": AppLovin
sdkKeyandzoneID - Products: AppLovin MAX (mediation), AppLovin Ads and Axon (demand), Unity LevelPlay (mediation), Google AdMob (mediation)
- Related case: AppLovin petition against Unity over the Ad Quality SDK, San Francisco Superior Court, case CPF-26-520212, filed September 28, 2026
Timeline
- May 28, 2025 - Unity bundles its Ad Quality SDK into LevelPlay SDK version 8.9.0
- June 30, 2025 - AppLovin completes the sale of its mobile games business to Tripledot Studios
- July 2025 - Google adds InMobi, ironSource and Unity as AdMob bidding partners and introduces bidding eCPM floors at mediation-group level
- February 2, 2026 - AppLovin chief executive Adam Foroughi defends the business model and says MAX reaches more than one billion daily active users
- May 2026 - AppLovin says the Axon platform will open to all advertisers in June
- September 28, 2026 - AppLovin petitions San Francisco Superior Court over Unity's Ad Quality data collection
- Undated, before the latest change - AppLovin stops edits to existing zones, including eCPM floors, and stops the creation of multiple zones at the same price, according to Janković
- About October 19 to November 16, 2026 - AppLovin stops allowing new zones for use outside MAX, according to Janković ("sometime in the past four weeks")
- November 4, 2026 - AppLovin reports third-quarter revenue of $2.18bn, up 55%; Foroughi says the MAX market grows at a strong double-digit rate
- November 16, 2026 - Janković publishes the account on LinkedIn; a developer in the comments reports being unable to create a new zone
Related PPC Land coverage
- AppLovin revenue gains 55% to $2.18bn as new ad models lift gaming - The third-quarter results, the 10-Q's segment description covering MAX, and Foroughi's remarks on MAX growth and auction data.
- AppLovin sues Unity to halt Ad Quality data collection within 5 business days - The September 2026 dispute over what Unity's LevelPlay-bundled SDK collects about AppLovin's winning impressions.
- AppLovin CEO defends business model as transparency questions mount - Foroughi's February 2026 defence of the platform, including MAX's reach of more than one billion daily users.
- AppLovin's $1.84B Q1 beats guidance as Axon platform opens to all in June - First-quarter 2026 results and the plan to open Axon to all advertisers.
- AppLovin revenue growth slows to 53% as Q3 margin guidance drops to 83% - Second-quarter 2026 results and the guidance that preceded the third quarter.
- Google launches major AdMob mediation updates with new bidding partners - The July 2025 AdMob changes that added bidding partners and group-level bidding floors.
- AppLovin reports 77% revenue growth in second quarter 2025 - The quarter in which AppLovin closed the sale of its games business to Tripledot Studios.
- AppLovin faces data collection controversy amid market scrutiny - The March 2025 short-seller allegations about AppLovin's data practices and the company's response.
Summary
Who: AppLovin, the mobile advertising company that runs the MAX mediation platform and the AppLovin Ads demand business; publishers using Unity LevelPlay and Google AdMob; and Božo Janković, head of ad monetization at GameBiz Consulting, who reported the change, with a developer confirming it in the comments.
What: AppLovin no longer allows publishers to create new zones, the waterfall lines used to call its ad network from outside MAX. New LevelPlay publishers cannot add AppLovin at all because its bidder is not offered there, AdMob publishers can still use AppLovin bidding but not new waterfall lines, and existing zones keep working at floors that could already not be changed.
When: The change took place "sometime in the past four weeks", according to Janković's post published today, November 16, 2026. Two earlier restrictions on editing and duplicating zones are undated.
Where: In the AppLovin publisher dashboard, affecting app publishers that mediate through Unity LevelPlay, Google AdMob or other platforms outside MAX.
Why: AppLovin has given no reason. Janković assumes it is a push to "encourage" publishers to use MAX; a commenter argued that bidding gives buyers more data and flexibility than fixed-price lines. The change matters because it ties full access to AppLovin's demand to the use of AppLovin's own mediation platform.
Discussion