Overview:
The AerServ mobile banner tag is intended for publishers that would like to integrate banner ads into their mobile properties, and are not able to integrate the AerServ SDK. The mobile banner ad tag is a small piece of JavaScript code that displays a mobile banner ad.
Ad Tag Types
AerServ offers multiple mobile banner ad tag types outside of the SDK. We strongly recommend publishers integrate via JavaScript to fully maximize their revenue opportunities.
Example JavaScript Tag
<script src="https://ads.aerserv.com/as/?plc=380000&key=1&cb=&adid=&lat=&long=&dh=&dw="></script>
Example Iframe Tag
320x50
<iframe src="https://ads.aerserv.com/as/?plc=380000&key=2&cb=&lat=&long=&url=&ua=&ip=&locationsource=&age=&yob=&gender=&mraid=&pchain=" frameBorder="0" border="0" scrolling="no" width="320px" height="50px">
</iframe>
300x250
<iframe src="https://ads.aerserv.com/as/?plc=380000&key=2&cb=&lat=&long=&url=&ua=&ip=&locationsource=&age=&yob=&gender=&mraid=&pchain=" frameBorder="0" border="0" scrolling="no" width="300px" height="250px"></iframe>
320x480
<iframe src="https://ads.aerserv.com/as/?plc=380000&key=2&cb=&lat=&long=&url=&ua=&ip=&locationsource=&age=&yob=&gender=&mraid=&pchain=" frameBorder="0" border="0" scrolling="no" width="320px" height="480px"></iframe>
For publishers using a third party SDK and including AerServ as part of their mediation stack, we do not allow iFrame tags to be used. JavaScript tags must be used.
Integration Options
AerServ offers multiple mobile banner integration options outside of the SDK.
Direct on Page
Publishers not using an adserver have the option of trafficking the mobile banner tag directly within the page code of their mobile website or app. This is not the suggested or ideal integration as the publisher will have less control over delivery.
Adserver
The mobile banner code can also be placed within an adserver to give the publisher additional flexibility, but testing needs to be done to ensure it works properly within your adserver.
PLC
The JavaScript code provided to each publisher contains a Placement (PLC) number that is unique to each publisher account and has ad campaigns assigned just for their site. A PLC is a unique ID that is used to retrieve ads for a particular site and placement created within the AerServ platform. Your PLC can be found within the Inventory section of the AerServ platform.
Please reach out to your Account Manager with any questions regarding your PLC or how to obtain it.
Passback Tags
In the event that AerServ cannot fill a banner request, we are able to "pass back" the impression to your adserver via a "passback tag". This is a recommended step as it allows AerServ to send the ad request back to the publisher, allowing the publisher to monetize the request somewhere else within their system.
Please contact your Account Manager for help setting up passback tags.
Macros
Keys=Macro are separated by "&" in the ad tag URI. And should be placed after the "key" key=value
It is important that each publisher using a third party adserver notifies AerServ regarding the macros they are able to populate and pass through.
If integrating at the tag level, please replace our internal macros with your server macro's.
Parameter Overview
PARAMETER | DESCRIPTION | EX. VALUE | MOBILE WEB | IN-APP | BANNER/VIDEO | DATA TYPE |
---|---|---|---|---|---|---|
adid |
Advertising ID - Unhashed Apple IDFA or Google AdId |
bbd606b1-32ab-4a1e- |
N/A | Required | Both | String |
age |
Age Demographic Information |
22 | Optional | Optional | Both | Integer |
appname | Application Name | Tien%Len%Online | N/A |
Required * Passing a application name is required. However, if you have set up your app in the AerServ platform using an Apple App Store URL or Google Play Store URL,AerServ can extract the application name from our system and you are not required to pass it in your ad request. |
Both |
String (encoded) |
appversion |
Application Version |
1.5 | N/A |
Optional |
Both |
String |
bundleid |
App Bundle ID |
com.popcap.ios.BejBlitz |
N/A |
Required * Passing a BundleID is required. However, if you have set up your app in the AerServ platform using an Apple App Store URL or Google Play Store URL,AerServ can extract the BundleID from this field and you are not required to pass it in your ad request.
|
Both |
String (encoded) |
carrier |
Cell carrier |
Verizon |
N/A |
Optional |
Both |
String (encoded) |
cb |
A unique number generated (guid) to prevent a browser from caching the ad and to ensure a unique call to the server for each ad. This macro helps eliminate discrepancies with outside servers |
46170 |
Required | Required | Both | String |
dh | Device screen height. | 480 | Optional | Optional | Both | Integer |
dnt |
Do Not Track . Values: 1 - for do not track is enabled, 0 - for allow to track |
1 | N/A | Required | Both | Boolean |
dw |
Device screen width. |
320 | Optional | Optional | Both | Integer |
gdpr |
Flag to signify whether the request needs to be treated under gdpr compliance. Omission indicates compliance is unknown. |
1,0 | Optional | Optional | Both | Boolean |
gdpr_consent |
Flag to signify that the end user has given consent to use and process their data. Omission indicates no consent. |
1,0 | Optional | Optional | Both | Boolean |
gender |
Gender demographic information. Values: male, female |
male | Optional | Optional | Both | String |
inttype |
Device ID Type. Values: 1 - Mobile/Tablet, 2 - Personal Computer, 3 - Connected TV, 4 - Phone, 5 - Tablet |
1 | Optional | Optional | Both | Integer |
ip |
Client IP Address |
123.456.78.9 |
Required | Required | Both | String |
key |
Response type from the server. |
1(js), 2(html), 3(for JSON) |
Required | Required | Both | Integer |
lat |
Latitude of Device |
33.58 |
Optional | Optional | Both | Float |
locationsource |
Origination of Lat/Long. Values: 1 - GPS, 2 - Derived from IP |
1 |
Optional | Optional | Both | Integer |
long | Longitude of device | 117.73 | Optional | Optional | Both | Float |
make | Device Make | apple | Optional | Optional | Both | String (encoded) |
model | Device Model | iPhone 7 | Optional | Optional | Both | String (encoded) |
mraid |
MRAID Flag 1 = allow MRAID 0 = do not allow |
1,0 | Optional | Optional | Banner | Boolean |
network |
The connection your device is using |
wifi, carrier | N/A | Optional | Both | String (encoded) |
os | Operating System | iOS | Optional | Optional | Both | String (encoded) |
osv | Operating System Version | 10.1 | Optional | Optional | Both | String |
pchain |
TAG payment chain. ex. pchain=[PCHAIN] |
123:xyz | Strongly Recommended | Strongly Recommended | Both | String (encoded) |
pl |
Indicates whether the call is for a preloaded ad. Values: 0 designates a call for an ad that will be displayed right away, 1 designates a call made to preload an ad |
1 | N/A | Required | Both | Integer |
plc |
plc - the PLC number sets the width and height |
1000308 | Required | Required | Both | Integer |
site_appstore_id |
Apple appstore ID |
123456789 | N/A |
Required for IOS |
Both |
Integer |
siteurl | App Store URL |
https://itunes.apple.com |
N/A |
Required * Passing a app store URL is required. However, if you have set up your app in the AerServ platform using an Apple App Store URL or Google Play Store URL,AerServ can extract the app store URL from our system and you are not required to pass it in your ad request. |
Both |
String (encoded) |
type |
Device Type. Values: phone, tablet |
Tablet | Optional | Optional | Both | String |
ua | Client User Agent |
Mozilla%2F5.0%20 |
Required | Required | Both | String (encoded) |
url |
The full page URL where advertisement will be displayed |
Required | N/A | Both | String (encoded) | |
vpaid |
VPAID flag set this if you would like or dislike VPAID ads. Values: 1=allow, 0=do not allow |
1 | Optional | Optional | Video | Integer |
vph |
Video player height |
480 | Optional | Optional | Video | Integer |
vpw | Video player width | 360 | Optional | Optional | Video | Integer |
yob | Year of birth demographic information | 1985 | Optional | Optional | Both | Integer |
Headers:
If sending an IP through the ad request parameter (i.e. https://ads.aerserv.com/as/?plc=[PLACEMENT]&key=2&ip=xxx.xx.xxx), make sure the same IP value in the ad request parameter is contained in the request headers for the IP
Comments