Adplayer FAQ
- What browsers are supported?
- What sizes/delivery are supported?
- What if I don’t add information to the chain?
- What about a noscript solution?
- How do I add my content?
- Is there mandatory metadata?
- Does my adserver support AdPlayer?
- How would I change the icon?
- How do I use the API?
- How is the Opt Out process be handled and confirmed?
- Does it work with iFrames?
- How do you ensure the the last partner in the chain fires the AdImpression event?
- How to change the default ids and class names to prevent naming conflicts?
All major browsers are supported. Tested on IE 6+, FF 3.6+, Opera 10+, Chrome, Safari 5. In addition, testing has been done on mobile OS browsers; Android and iOS.
All types of display advertising are supported. We are looking at ways to support in-player video in the future, as well as mobile solutions.
It is not required that every or any party add to the chain.
This is not meant to support non JS environments, which most users support.
The AdPlayer API provides the ability to add information. Please see the API documentation on implementation details.
No.
This solution was designed to work with any adsever, but will require that JS files be manually changed for now. ADTECH is looking to support this solution with it’s flexible creative UI, for now. Other vendors are encouraged to also build hooks into their systems to support this framework.
The default location of the icon is on the top right, but can altered by chaning the CSS file.
See intra-code documentation.
One click opt out can be instituted or you can direct the users to an opt-out website if you prefer.
Yes, we have designed the product to support iFrames, with both a stub file based solution for breaking out of the frame and a solution built not to need to support breaking out of the frame.
We are looking at support for this concern, and hope to have a guaranteed method with a fallback in the near future.
The AdPlayer API allows the ability to listen to events fired across an AdPlayer delivery chain. When an impression, or any event, is tracked through the AdPlayer, all subscribers to this event will be notified. Please see the API documentation on implementation details.
By default, all element ids and class names generated by the AdPlayer will be prefixed with the string adplayer followed by a dash (-). Please inspect the style.css file to see the results.
.adplayer-privacyPanel {
/* some style definitions */
}
To prevent naming conflicts on your website, it is possible to change the default prefix string. To do that, you have to invoke the following command before the AdPlayer will be instantiated. This setting will be stored globally for the page impression lifecycle.
$ADP.Util.cssPrefix = 'myCustomPrefix';
Please note, that it is necessary to modify the stylesheet files (style.css and style-ie.css) accordingly.
.myCustomPrefix-privacyPanel {
/* some style definitions */
}