At a glance
| Field | Detail |
|---|---|
| What | PPC Land reports that publishers cannot create new AppLovin waterfall zones outside MAX. |
| Who | App publishers using other mediation platforms and advertisers reviewing AppLovin inventory access. |
| Where | Mediation outside MAX, including Unity LevelPlay. Markets: Not specified in the supplied source. |
| When | Report published November 16, 2026. Exact effective date: Not specified in the supplied source. |
| Action | Check which inventory access assumptions depend on existing waterfall zones. |
What the report establishes
AppLovin waterfall zones can no longer be created for mediation outside MAX, according to PPC Land's report citing Božo Janković, head of ad monetization at GameBiz Consulting. Zones are the configured lines through which AppLovin demand participates in another platform's mediation waterfall. The reported restriction concerns publishers' ability to establish those lines.
According to Janković's account, existing zones continue to work, including for new games. He also described earlier restrictions that prevented changes to existing zones, including their floor prices. Together, these reported limits leave publishers dependent on previously configured lines and prices when using waterfall access outside MAX.
For an app advertiser reviewing supply coverage, a working legacy integration therefore needs a different review from a proposed integration that requires fresh zones.
Scope and confirmation limits
PPC Land reports that AppLovin bidding is unavailable on Unity LevelPlay. Publishers using that platform without existing AppLovin zones would consequently lack the access route described in the report. Existing LevelPlay publishers with usable zones have a different starting position.
PPC Land found no public AppLovin announcement about the restriction. The supplied report does not establish an exact effective date, market list or the number of affected publishers. It also does not show whether publishers will move to MAX at scale. Any effect on app acquisition costs or campaign performance remains unquantified in the supplied source.
What to review
- Check whether planned supply access depends on new zones, existing waterfall lines or an available bidding integration.
- Separate Unity LevelPlay integrations with legacy AppLovin zones from proposed integrations that have none.
- Request confirmation of current integration options before revising inventory coverage assumptions.
Use a buying-channel map to record these dependencies. Keep any proposed budget adjustment tied to campaign evidence, since the report supplies no acquisition-performance comparison.



