Here we discuss the most frequently recurring issues, the possible source of the issue, and recommended solutions.

In case after upload the images in the banner banner do not show up, is most like due to the fact, that the banner searches for the resources in sub directories, like in this example:

<img src="images/cica.png" />

While all resources will be placed inside the same folder after upload, the URLs have to be changed like the following example:

<img src="cica.png" />

Sometimes the banner is developed with the usage of previous Markup or HTML banner specification. In these cases resource URLs are refered like below:

<img src="[file: cica.png]" />

Because the AdServer is unable to modify the files of an easyHTML banner, we have to change the AdServer variables to local (without folders) relative path:

<img src="cica.png" />

This issue manifests by opening two windows on clicking the banner. One is moste likely is the correct landing page, and the URL of the other end in /undefined, and is most likely blank.

A possible reason is that two suggested code snipets are mixed up - Javascript and HTML.

For example:

<a id="clickTAG" href="" target="_blank">KATT</a>
 
<script>
  document.getElementById('clickTAG').onclick = function () {
    window.open(goa.clickTAG, goa.clickTARGET);
  }
</script>

Because in the example above clickTAG is an anchor tag, it will be clickable in itself. If we combine this element with the JS example snippet, we tell the browser to open a web page on click, onto an element that already opens a new page. So in the end we open two windows.

If we use an anchor element, we need to insert the matching code instead of the above, from the following link:

http://dev.adverticum.com/creatives:ehtml-en#html_example

The goa-helper.js manages the URLs and other variables for the banner, as it parses the query parameters, and compiles an object of them. The banner can read the clickTAG from there.

The goa-helper.js has to be included in the beginning of the banner, usualy in the end of the head tag, with the code snippet from the following page:

http://dev.adverticum.com/creatives:ehtml-en#including_goa-helperjs

Sometimes the banner is developed with the usage of previous Markup or HTML banner specification. In these cases CT URLs are refered like below:

<a id="clickTAG" href="[cthref]" target="[target]">KATT</a>

Because the AdServer is unable to modify the files of an easyHTML banner, we have to change the AdServer variables to local (without folders) relative path:

http://dev.adverticum.com/creatives:ehtml-en#html_example

In some cases, the banner is created by the Gemius specification, but are given to run in our AdServer. In these cases, the following code is present:

	var parsed =
(document.location.href.split('#')[1]||'').split('&');
	var params = parsed.reduce(function (params, param) {
		var param = param.split('=');
		params[param[0]] =
		decodeURIComponent(param.slice(1).join('='));
		return params;
	}, {});
// change link href
document.getElementById('clickTAG').href = params.clickTag;

While this code is similar to what the goa-helper.js does, we only need a little modification, to make CTs work. In the second line of the code, the '#' has to be replaced with '?' , because the easyHTML banner recieves the clickTAG URL among others, as query parameters.

	var parsed =
(document.location.href.split('?')[1]||'').split('&');
	var params = parsed.reduce(function (params, param) {
		var param = param.split('=');
		params[param[0]] =
		decodeURIComponent(param.slice(1).join('='));
		return params;
	}, {});
// change link href
document.getElementById('clickTAG').href = params.clickTag;