Click macros

// in AdAction

 
AdAction is currently available in two versions, version 4 and 5. The main differences between the two systems is that they operate on different domains. Most of the behaviour that existed in version 4 is still available in version 5, but with some slight modifications.
 
How it works
Handling clicks through a third-party adserving system is not always trivial or easy. AdAction provides the possibility to deliver the tags with ”Click macros”. This lets the local adserving system count clicks, and redirect them through AdAction and then to the clients website.
 
How to tell which version is being used
Since the two versions operate on different domains, it is very easy to spot which version is used. You can simply look for the two different domains in the text files:

• Version 4: Look for ”v4.adaction.se”
• Version 5: Look for ”de17a.com”

Different types of tags may come from the system, and the only difference between them is that the iframe tag is supplied as a script-tag instead. The same procedure is applied in both cases. Also, the iframe tag may contain an additional script tag in the end, which should be left unmodified.

 Example, version 5
The following lines shows a standard tag that is sent out from AdAction:

 
<iframe src="http://www.adaction.se/JavaScript" src="http://de17a.com/a/1234.js" width=”468” height=”60”></script>
<noscript><a href="http://de17a.com/a/1234.click" target="_blank"><img src="http://de17a.com/a/1234.image" border="0" width="468" height="60" galleryimg="no"></a></noscript>
If clicks need to be counted, AdAction can instead generate a tag that lets the local adserving system insert its own click url. If the tag that you were supplied with does not contain this click macro, please contact , indicating that you want a tag with click macro in it.
<iframe src="http://de17a.com/a/1234.iframe?url=[click]http%3A%2F%2Fde17a.com%2Fa%2F1234.click" width=”468” height=”60”></iframe>
<noscript><a href="http://www.adaction.se/[click]http%3A%2F%2Fde17a.com%2Fa%2F1234.click" target="_blank"><img src="http://de17a.com/a/1234.image" border="0" width="468" height="60" galleryimg="no"></a></noscript>
When the local adserving system processes the tag, it should recognize [click] and replace it with its own click url, and allow it to redirect to the address that is appended on the end. An example of a processed html-tag could look something like this:
<iframe src="http://de17a.com/a/1234.iframe?url=http://www.yourserver.com/click?redirect=http%3A%2F%2Fde17a.com%2Fa%2F1234.click" width=”468” height=”60”></iframe>
<noscript><a href="http://www.yourserver.com/click?redirect=http%3A%2F%2Fde17a.com%2Fa%2F1234.click" target="_blank"><img src="http://de17a.com/a/1234.image" border="0" width="468" height="60" galleryimg="no"></a></noscript>
 Example, version 4
The following lines shows a standard tag that is sent out from AdAction:
<script language="JavaScript" src="http://testsite.v4.adaction.se/js.php?658,4786,0,&z="></script>
<noscript><a href="http://testsite.v4.adaction.se/click.php?658,4786,0,&z=" target="_blank"><img src="http://testsite.v4.adaction.se/img.php?658,4786,0,&z=" border="0" width="468" height="60" galleryimg="no"></a></noscript>
If clicks need to be counted, AdAction can instead generate a tag that lets the local adserving system insert its own click url. If the tag that you were supplied with does not contain this click macro, please contact , indicating that you want a tag with click macro in it.
<script language="JavaScript" src="http://testsite.v4.adaction.se/js.php?658,4786,0,&z=&ourl=[click]http%3A%2F%2Ftestsite.v4.adaction.se%2Fclick.php%3F658%2C4786%2C0%2C%26z%3D"></script>
<noscript><a href="http://www.adaction.se/[click]http://testsite.v4.adaction.se/click.php?658,4786,0,&z=" target="_blank"><img src="http://testsite.v4.adaction.se/img.php?658,4786,0,&z=" border="0" width="468" height="60" galleryimg="no"></a></noscript>
When the local adserving system processes the tag, it should recognize [click] and replace it with its own click url, and allow it to redirect to the address that is appended on the end. An example of a processed html-tag could look something like this:
<script language="JavaScript" src="http://testsite.v4.adaction.se/js.php?658,4786,0,&z=&ourl=http://www.yourserver.com/click?redirect=http%3A%2F%2Ftestsite.v4.adaction.se%2Fclick.php%3F658%2C4786%2C0%2C%26z%3D"></script>
<noscript><a href="http://www.adaction.se/ http://www.yourserver.com/click?redirect=http://testsite.v4.adaction.se/click.php?658,4786,0,&z=" target="_blank"><img src="http://testsite.v4.adaction.se/img.php?658,4786,0,&z=" border="0" width="468" height="60" galleryimg="no"></a></noscript>
The flow of process
The local adserving system analyses the tag, and recognizes [click] as a click macro. It replaces this macro with its own click address. When the click address is triggered (the user clicks on the ad), the local adserving system needs to be able to redirect the browser to the url that has been appended to the end of the click address. AdAction will then be called from the browser, and redirected to the clients website.