Requirement:  GujAd Implementation

The page must be connected to the eMS AdControl via the GujAd which needs to be fully implemented.

Requirement:  Implementation Teaser AdSlots

If the GujAd framework is available, the AdSlots can send requests to the ad server.

Example (inoperable)

<div class="gujAd teaser" id="teaser_11">
<script type="text/javascript">
if (GujAd !== undefined && GujAd.cmd !== undefined) {
       GujAd.cmd.push(function() {
             GujAd.push('teaser_11');
       });
}
</script>
</div>

The implementation guide for GujAd and AdSlots is available HERE

Requirement: HTML Teaser Template / JSON

The components of a native teaser essentially come from the ad server and/or a CMS. Optically, the teasers are then oriented to the design of the respective page. The teaser is then configured by retrieving a JSON file during rendering. This passes the HTML elements, which in turn accesses the CSS of the page. Minor adjustments via JSON such as inserting the ad  and presentership label can also be made via JSON. This file is build and hosted by G+J eMS.

The delivery of an HTML teaser template by the publisher is mandatory!

Teaser template example:

left: original site teaser,                                                    right: Autonative test teaser

Testing the ad slot implementation

Permanent test circuits with high priority are set up in the ad server, which are called up via the URL parameter ?testZone=develop. In addition, these banners contain the IDs of the ad server and the creative size, as shown here for stern.de as an example:

https://www.stern.de/?testZone=develop

Testing native teaser

There are also permanent test teaser campaigns existing. These can be loaded onto the page using the following URL parameters:

?gujAd=1&testZone=gpt&adType=teaser_16_9

?testZone=gpt&adType=an_teasertest

 This teaser can then be seen at any point where a teaser slot is available.