E-ntegration table

Matrix

AdFormat Web InApp
Integration Option Banner Video Native Banner Video Native
JS tag
VAST tag
VPAID tag
Native tag
E-ntegration

# Tag Integration

SSP platform generates tags for integration with suppliers. These tags are to built into the sources of traffic and are used to send the request for ads from there. When the user is located at the place where the ads must be served, your traffic source (e.g. site page or application) fires the tag embedded there and the call reaches SSP servers if everything is set up correctly.

#JS Tag Banner Integration

JS tag integration works for banner ad format. You can use JS tags for banners in any supply source such as web-site, application, Google Ad Manager etc.

#Web Banner

So if you want to monetise banner traffic through SSP, here are JS tags that you can use :

Direct Web Page Tag

This is the tag for copy and paste into the web page where you have the placeholder for banner ads. Please embed it into body of the page.

<script type="text/javascript" src="https://service.e-volution.ai/?c=b&m=s&placementId=[PLACEMENT_ID]"></script>

Note: It does not require any macros swapping out. Just embed as is. SSP will pass the request to the demand side based on the settings and info provided on UI in inventory and placement settings. Also, please make sure that you have put it in the right order in case you have some waterfall of the tags on the page.

 

JS tag

This tag fits good for the users of the ad servers, traffic aggregators or the publishers who wants to pass custom macros values. Please contact our representative in order to get more details.

<script type="text/javascript" src="https://service.e-volution.ai/?c=b&m=tag&placementId=[PLACEMENT_ID]&ip=[IP]&ua=[UA]&domain=[DOMAIN]&page=[PAGE]&secure=[SECURE]&language=[BROWSER_LANGUAGE]&bidfloor=[BIDFLOOR]&gdpr_consent=[GDPR_CONSENT]"></script>

 

Async Tag

This type of tag is aimed to resolve timeout issues. Sometimes it happens that websites are loading the content forever when trying to do that simultaneously with ads loading. If you face such an issue, you can use async tag. It allows to load ads into the placeholder only after the content of the website is displayed.

Note: this tag is an alternative to Direct Web page tag, which loads ads and content synchronously. So if you already use it on the page, but decided to go ahead with async tag, please delete the first one from the page and replace it with async one. They will not work if they both are set up in the one place.

Here are the steps to reproduce in order to embed it to the page:

Please plug in the library in <head> of the page.

<script src="https://service.e-volution.ai/?c=res&m=async"></script>

Please add html to the <body> of the page.

<div id="block_%%PLACEMENT_ID%%"></div>

Please add ads to the website:

<script type="text/javascript">
    var adUnits = [
        {
            code: 'block_%%PLACEMENT_ID%%',
            placement_id: %%PLACEMENT_ID%%,
            sizes: [%%_WIDTH_%%, %%_HEIGHT_%%]
        }
    ];
    eVolution.buildUnits(adUnits);
</script>

Field values:

  • code – String id of the block to place ads in;
  • placement_id – Integerid of the block to place ads in;
  • sizes: [width<Integer>, height<Integer>] – sizes. The first number stands for width and the second one for height.

If you are the user of Google Ad Manager and you want to monetise traffic through SSP from Google UI, please refer to this specific type of integration.

#InApp Banner

If you want to monetise banner traffic from applications, you can use:

Mopub Tag

If you are using Mopub SDK in your application, this tag will help you. Please refer to Mediation part for more details.

<script type="text/javascript">
    var placementId = [PLACEMENT_ID];
    var p = document.currentScript;
    var s = document.createElement("script");
    s.src = "https://service.e-volution.ai?c=b&m=api&app=1&res=mopub&placementId="+placementId+"&bundle=%%BUNDLE%%&ip=%%IPADDRESS%%&ua=%%USERAGENT%%&lat=%%LATITUDE%%&lon=%%LONGITUDE%%&ifa=%eudid!";

    p.insertAdjacentElement("afterend", s);
</script>
JS tag

This tag fits good for the users of the ad servers, traffic aggregators or the publishers who wants to pass custom macros values. Please contact our ad op representative in order to get more details.

<script type="text/javascript" src="https://service.e-volution.ai/?c=b&m=tag&app=1&res=json&placementId=[PLACEMENT_ID]&ip=[IP]&ua=[UA]&name=[APP_NAME]&bundle=[APP_BUNDLE]&ver=[APP_VERSION]&os=[DEVICE_OS]&osv=[DEVICE_OS_VERSION]&make=[DEVICE_MAKE]&model=[DEVICE_MODEL]&w=[DEVICE_W]&h=[DEVICE_H]&hwv=[DEVICE_HW_VERSION]&ifa=[IFA]&js=[JS]&carrier=[CARRIER]&paid=[PAID]&country=[GEO_COUNTRY]&geo_type=[GEO_TYPE]&city=[GEO_CITY]&lat=[GEO_LAT]&lon=[GEO_LON]&bidfloor=[BIDFLOOR]&gdpr_consent=[GDPR_CONSENT]"></script>

#VAST/VPAID Integration

VAST and VPAID tag integration works for video ad format. You can use these tags for videos in any supply source such as web-site, application, Google Ad Manager etc. So if you want to monetise video traffic through SSP, here are VAST and VPAID tags that you can use:

 VAST tag for Web video

Please select VAST or VPAID based on what you want to receive in the response. Please make sure that you swap out the macros with the values in order to get ads.

Original VAST tag for Web looks like:

https://service.e-volution.ai/?c=v&m=tag&placementId=[PLACEMENT_ID]&videotype=[VIDEO_TYPE]&wPlayer=[VIDEO_W]&hPlayer=[VIDEO_H]&ip=[IP]&ua=[UA]&domain=[DOMAIN]&page=[PAGE]&secure=[SECURE]&language=[BROWSER_LANGUAGE]&bidfloor=[BIDFLOOR]&gdpr_consent=[GDPR_CONSENT]

Macros you have to swap out:

  • placementId – Number  – Placement Id on platform
  • domain – String – Website domain required
  • page – String – URL of the page where the impression will be shown
  • ip – String – IPv4
  • ua – String Url – encoded user agent string
  • secure – Number – Flag to indicate if the impression requires secure HTTPS URL:
    Allowed values: 0 – non-secure, 1 – secure
    Default value: 0
  • language – String – Browser language using ISO-639-1-alpha-2. Lowercase.
  • bidfloor – Number – Minimum acceptable price.
  • gdpr_consent – String – The values ALL or NO GDPR Documentation Always encrypted, for instance hashed.
  • video_type – String – VAST.
  • wPlayer – Number – Video player width (in pixels). required
  • hPlayer – Number – Height of video player (in pixels). required

Please make sure that your back-end swaps out the macros. If the macros values are not passed correctly, you will not get ads from SSP. All macros values serve the information for the bid request. The more data you pass the more chances to get bid from demand partners.

Correctly passed tag example:
https://service.e-volution.ai/?c=v&m=tag&placementId=99999&videotype=VAST&wPlayer=360&hPlayer=780&ip=88.232.175.21&ua=Mozilla%2F5.0+%28Macintosh%3B+Intel+Mac+OS+X+10_15_7%29+AppleWebKit%2F537.36+%28KHTML%2C+like+Gecko%29+Chrome%2F100.0.4896.127+Safari%2F537.36&domain=exmaple.com&page=exmaple.com/test-exmaple.html&secure=1&language=en&bidfloor=3.4&gdpr_consent=BOcN9RKOniuO3AHABBESCv-AAAAst7_______9______9uz_Gv_v_f__33e8__9v_l_7_-___u_-3zd4u_1vf99yfm1-7etr3tp_87ues2_Xur_959__3z3_FIAAAAAAAAAAAAAAAAAAAAAAAAAA

 

Incorrectly passed request

(!macros are not swapped out! SSP cannot recognise what it is):

https://service.e-volution.ai/?c=v&m=tag&placementId=[PLACEMENT_ID]&videotype=[VIDEO_TYPE]&wPlayer=[VIDEO_W]&hPlayer=[VIDEO_H]&ip=[IP]&ua=[UA]&domain=[DOMAIN]&page=[PAGE]&secure=[SECURE]&language=[BROWSER_LANGUAGE]&bidfloor=[BIDFLOOR]&gdpr_consent=[GDPR_CONSENT]

#VPAID tag for Web video

VPAID tag turns back VAST XML, where you can get VPAID only.

Original VPAID tag for Web looks like:

https://service.e-volution.ai/?c=v&m=tag&placementId=[PLACEMENT_ID]&videotype=[VIDEO_TYPE]&wPlayer=[VIDEO_W]&hPlayer=[VIDEO_H]&ip=[IP]&ua=[UA]&domain=[DOMAIN]&page=[PAGE]&secure=[SECURE]&language=[BROWSER_LANGUAGE]&bidfloor=[BIDFLOOR]&gdpr_consent=[GDPR_CONSENT]

Macros you have to swap out:

  • placementId – Number -Placement Id on platform
  • domain – String – Website domain, required
  • page – String – URL of the page where the impression will be shown
  • ip – String – IPv4
  • ua – String – Url encoded user agent string
  • secure – Number – Flag to indicate if the impression requires secure HTTPS URL:
    Allowed values: 0 – non-secure, 1 – secure
    Default value: 0
  • language – String – Browser language using ISO-639-1-alpha-2. Lowercase.
  • bidfloor – Number – Minimum acceptable price.
  • gdpr_consent – String – The values ALL or NO GDPR Documentation Always encrypted, for instance hashed.
  • video_type – String – VPAID.
  • wPlayer – Number – Video player width (in pixels). required
  • hPlayer – Number – Height of video player (in pixels). required