Rendered like content, labeled as advertising.
A customizable unit whose components, headline, image, icon and call to action, are rendered by the app to match its own design. The unit adapts to the product; the label keeps it honest.
Illustrative placement
What it is.
A native ad is a customizable unit whose components are rendered to match the app's own design. The app controls layout, fonts and which assets appear, and renders the unit inside its feeds, listing screens or launch surfaces. One rule does not flex: the unit must remain identifiable as advertising.
Native works because it avoids pattern interruption: a unit rendered in the visual language of the feed gets read as part of the feed. Whether that converts better than a banner in the same slot is a question your own A/B cohorts answer better than any vendor page.
The mechanics, in order.
Assets requested with the bid
The bid response carries structured assets, headline, image, icon, call to action, instead of a fixed creative size, so your rendering code can lay them out natively.
App renders the template
Your template positions the assets using your fonts, spacing and card design. The unit inherits the visual grammar of the feed because it is genuinely rendered inside it.
Label applied in your typography
The sponsored label renders in the same style as the rest of the card, readable but consistent. Labeling is policy, and your typography does not exempt it.
Interaction reported back
Impressions, visible-asset events and clicks report through the SDK like any other format, so native revenue sits in the same reporting as everything else.
Where this format belongs.
Content feeds
The classic position: a card inside the feed, in the feed typography, with the sponsored label in place.
Listing screens
Search results and category listings, where a well-rendered native unit answers the same visual grammar as the results around it.
Launch surfaces
Home and start screens, where a single unit carries the session without competing with navigation.
The numbers that ship.
Assets, ratios and size limits, per template
Asset types, image ratios and size limits per native template are documented with the template list in the docs, so your rendering code is written against the assets buyers actually send.
The rules this format is held to.
Labeling is policy: every native unit must be visibly identifiable as advertising, using a label such as Sponsored, in the app's own typography but not in camouflage. Disguised units, ads that mimic system dialogs, or unlabeled placements are violations under the publisher policy.
What each number tells you.
Engagement
Interaction relative to banners in the same placement. This is the honest comparison for native: same spot, different rendering.
Fill by feed position
Where in the feed the unit serves affects both viewability and engagement. Read fill and engagement by position before locking the template slot.
Rendering defects
Track template errors, missing assets, mis-sized images, as their own line. A broken template quietly starves a placement of demand that never gets to bid well.
Your design, with demand inside it.
Share a screen of your feed and onboarding will map the native template to it before you write a line of rendering code.
Layout control · labeled · feed-grade