...
| Code Block |
|---|
https://ads.us.e-planning.net/vssp/1/18f66?sz=640,480&ur=https%3A%2F%2Fwww.test.com&vv=3&vctx=1 |
In-App & CTV VAST tag
[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.
...
| Code Block |
|---|
https://ads.us.e-planning.net/vssp/1/18f66?sz=640,480&b=com.android.myapp&vv=3&vctx=1&ifa=AA000DFE74168477C70D291f574D344790E0BB11 |
Extra fields
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.
User & device fields
Field | Description |
|---|---|
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 for Canadian users, gpp is recommended instead |
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 |
Inventory fields
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: |
pt | 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. |
Content fields
Field | Description |
|---|---|
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) |
len | Length of content in seconds |
ctx | Type of content (game, video, text, etc.). |
livestream | 0 = Not live |
Bid floor
By default the auction will be performed using the price configured in the UI. However, it is possible to define prices dynamically in the tag using the p= parameter.
...