Help save net neutrality! Learn more.


Brendan Riordan-Butterworth

These files are of note:

File Details
./src/js The Javascript files required to be hosted on a CDN. This includes both the host source files and the external side source files.
./src/html This holds the external boodstrap document that SafeFrames render the ad into. This file MUST be located in a different domain than the publisher site to benefit from the IFrame jail domain behavior SafeFrames provides. For testing purposes your dev can use the same domain.
./tests Included here are many sample documents that demonstrate how SafeFrames can be implemented. These should serve as a rough guide to embedding SafeFrames in your site.


This sample demonstrates the simplest implementation of SafeFrames. There are three ad areas - one with literal HTML, one with a script file that serves the ad, and one that references a URL to a file that renders the ad. At the bottom is the basic configuration code required by SafeFrames.


This sample embeds an ad that utilizes the various features of the external side of the SafeFrames API, like ad expansion and tests for viewability.


This sample shows how SafeFrame ads can be rendered without using SafeFrame tags, but instead just having a defined region for the ad and utilizing Javascript to initialize the SafeFrame ad region.

Adding SafeFrames to your site

1. Host Resources

Place all files from "./src" directory on a website hosted on an external domain from the publisher site.

2. Update Script-Includes

Add the SafeFrame source script tags to your site pages. This package does not include a final optimized and minified version of the framework, so you need these three script includes:

<script type="text/javascript" src=""></script>
<script type="text/javascript" src=""></script>
<script type="text/javascript" src=""></script>

3. Update Specific Elements

Identify the html element where ads will be rendered. Know that this element is replaced by the SafeFrame - not rendered into. Any formatting of this element will be lost.

<div id="tgtLREC"></div>

4. Add Script

Add script to the publisher page that configures and boots the SafeFrame ads.

(function() {
    var conf    = new ${
        renderFile:        "",
                id:      "LREC",
                dest:    "tgtLREC",
                w:       300,
                h:       250

    var posMeta        = new $,"rmx",{foo:"bar",bar:"foo"});
    var pos            = new $"LREC", "<h1>Hello World</h1>", posMeta);



Wiki: Home


  • David Levine

    David Levine - 2014-10-12

    Are the includes missing the version number (e.g. 1-1-0) from the path?

  • Chris Cole

    Chris Cole - 2014-10-13

    Yes, in a real deployment you should include the version number in the path where you place your copy of the files on the CDN. The sample url should really be more like:

    We don't currently provide a hosted CDN for the framework. The expectation is that publishers will be able and desire to host via their own CDN and CDN domain.


Log in to post a comment.