Mobile apps and websites use the elements you provide to render a native ad. Video ads require a video field.
Required and recommended display and video ads
| Field | Description | Always included? | Required to be displayed? | May truncate after * |
|---|---|---|---|---|
| Headline | Primary headline text (for example, app title). | Yes | Required | 25 characters |
| Image | Large, primary image. | One of image or video will always be included |
Yes, if provided |
NA |
| Video | The video VAST response containing all necessary assets to play back a video ad. | One of image or video will always be included | Yes, if provided | NA |
| Body | Secondary body text (for example, app description). | No | Recommended | 90 characters |
| App icon | Small app store image. | No | Recommended | NA |
| Call to action | Button or text field that encourages user to take action (for example, Install). | No | Recommended | 15 characters |
| Star rating | Rating from 0-5 that represents the average rating of the app in a store. | No | Recommended | NA |
| Store | The app store where the user downloads the app. | No | Recommended | 15 characters |
| Price | Cost of the app. | No | Recommended | 15 characters |
See examples of native ads
* "May truncate after" means that text assets which exceed the specified text limit may be truncated by Authorized Buyers or the publisher, provided that the truncated text limit will be no less than the stated value. For example, a "May truncate after" value of 25 for headlines indicates that Authorized Buyers or publishers may truncate the text to the stated value (or longer) in this column and add '...' or another text treatment to indicate when a value has been truncated.
Learn more about the creative specifications of native ads for Authorized Buyers, or for detailed developer documentation, see the Authorized Buyers Real-Time Bidding (RTB) Protocol.