Native ads adopt the look and feel of the surrounding editorial content. They are considered more acceptable ads since they are presented to the end user in a less intrusive way.
Visit the gallery here to see a demo.
Preparing the app for RTB+ native ad support
To serve native ads in iOS or Android apps, the app developer needs to:
About native ad design
Native ads are composed as follows:
- the app developer designs the native ad's layout/style and chooses which components to use (title, icon, etc.)
- when opened by the end user, the app calls the ad server which serves the native ad's content in json format (title text, body text, URL of the icon etc.)
- the native ad is displayed with the served content based on the app developer's design
Smart AdServer's SDK provides the framework but the actual design and the chosen components are defined by the app developer.
Script template "RTB+ SDK In-Feed Native Ad"
- Create a Mobile RTB+ insertion as described here; make sure you select the insertion type Mobile; enable the checkbox "Activate "Holistic yield" mode..."
- On the Creatives Tab, open the Template library and select the script template "RTB+ SDK In-Feed Native Ad".
Script template parameters
|Data max length
||the maximum amount of characters for „Data“; enable "Use data“ - see below;
maximum: 100 characters
|Third party pixels URLs
||specifies third party impression counting URLs (in case of multiple URLs, separate them by a comma)
|Enable viewability tracking
||allows for tracking of viewable impressions
|Viewability exposure duration (s)
||specifies the duration an ad must be displayed before being counted as viewable; "Enable viewability tracking“ must be enabled
|Viewability exposure percentage of area (%)
||the percentage of the ad's full size which must be visible to be considered as viewable; "Enable viewability tracking" must be enabled
||specifies if the native ad has a title
||specifies if the native ad has an icon
||the "data" field is used for miscellaneous elements of the native ad (e. g. brand name, ratings, descriptions etc.); see above: "Data max length“
||the layout of the environment where the native ad is displayed; to be deprecated: not recommended in case of new implementations
||specifies the ad unit as specified in the IAB native advertising playbook; to be deprecated: not recommended in case of new implementations
||specifies if a title is required
|Title max length
||specifies the title maximum length (characters);
maximum: 25 characters; enable "Use title“ - see above
||specifies if an icon is required
||specifies the image type
|Image min width
||see chapter "About image width and height“ below
|Image min height
see chapter "About image width and height“ below
||specifies if data are required
About image width and height
Image min width
- specifies the minimum width you accept;
- images (served by DSPs) which are wider than this minimum width will be resized by the SDK (as configured by the SDK developer)
- together with the "Image min height" value (see below), the "Image min width" must respect one of the following aspect ratios 1:1, 4:3 or 1.91:1; this is mandatory, since RTB+ supports resizing for these aspect ratios only!
- maximum widths by aspect ratio:
aspect ratio 1:1 => max width: 1000px;
aspect ratio 4:3 => max width: 1600px;
aspect ratio 1.91:1 => max width: 1200px
- Example: if the min. width is 720px, the min. height must be 720px (aspect ratio 1:1), or 540px (aspect ratio 4:3) or 377 (aspect ratio 1.91:1)
Image min height
- specifies the minimum height you accept;
- images (served by DSPs) which are higher than this minimum height will be resized by the SDK (as configured by the SDK developer)
- together with the "Image min width" value (see above), the "Image min height" must respect one of the following aspect ratios 1:1, 4:3 or 1.91:1; this is mandatory, since RTB+ supports resizing for these aspect ratios only!
- see also example above