Publisher Side File Implementation Instructions
Serving over-the-page ads into iframes using the publisher-side buster file
To serve Atlas Rich Media expanding ad tags into iframes, a static HTML file, called “publisher-side file,” (or sometimes “buster-file”) must be hosted on the publisher's site in the same domain as the placement calling the over-the-page tag. This file can be obtained here (simply right-click and select 'Save Target As' or 'Save Link As' or 'Save Linked File').
Once this file is in place, enter the URL of the publisher-side file after “buster_url=”.
For example:
Sample tag (with sample buster URL implemented):
<script language="JavaScript" type="text/javascript" src="http://view.atdmt.com/ARM/jview/137559071/direct;vt.1/01?
buster_url=http://www.domain.com/atlas_rm.htm&pub_view_url=&click=">
</script>
<noscript>
<a href="http://clk.atdmt.com/ARM/go/137559071/direct/01/" target="_blank">
<img border="0" src="http://view.atdmt.com/ARM/view/137559071/direct/01/" />
</a>
</noscript>
Although it is recommended that an absolute URL be used, a relative path can be used when necessary (such as when the publisher has several different sub-domains that are running the Atlas Rich Media tag. This would avoid the need for running separate tags per sub-domain, but the publisher side file must still reside on all of the sub-domains that the ad is running on).
Example: buster_url=/atlas_rm.htm
When the Atlas Rich Media ad is served, it references the publisher-side file, and will be displayed over the page itself rather than being confined to the iframe.
