AppLovin's halt on new waterfall zones for its ad network outside MAX also applies to Google Ad Manager, according to Kean Graham, founder and chief executive of the publisher monetization firm MonetizeMore, who set out the change in a LinkedIn post on November 19, 2026. Existing AppLovin lines in Ad Manager keep serving, Graham wrote, "but the floors are frozen, so no new price points." The post puts Ad Manager alongside Unity LevelPlay and Google AdMob, the two mediation platforms named when the restriction was first reported on November 16.
The post also settled one open question from that first report and opened another. A 10% to 20% advantage for hybrid setups over bidding-only setups, which appeared without a source in the earlier account, is MonetizeMore's own average, Graham wrote in a reply. A business development analyst at AppLovin challenged the figure in the same thread, writing that AppLovin's side "doesn't show the uplift mentioned, especially not on gaming."
In Short
A second industry figure says AppLovin has stopped letting app publishers create new waterfall lines for its ad network outside its own MAX platform, and adds Google Ad Manager to the list of affected tools. App developers who sell ads through Ad Manager, AdMob or Unity's LevelPlay are left with whatever AppLovin lines they set up before the change, at prices they can no longer adjust. The often-cited claim that mixed setups earn 10% to 20% more turns out to come from one vendor's own client data, and an AppLovin employee disputes it in public, so the cost of the change for publishers is still an open question.
What Graham's post adds
Graham opened with an address to "ad monetized mobile app publishers" and a verdict: "AppLovin just changed the rules on you...quietly." The description of the change matches the November 16 account by Božo Janković of GameBiz Consulting. "AppLovin recently stopped letting publishers create new zones for its ad network outside MAX. Zones are the waterfall lines you price AppLovin demand with. No announcement. No warning," the post states. "Existing zones keep running but you can't add new price points based on what your own data tells you."
No date is given beyond "recently". Janković had placed the change "sometime in the past four weeks" before November 16. PPC Land has found no public statement from AppLovin on the restriction in either period.
Graham's post goes further on two points. It names Google Ad Manager, which Janković did not mention, and it states that AppLovin's bidder on AdMob "doesn't support banners" - a limit that Google's own integration documentation confirms. The post is illustrated with a cartoon: a figure in a "Publisher" shirt stands beside a figure in a Google Ad Exchange shirt holding out coins, while characters wearing the Unity, Google AdMob and Google Ad Manager logos wait behind a velvet rope outside a vault marked "AppLovin MAX", guarded by a bouncer. By November 22 the post had drawn 98 reactions, 15 comments and five reposts.
Platform by platform
The two accounts differ mainly in coverage. The table sets out each platform's position as described by Graham on November 19 and by Janković on November 16.
| Mediation platform | Graham, November 19 | Janković, November 16 |
|---|---|---|
| Unity LevelPlay | "No AppLovin waterfall lines and no AppLovin bidding there either. Zero access unless you already have legacy zones." | AppLovin network unavailable "AT ALL" because AppLovin bidding is not offered on LevelPlay; existing zones still usable |
| Google AdMob | "Bidding still works, but hybrid setups are dead and AppLovin bidding doesn't support banners." | AppLovin bidding available; no new waterfall lines, so no hybrid setup built on them |
| Google Ad Manager | "Same treatment as AdMob. Existing lines keep serving but the floors are frozen, so no new price points." | Not mentioned |
| Existing zones | Keep running; no new price points | Keep working, "even for new games"; floors on existing zones already could not be edited |
| Hybrid uplift | "Hybrid setups typically beat bidding-only by 10-20%" | "Data shows hybrid setups outperform bidding only setups by 10% to 20%" |
A hybrid setup lets bidders and fixed-price lines compete for the same impression. In a mediation waterfall, each fixed line carries a price floor, the minimum the network must pay to fill at that position. Graham's phrase "hybrid setups are dead" refers to hybrid setups that include AppLovin: without new zones, AppLovin can take part in an AdMob or Ad Manager auction only as a bidder or through the lines a publisher already holds.
Where the 10-20% figure comes from
The most prominent reply under the post was a one-word question. Nathan Sadeh, whose LinkedIn headline reads "Senior Analyst, Business Development @ AppLovin", quoted the hybrid claim and asked: "source?"
"MonetizeMore. This is what we've seen on average across mobile app pubs with different setups. What have you seen?" Graham replied. In a separate reply to Kirill Shulman, who asked whether the uplift still held when AppLovin demand was limited to legacy zones or MAX, Graham narrowed the claim. "The 10-20% was hybrid vs bidding-only across the stack, not an AppLovin specific number. But you're right that the lockout changes what hybrid means now," the reply states.
Neither reply gives the number of apps, the period, the ad formats or the method behind the average. Janković's post used the same range but did not name a source, so whether the two figures share an origin is not known.
Sadeh rejected the figure on the basis of tests in which apps moved from MAX to other mediators. "We've beat many hybrid setups recommended by Admob when transition apps from MAX to Admob or other mediation for tests. If this was overperforming, not entirely sure most results would be negative," Sadeh wrote, adding that "there are other parameters to account for in a test but still. Doubting this is true."
Graham answered that those were not like-for-like comparisons. "What you ran were migration tests. MAX to AdMob mediation swaps the whole auction, the floors and the learning," the reply begins. Sadeh did not accept the point. "Transition tests across the industry happened on all sizes of publishers for months. So the argument of learning phase doesn't hold," Sadeh wrote. "But ultimately, after a learning phase of about 2 weeks, you end up with full bidding stacks for the most part that win over hybrid stacks in the long run. It's a product decision to go full bidding or hybrid. On our side, it doesn't show the uplift mentioned, especially not on gaming."
Sadeh's comments were made in a personal capacity on LinkedIn and are not an AppLovin statement. They are the only remarks in the thread from someone identifying as an AppLovin employee, and they offer no figures either. Neither side has published the test data it describes.
Seemab Haider, a monetization analytics manager who describes leading monetization across 24 studios, wrote that "diversification makes sense, but publishers also need to keep comparing actual ARPDAU and eCPM performance rather than migrating based on platform promises alone." Another commenter, Zulmonan Masroor of Mobify, suggested TopOn's hybrid mediation as an alternative; Graham asked how it compared with AppLovin.
What Google's Ad Manager guide says
Google publishes a separate AppLovin integration guide for Ad Manager. The Android version, which sits under the legacy Mobile Ads SDK documentation and notes that the "Google Mobile Ads SDK is in maintenance mode", describes the integration in four points:
- Integration types. The guide lists both bidding and waterfall for AppLovin, and states: "Waterfall integration is in closed beta." It does not say since when.
- Formats. App open, banner, interstitial, rewarded and native formats are listed.
- Banners. "Waterfall supports only 320x50 and 728x90 banner sizes. Bidding doesn't support banner ads."
- Zones. "We highly recommend that you create an AppLovin zone corresponding to each Ad Manager ad unit," the guide states, so that Ad Manager can optimize the ad source.
The guide makes no reference to the restriction Graham describes. Read together with the post, it means an Ad Manager publisher that never created an AppLovin banner zone has no route to AppLovin banner demand through Ad Manager, because the bidder does not serve banners and new zones cannot be created. That is a PPC Land reading of the two sources; neither Google nor AppLovin has addressed it. The same pattern applied to AdMob in the November 16 report.
A pitch inside the warning
Graham's post is not a neutral briefing. Its second half argues against moving everything to MAX - "The obvious take is migrate everything to MAX. The better take is don't let one demand source hold your ad revenue hostage" - and recommends a route that MonetizeMore sells.
"Google Ad Exchange (AdX) demand through Google Ad Manager (GAM) adds incremental premium demand that competes in real time in GAM's unified auction, lifting average revenue per daily active user (ARPDAU)," the post states. "MonetizeMore's price floor optimization tech further increases ARPDAU by driving up advertiser CPMs." It closes with a question: "All-in on MAX or build diversified ARPDAU that no single platform can switch off?" The post gives no figures for either claim. The banner on Graham's LinkedIn profile displays a Google Certified Publishing Partner badge.
Graham has led MonetizeMore since January 2010, according to Graham's LinkedIn profile. In October, Graham used a webinar for Indonesian publishers to warn that invalid traffic enforcement can erase unpaid Google revenue and to promote the company's Traffic Cop tool.
Why it matters
The dispute over the hybrid figure is central to what publishers outside MAX lose. If hybrid setups beat bidding alone by a meaningful margin, freezing AppLovin's waterfall presence costs those publishers money and makes MAX, where AppLovin's demand is fully available, more attractive. If full real-time bidding stacks catch up after a short learning phase, as Sadeh argues, the cost is smaller and the change looks more like the industry's long move away from waterfalls.
That move has been under way for years. AppLovin joined AdMob Open Bidding in December 2018. Google Ads began moving away from multicall waterfall requests in apps in October 2023, with the aim of completing the transition in early 2024, and Display & Video 360 stopped bidding on multiple waterfall calls on October 23, 2024.
AppLovin's own weight in the market has grown in the meantime. The company reported third-quarter revenue of $2.18bn, up 55%, on November 4, and its relationship with Unity, owner of LevelPlay, is already the subject of a court dispute over Unity's Ad Quality SDK. Graham's post does not connect the zone change with that case.
What remains unclear
AppLovin has not confirmed the change, dated it or explained it. Graham's Ad Manager claim has not been independently confirmed, and the post does not cover mediators beyond LevelPlay, AdMob and Ad Manager. The 10-20% average has no published sample or method, and the migration tests Sadeh cites have no published results.
Key facts
- Source: LinkedIn post by Kean Graham, Founder & CEO of MonetizeMore, published November 19, 2026 and marked as edited, opening "Calling all ad monetized mobile app publishers! AppLovin just changed the rules on you...quietly." URL: https://www.linkedin.com/posts/monetizemore_calling-all-ad-monetized-mobile-app-publishers-share-7529114260329705472-SgQc/
- Engagement as of November 22, 2026: 98 reactions, 15 comments, five reposts
- Change described: publishers can no longer create new AppLovin zones for use outside MAX; existing zones keep serving without new price points
- Platforms named: Unity LevelPlay (no AppLovin bidding, no new zones), Google AdMob (bidding only, no banners via bidding), Google Ad Manager (same as AdMob, floors frozen)
- Hybrid figure: "Hybrid setups typically beat bidding-only by 10-20%"; source given in a reply as MonetizeMore's average "across mobile app pubs with different setups", "not an AppLovin specific number"
- Dissent: Nathan Sadeh, LinkedIn headline "Senior Analyst, Business Development @ AppLovin", in personal comments: full bidding stacks win over hybrid after "a learning phase of about 2 weeks"; no published data
- AppLovin statement: none found
- Earlier report: Božo Janković, GameBiz Consulting, LinkedIn post of November 16, 2026
- Documentation: Google "Integrate AppLovin with Mediation | Mobile Ads SDK (Legacy) for Android" (Ad Manager): bidding and waterfall listed, "Waterfall integration is in closed beta", "Bidding doesn't support banner ads", waterfall banners 320x50 and 728x90 only
- Products: AppLovin MAX, Unity LevelPlay, Google AdMob, Google Ad Manager, Google Ad Exchange (AdX)
Timeline
- December 16, 2018 - AppLovin, Facebook Audience Network and Rubicon Project enroll in AdMob Open Bidding
- October 31, 2023 - Google Ads moves away from multicall waterfall requests in apps, aiming to complete the transition in early 2024
- October 23, 2024 - Display & Video 360 stops bidding on multiple waterfall calls for mobile apps
- September 28, 2026 - AppLovin goes to court to stop Unity's Ad Quality SDK collecting data on its impressions
- October 8, 2026 - MonetizeMore publishes a webinar in which Graham warns publishers about invalid traffic and Google revenue
- About October 19 to November 16, 2026 - AppLovin stops allowing new zones for use outside MAX, according to Janković
- November 4, 2026 - AppLovin reports third-quarter revenue of $2.18bn, up 55%
- November 16, 2026 - Janković reports the change on LinkedIn, citing a 10% to 20% hybrid advantage without a source
- November 19, 2026 - Graham's post adds Google Ad Manager to the affected platforms and repeats the 10-20% figure
- November 20-21, 2026 - Graham names MonetizeMore's own data as the figure's source; AppLovin analyst Nathan Sadeh disputes it in the comments
Related PPC Land coverage
- AppLovin blocks new waterfall lines for apps on rival mediation - The first report of the zone restriction, with the LevelPlay and AdMob setup documentation.
- Google to test Gemini agent that flags AdMob setup errors - Google's AdMob AI tools, published the same day as the first zone report and noting it.
- Invalid traffic can wipe out unpaid Google ad revenue, MonetizeMore warns - Graham's October webinar for Indonesian publishers and the claims made for Traffic Cop.
- AppLovin revenue gains 55% to $2.18bn as new ad models lift gaming - AppLovin's third-quarter 2026 results and remarks on the MAX market.
- AppLovin sues Unity to halt Ad Quality data collection within 5 business days - The dispute over what Unity's LevelPlay-bundled SDK collects about AppLovin's impressions.
- DV360 to stop bidding on multiple waterfall calls for mobile apps - Google's October 2024 cut-off for DV360 multicall waterfall bidding in apps.
- Google Ads to complete transition to RTB for Apps as early as January 2024 - The earlier Google Ads move from waterfall calls to real-time bidding for app inventory.
- Magnite gains bidder seat in CloudX mobile app auctions - Another October 2026 change in who bids for in-app inventory.
- Facebook Audience Network, AppLovin, and Rubicon Project enroll in AdMob Open Bidding - AppLovin's 2018 entry into bidding on AdMob.
Summary
Who: Kean Graham, founder and chief executive of MonetizeMore, who described the change; AppLovin, which runs the MAX mediation platform and an ad network; app publishers using Google Ad Manager, Google AdMob and Unity LevelPlay; and Nathan Sadeh, an AppLovin business development analyst who disputed Graham's figures in a personal capacity.
What: Graham's post states that AppLovin no longer lets publishers create new zones for its network outside MAX, and that Google Ad Manager publishers, like AdMob users, keep existing AppLovin lines at frozen floors. The 10-20% hybrid advantage cited in both public accounts of the change is, according to Graham, MonetizeMore's own average, a figure Sadeh says AppLovin's tests do not support.
When: The post was published on November 19, 2026, three days after the restriction was first reported on November 16. The comment exchange took place on November 20 and 21. AppLovin has not dated the change.
Where: On LinkedIn, concerning the AppLovin publisher dashboard and in-app mediation through Google Ad Manager, Google AdMob and Unity LevelPlay.
Why: AppLovin has given no reason. Graham presents the change as a reason to diversify demand through Google Ad Exchange and MonetizeMore's floor tools, a service the company sells; Sadeh describes the choice between full bidding and hybrid as a product decision. The size of the hybrid advantage determines how much publishers outside MAX lose, and no one has published data to settle it.
Discussion