Native Ads in Mobile Apps

In an app, a native ad is a bundle of assets that the SDK hands over and the developer draws. That gives full design control and a few duties to remember: expiry, clean-up and clear labeling.

Data checked: November 2026

How in-app native differs from the web

On a website, a widget renders the ad for the publisher. In an app, the SDK usually delivers the assets, such as a headline, an icon and an image, and the developer builds the layout. Google’s AdMob documentation puts it plainly: when a native ad loads, the app receives an object containing the assets and is responsible for displaying them. The reward is a unit that matches the app exactly. The cost is design and engineering time.

What a native ad contains

Assets differ by network. AppLovin’s documentation lists a title, body text, an icon, a star rating, an advertiser name, a media view and a call to action, and it requires a privacy information icon. Yandex’s documentation says you render native ads with your own assets. A good layout shows only the assets that the network lets you show, in a consistent order, with an unmistakable ad label.

SDK support at a glance

The table shows what each network’s pages state about native ads in apps. Cells say so when a point is not published.

NetworkNative supportDocumented detailOfficial page
Google AdMobYes, on the product pageUp to five ads per batch, not for mediated units; ads expire after an hour; destroy every adAdMob
Yandex AdsYes, among seven formatsOwn assets; up to nine ads per requestYandex Ads
AppLovin MAXYes, on AndroidDeveloper-built layout; privacy icon required; four-hour expiryAppLovin MAX
Unity LevelPlayYes, among four formatsNot stated on the public pageLevelPlay
AppodealYes, among five formatsNot stated on the public pageAppodeal
Source: official network pages and documentation, checked November 2026 · checked November 2026

Expiry and clean-up

Native ads are not meant to be held indefinitely. Google’s documentation says that ads expire after an hour, so a cache of preloaded ads should be cleared and refilled hourly. AppLovin’s documentation gives a longer window of four hours. Google also tells developers to destroy every native ad, including unused ones, to release resources and avoid memory leaks. If your app shows stale or leaking ads, check these rules first.

Native ads and mediation

Mediation adds a wrinkle. Google’s documentation says that its batch loading method does not work for mediated ad unit IDs, so apps with mediation request ads one at a time. Each network in a mediation stack may also deliver a slightly different asset set, so test the layout against every source before you release. Keep the layout code generic enough to handle a missing asset without breaking.

Labeling and trust

A native ad inside an app should still look like an ad. The FTC’s Native Advertising: A Guide for Businesses says that terms such as “Ad” and “Advertisement” are likely to be understood, advises against “Promoted”, and says a disclosure is most noticeable in front of or above the headline. On a small screen, put the label where a reader’s eye starts, and do not hide it behind an icon.

Layout principles that hold up

A native layout works best when it is predictable. Reserve a fixed slot height so the screen does not jump when the ad arrives. Keep text legible against the app’s background, show the label before the headline, and make the call to action look tappable but not like a core control. Test with long and short headlines, with and without an icon, and in both orientations. A layout that survives these tests will survive most mediated sources too.

When native is the wrong choice

Native units suit feeds, lists and shops, where a card is a normal part of the screen. They suit a full-screen game poorly, where an ad card breaks the experience and rewarded video fits better. They also suit an app with very few content screens poorly, because there is no natural place for a card. Choose the format that fits the screen instead of the format with the most appealing name.

Performance and memory

Native ads add views and images to a screen, so treat them like any other heavy component. Keep ad views light, reuse them where the platform allows, and release their resources when a screen closes. Load ads early enough that they are ready when needed, but not so early that they expire unseen. If a scrolling list stutters after ads are added, the cause is usually layout work or image size, not the network.

Privacy in app native ads

Ad SDKs read device identifiers, so privacy duties apply. If children may use your app, read the FTC’s COPPA FAQ before you choose a network, and check each SDK’s consent and child-directed settings. Document what the SDK collects in your own privacy policy, so users and reviewers can see it.

A checklist before release

  • Is every ad labeled clearly in front of or above the headline?
  • Does the layout handle a missing asset without a blank gap?
  • Are cached ads cleared before they expire?
  • Are ads destroyed when a screen closes?
  • Have you tested each mediated network’s assets in the layout?
  • Does the app-ads.txt file on your developer site list every seller, as the IAB Tech Lab describes?

For the full list of networks, see the directory, and for the standards behind native ads see types of native ads.

Frequently asked questions

Who draws a native ad inside an app?

The developer does. The SDK delivers the assets, and the app lays them out, which is why native units can match an app’s design exactly.

How long can I keep a native ad before showing it?

Not long. Google’s documentation says AdMob ads expire after an hour, and AppLovin’s says four hours. Refresh any cached ads before they expire.

Do native ads need a label in apps?

Yes. The FTC recommends clear terms such as “Ad”, placed in front of or above the headline, and the same logic applies on a phone screen.