Table of Contents
Overview
The Native App Promo Icon creative promotes app installs, and is only available for custom exclusive supply use cases. It is not supported by any of our publicly available inventory sources.
How it Works
Required assets include: Title, Description, and Mobile App Icon (must be 1:1 and at least 256 x 256).
The following fields are available:
| Creative Fields | Description |
| Creative Name | Name of the creative |
| Active | Whether the creative is active or inactive. Active Line Items must have at least one active creative associated to them. |
| Secure | Whether the creative is secure or not. For a creative to be secure, all URL calls from the creative need to be over HTTPS |
| Alternative ID | Alternative ID for the creative. Use this field to map an creative ID in Beeswax to a creative ID in your system. |
| Advertiser | Advertiser under which you are creating this creative. Creatives can be assigned to any line item beneath this advertiser only. |
| Advertiser Domain | The domain of the advertiser. For example if the advertiser is Ford Motor Company, the advertiser domain would be www.ford.com |
| Advertiser Category | The category of the advertiser. For example if the advertiser is Ford Motor Company, the advertiser category would be “Automotive”. If you leave this field blank it will inherit the advertiser category you set when you created the Advertiser object. NOTE: Advertiser category is a required field for certain exchanges like MoPub. Lack of an advertiser category will result in you not bidding on MoPub. |
| Native Offer | Object that contains many assets for the native creative, such as logo, title, description, icons, etc. The full description can be found here. Native offers and native creatives are a one to many association. |
| Click URL | The Click URL triggered when someone clicks on your creative. |
| Technical Vendor | Not required for this format. |
| Landing Page URL | Not required for this format. |