Banner Rendering on a Page
A script library placed on a page collects all slots (1) and sends the only request to a server (Invocation) (2) that returns banners (3). Then, the library renders creatives once a placeholder and a banner are ready (4). Afterwards the library sends event trackers to the server (5).
Script Library
ScriptLib
|
HTML5 API
(application programming interface)
|
UI/HTML5 Banner
Through properties and methods, API informs the script library what to do with a container (change size, positioning, etc.) in which a banner is rendered.
The latest HTML5 API version is 2.0. All formats work according to it. The previous version of script library (1.0) hasn’t been supported since December 2017.
Formats and Templates
A format is a general name that defines a creative’s behaviour.
A template is a form in UI that allows to upload files (image, video, archive) and select available settings.
Template types:
- UI template: to upload images/videos. It doesn’t requires particular skills; creatives can’t be customized.
- ZIP archive: to upload HTML5 creatives that correspond to technical requirements and are saved as zip archives. It requires design/development skills. Creatives can be customized according to customer’s requirements.
Check how formats are divided by template type
- on the website
- in UI in Help — Creatives — Creatives specifications (block names with HTML5_—for formats that are uploaded as zip files through _HTML5 templates; block names without HTML5—for formats that are uploaded through UI templates)
- in documentation (HTML5 in a format name defines whether you need to upload a creative through UI templates)
Format names and respective UI templates through which creatives are uploaded mostly correspond.
HTML5 fromats are uploaded as zip archives through HTML5 templates: HTML5 Banner, HTML5 Float, HTML5 Mobile Banner, HTML5 Mobile Float.
Ad type:
- In-page/Banner: creatives that have a particular placement on a page. They move with a page when you scroll.
- Floating/Rich Media: ‘floating’ creatives; they are placed regarding the screen and don’t move with a page
- Video: creatives that show in a video player
- Mobile: creatives that show on mobile devices
Standard and WOW templates
Depending on the complexity of developing and using Admixer technology, all templates are divided into Standard and WOW. See details here.
Initial Better Ads Standards
Ad standards for desktops and mobile devices are designed by The Coalition for Better Ads organization based on the research on user experience to exclude the least wanted creative behaviour.
Check a list of Admixer formats that may partially or completely violate the Standards requirements here.
Friendly/Non-friendly iFrames
Friendly iFrame is an iframe that loads to a page of the same domain where the page is located. The frame allows a creative to interact with the page.
Non-friendly iFrame is hosted on a domain different from that where a tag loaded into a frame is located. It doesn’t allows a creative to interact with the page.
Admixer renders creatives in Friendly iFrame.
External Code in Admixer
A code of a standard unexpandable banner that belongs to an external ad tech providers is uploaded through External banner.
Use an External rich media template for a third-party code of a rich media banner. Our template allows a banner to escape the frame if a third-party code provides it.
Use an External expandable banner template for a third-party code of an Expandable banner. It works the same way as the previous one.
Admixer Code in a Third-party System
To upload the Admixer tag to third-party template, use special external banner code (go to Get Code — Get External Code) or external zone code (go to Ad unit — External code).
Admixer tag can escape a third-party frame if that frame is designed according to Friendly iFrame.
Third-party systems use special macros to track clicks. Check how to add third-party macros here.
VAST, VPAID, MRAID
The guide is provided by Interactive Advertising Bureau.
VAST (Digital Video Ad Serving Template) is a universal XML schema for serving ads to digital video players, and describes expected video player behavior when executing VAST-formatted ad responses.
Admixer system generates a VAST response for the following templates:
- In-stream video (Preroll, Midroll, Postroll)
- Video overlay
VPAID (Video Player Ad-Serving Interface Definition) establishes an API between video players and ad units, enabling a rich interactive in-stream ad experience.
Use a VPAID template to upload VPAID creatives in Admixer UI.
MRAID (Mobile Rich media Ad Interface Definition) is the common API for mobile rich media ads that will run in mobile apps.
Creatives show in mobile apps through AdmixerSDK.
