User Tools

Site Tools


conversion-faq-en:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
conversion-faq-en:start [2015/12/08 11:36]
avarga
conversion-faq-en:start [2015/12/10 09:15]
avarga
Line 7: Line 7:
 ==== Issue: Using folders in relative links ==== ==== Issue: Using folders in relative links ====
  
-In case after upload the images in the banner banner do not show up, is most like due to tehfact, that the banner searches for the resources in sub directories, like in this example:+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:
  
 <code html> <code html>
Line 31: Line 31:
 ==== Solution ==== ==== Solution ====
  
-Because the AdServer is unable to modify teh files of an easyHTML banner, we have to change the AdServer variables to local (without folders) relative path:+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:
  
 <code html> <code html>
Line 41: Line 41:
 ==== Issue: The usage of two uncompatible code snipets ==== ==== Issue: The usage of two uncompatible code snipets ====
  
-This issue manifests by opening to 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.+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. A possible reason is that two suggested code snipets are mixed up - Javascript and HTML.
Line 61: Line 61:
 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. 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 use the matching code instead of the above, from teh following link:+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 http://dev.adverticum.com/creatives:ehtml-en#html_example
Line 67: Line 67:
 ===== The banner is not clickable / It redirects to a wrong site ===== ===== The banner is not clickable / It redirects to a wrong site =====
  
-==== Issue: Nem került bele a goa-helper.js ====+==== Issue: The goa-helper.js is missing ====
  
 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'' 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.
Line 73: Line 73:
 ==== Solution ==== ==== Solution ====
  
-The ''goa-helper.js'' has to be included in teh beginning of the banner, usualy in the end of the ''head'' tag, with the code snippet from the following page:+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 http://dev.adverticum.com/creatives:ehtml-en#including_goa-helperjs
Line 87: Line 87:
 ==== Solution ==== ==== Solution ====
  
-Because the AdServer is unable to modify teh files of an easyHTML banner, we have to change the AdServer variables to local (without folders) relative path:+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 http://dev.adverticum.com/creatives:ehtml-en#html_example
Line 93: Line 93:
 ==== Issue: Usage of Gemius specifications ==== ==== Issue: Usage of Gemius specifications ====
  
-In some cases, the banner is created by the Gemius specification, but are given to run in our AdServer. In tehse cases, the following code is present:+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:
  
 <code javascript> <code javascript>
Line 110: Line 110:
 ==== Solution ==== ==== Solution ====
  
-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.+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.
  
 <code javascript> <code javascript>
conversion-faq-en/start.txt · Last modified: 2016/10/03 15:43 by dczipperer