VAST is today's preferred technology for monetizing video inventory. E-Planning SSP can be implemented using VAST tags for both web traffic and mobile apps.
VAST tags consist of URLs that must be implemented directly in your video player or ad server. They can be extracted from the platform by accessing the Implementation tab.
There are different tag versions, depending on where they will be implemented:
Web VAST tag: Use this code if you are going to implement the VAST tag in a web site
In-App VAST tag: Use this code if you are going to implement the VAST tag in a mobile app
CTV VAST tag: Use this code if you are going to implement the VAST tag in a CTV app
Remember that you also need to implement the lines in the ads.txt file correctly. Click here for more info about ads.txt.
Copy the tag and paste it into your video player or ad server, according to the instructions provided by them for implementing VAST tags.
The tags that can be extracted from the platform contain a series of macros, which are automatically replaced by your video player or ad server. In case your video player or ad server does not support VAST macros, please replace them manually.
[PLAYERSIZE]: must be replaced by the height and width of the video player, separated by the "," (comma) character. For example: 640,480
[PAGEURL]: must be replaced by the URL of the current page encoded.
[PLACEMENTTYPE]: must be replaced by 1 if the player is in-stream or 2 if the player is out-stream.
Eg:
https://ads.us.e-planning.net/vssp/1/18f66?sz=640,480&ur=https%3A%2F%2Fwww.test.com&vv=3&vctx=1 |
[PLAYERSIZE]: must be replaced by height and width of the video player, separated by the "," (comma) character. For example: 640,480
[APPBUNDLE]: must be replaced by the bundle of the application, for example com.android.myapp
[PLACEMENTTYPE]: should be replaced by 1 if the player is in-stream or 2 if the player is out-stream
[IFA]: must be replaced by the user's Identifier for Advertisers (IFA). If not available or unknown, it should be left blank.
Eg:
https://ads.us.e-planning.net/vssp/1/18f66?sz=640,480&b=com.android.myapp&vv=3&vctx=1&ifa=AA000DFE74168477C70D291f574D344790E0BB11 |
Some fields are optional and are not included by default in the tags. However, we strongly recommend you to add them when available, as it will help to better monetize your content.
You can append any of these as a parameter to your VAST tag. For example, if you want to add age information to the tag:
https://ads.us.e-planning.net/vssp/1/18f66?sz=640,480&b=com.android.myapp&vv=3&vctx=1&ifa=AA000DFE74168477C70D291f574D344790E0BB11&age=35
All parameters should be URL encoded where necessary.
Field | Description |
---|---|
ip | User IPv4 addresss |
ua | User Agent |
dtype | Device Type (device.devicetype): |
ifv | Identifier For Vendors (aka IDFV) |
lat | Latitude expressed as a float |
lon | Longitude expressed as a float |
lltype | Lat/Lon type, ie. how was lat/lon collected? |
age | Age of user (eg. 51, 24) |
gender | Gender of user. Lowercase values will work as well |
us_privacy | US privacy string, required jurisdictions where legally enforced |
consent | TCF2 consent string |
gpp | GPP string, required in jurisdictions where legally enforced |
gpp_sid | GPP section id. Comma separated for multiple sections |
coppa | Boolean to specify if the transaction is subject to COPPA or not |
Field | Description |
---|---|
minduration | Minimum duration allowed in seconds |
maxduration | Maximum duration allowed in seconds |
protocols | Comma separated list of supported video protocol IDs |
apis | Comma separated list of supported video API IDs |
pm | Playback method that is used, if none is specified, any may be used: |
sd | Indicates the start delay in seconds for pre-roll, mid-roll, or post-roll: |
plcmt | Placement type for the impression: |
instl | Whether this ad unit is within an interstitial or not |
pos | Position of ad in the viewport |
schain | The serialized form of the supply chain object. Only required if the publisher’s relationship with E-Planning is not direct. |
ssai | Indicates if server-side ad insertion |
ipd | Inventory partner domain. Third-party domain authorized to validate ads.txt and app-ads.txt |
mnbr | Minimum bit rate in Kbps |
mxbr | Maximum bit rate in Kbps |
sturl | App store URL for an installed app |
These fields describe the content in which the ad will appear. Content fields are highly recommended in CTV inventory and should be added whenever possible.
Field | Description |
---|---|
content_id | ID uniquely identifying the content |
title | Content title (e.g. Search Committee) |
series | Content series (e.g. The Office) |
genre | Genre that best describes the content |
season | Content season (e.g., “Season 3”) |
episode | Episode number |
language | Content language using ISO-639-1-alpha-2 (i.e., EN) |
rating | Content rating (e.g., MPAA) |
len | Length of content in seconds |
ctx | Type of content (game, video, text, etc.). |
content_categories | Comma-separated list of IAB categories |
content_keywords | Comma-separated list of keywords |
livestream | 0 = Not live |
channel | Channel name (e.g., “MTV”) |
content_producer_name | Content producer or originator name (e.g., “Warner Bros”) |
network_name | Network the content is on (e.g., a TV network like “ABC") |
By default the auction will be performed using the bid floor configured in the UI. However, it is possible to define bid floors dynamically in the tag using the p= parameter.
To set them up, add to the tag (in any of its versions) a new parameter p= with the bid floor. For example:
https://ads.us.e-planning.net/vssp/1/18f66?sz=640,480&b=com.android.myapp&vv=3&vctx=1&p=1.23
Then the auction will have a minimum price of USD 1.23
We support the use of the <Pricing> tag in the VAST response, where we report the bid price expressed as CPM. If your ad server or video player supports it, you can use this field to decide whether to play the ad or not based on other bids you may have for the same impression.
This is an example of a a VAST document using the <Pricing> tag:
<VAST version="3.0" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <Ad id="45-1678755"> <InLine> <AdSystem>e-planning</AdSystem> <AdTitle>Demo Ad</AdTitle> <Pricing model="cpm" currency="USD"> <![CDATA[ 5.00 ]]> </Pricing> |
You can find more information in the IAB VAST 3.0 definition under the 2.2.4.2 section.
For web implementation, it is important to sync users as this can considerably increase the results.
To do this, insert the following HTML code in all your pages:
<iframe src="https://ads.us.e-planning.net/uspd/1/" width="0" height="0" style="display: none;"></iframe> |