IFrame Delivery
Publisher-Side File (PointRollAds.htm)
When served into an IFrame, a PointRoll Ad needs to communicate with the parent page for panel display and panel placement. However, the JavaScript object model does not allow two frames (the IFrame and the parent page in this case) to communicate if they come from different origins. For this serving scenario, PointRoll's patent-pending Ad technology utilizes a simple, generic HTML Publisher-Side File that is placed on the web servers hosting any sub-domains on which PointRoll Ads will be delivered into an IFrame. This Publisher-Side File is never seen or referenced directly by end users - it is only referenced by PointRoll's Ad Delivery System when a PointRoll Ad is being served.
Reasons for the Publisher-Side File
- Proper Panel Placement
- Proper Panel Display & Removal
- Abide by the JavaScript 'Same Origin Policy'
- Eliminate the need for any modifications to web page code/content
Download Test Tags and Publisher Side File
Procedures
The Publisher-Side File only needs to be placed once in each sub-domain that will display PointRoll Ads. PointRoll does not dictate the location of the file, so the publisher can place it anywhere within the sub-domain. Therefore, after this file is placed on those servers, PointRoll must be notified of the URL path of the file so the Ad Delivery System can be updated. This path information can be emailed to your PointRoll Technical Support contact or traffic@pointroll.com. After this is complete, any PointRoll Ad unit can run on those sub-domains without further publisher involvement. Any PointRoll Ad tags can then be trafficked into the publisher's ad rotation.
Summary
The Publisher-Side File is placed in each of the sub-domains that PointRoll Ads are to be served into. This is only a one-time placement for each sub-domain (not "per ad" or even "per campaign").
The Publisher-Side File is a basic HTML file that is accessed via standard HTTP.
The sole purpose of the Publisher-Side File is for proper functioning of the PointRoll Ad technology. It does not collect any information.
Details of the Ad Delivery Process Involving the Publisher-Side File
- User Comes to Page
A user navigates to the publisher's web page that contains an advertisement. - Ad Engine Serves PointRoll Tag
The web page makes a request to the ad serving engine for an ad. The ad engine serves a tag for a PointRoll Ad Unit. - PointRoll Ad Tag Looks Up Location of Publisher-Side File
When the PointRoll Tag is served, it knows it is in an IFrame and knows the sub-domain of the parent page containing the IFrame, and therefore knows the location of the relative Publisher-Side File. - PointRoll Ad Tag Sends Parameters to Publisher-Side File
The PointRoll Ad Tag then makes a standard HTTP redirect (via Port 80) to the Publisher-Side File, sending parameters to it to identify the specific ad call. - Publisher-Side File Makes Final Call for the Ad
The Publisher-Side File simply takes the call-specific parameters from the query string and makes the call for the creative. - PointRoll Ad is Served
The final creative is delivered into the IFrame within the publisher's page.
Learn more about joining our network:
To get started immediately, please contact our Trafficking, Site Acceptance, Publisher Testing division at support@pointroll.com, or call 800-203-6956.