Table of Contents
Overview
HTML5 creatives are used to support advanced creative formats, such as playables.
Please note that the file must be .html. Other formats such as .zip are not supported. If the creative requires additional assets, they should be encoded into the .html file or you can host assets on a third party CDN and reference them from the .html file.
To track clicks in Beeswax, you must use the {{CLICK_URL}} macro.
How it works
The following fields are available:
| Creative Field | Description |
| Advertiser | Advertiser under which you are creating this creative. Creatives can be assigned to any line item beneath this advertiser only. |
| Creative Name | Name of the creative |
| Width x Height | The width and height 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 |
| Start Date | Optional start date for the creative |
| End Date | Optional end date for the creative |
| Alternative ID | Alternative ID for the creative. Use this field to map an creative ID in Beeswax to a creative ID in your system. |
| Asset | Either “Choose an Existing Asset” or “Upload a New Asset”. Only assets uploaded beneath this advertiser will appear in the “Choose an Existing Asset” drop down |
| MIME Type | MIME of the media asset loading by your ad tag. This field is used for creative matching. |
| Expandable Type | Select if your tag expands automatically, on user click, on user rollover, or does not expand. |
| Expandable Direction | The direction in which an expandable will expand, if applicable. |
| Responsive Size | Toggle “Yes” if the creative adjusts size; select “No” if it is a fixed size. |
| In-Banner Video | Select whether it is click-to-play or autoplay. If there is no video, select no-video. |
| Thumbnail | Required if you are running your tag on MoPub or Millennial Media. The thumbnail should be an image file. Best practice is to always include a thumbnail image. |
| Technical Vendor | On Google’s AdX, any technical vendor including a 3rd party ad server or measurement vendor need to be declared. Failure to declare technical vendors may result in your creatives being rejected by AdX. |
| Landing Page URL | This is the full URL that the user will land on after clicking on your creative. For example, www.ford.com/landingpage/fordfocus. Failure to include the full URL may result in your creatives being rejected by Google’s AdX. |
| Creative Add-Ons | If you previously have defined pixels or scripts via the creative add-ons module, they will be listed here. |
| Additional Pixels | Additional tracking pixels that will be fired at the same time as the impression. This field should contain a URL, for example https://ad.doubleclick.net/ddm/trackimp/[additional_parameters]. |
| Additional Scripts | Additional JS tags to be called at the same time as the impression. This field should contain a URL, for example: |
To traffic an HTML5 creative:
- Create the HTML5 creative on a third party platform or creative builder. Beeswax macros can be used in the creatives
- Export the HTML5 asset into a single .html file.
- Select +New > Creative
- Select ‘HTML5 Creative’ from the creative type dropdown:
5. Enter a creative name, the start and end date, and select the ad size and advertiser
6. Upload the creative asset via the “ad content” section:
7. Select the rest of the creative attributes and save.
Please note, to serve MRAID HTML5 Creatives the .html file content will need to invoke MRAID via one of the two methods outlined below.
<script src="mraid.js"></script> This call-out will allow for the ad container to access the SDK's mraid library.
<script src="https://[host]/libraries/mraid.js"></script> This call-out will allow for the client to host the MRAID library on their own CDN rather than rely on SDK for MRAID support.
Caveats for MRAID HTML5 creatives hosted by Beeswax are below:
MRAID HTML5 creatives should only be associated with line items that target MRAID and inApp inventory.
The Beeswax creative preview URL does not support MRAID; therefore, the HTML5 preview will not work but the creative will render on MRAID inventory when served programmatically.
Dynamic macros from a Data Augmentor or Custom Bidding Agent are not supported for HTML5 creatives hosted in Beeswax.