Ad Review update: aggregate-level data

Ad Review helps publishers review the ad content shown in their apps. We’ve updated Ad Review to operate on aggregate-level data only. This page explains what changed and what it means for you.

How Ad Review Works

Ad Review runs only on impressions AppLovin’s MAX mediates, and only after you enable Ad Review. Ad Review uses that data to moderate ads—to find and flag low-quality, deceptive, or non-compliant content, and then aggregates that data for reporting. We do not build user or device profiles from it, and we do not use it to train Axon or any other AppLovin model.

What changed

• We removed the user journey feature and the user- and device-level identifiers that feature required.
• Ad Review now collects and reports ad-moderation data at the aggregate level only—by network, ad unit, and creative.
• The user-level ad journey views are no longer available. You’ll see aggregate reporting instead.

The standard behind it

The data an ad generates belongs to the network that served it and the user who saw it, and it should be collected to review ad content and nothing else. We’re holding Ad Review to that standard. Read the full post: Ad quality tools should catch bad ads, not collect other networks' user-level data.

What you need to do

Update to the latest Ad Review SDK: iOS and Android. No other action is required.

Common questions

• Why did the user-level ad journey views go away?
  • Ad Review still detects and flags non-compliant ads through aggregate reporting. We removed the persistent user-level ad journey views. The Creative Debugger remains available.
• Does this affect ads from other networks?
  • Ad review features still report impressions from all eligible networks at the aggregate level, only user-level ad journey impressions views are no longer available.
• Does this affect the Creative Debugger?
  • No. The Creative Debugger remains available.

For more, see our Ad Review pages.