iFrames, JavaScript and Ad Delivery

The type of ad delivery a site uses can have far reaching impacts.  Everyone’s had a conversation with the Content or IT team that started Your ads are making the site …!”  This is usually followed by any one of a number of complaints: slow; install malware; totally unusable; leak all of our audience data or two-hundred-thousand pixels wide.   When faced with such a barrage, Ad Ops is forced to not only identify the cause of the problem but also mediate a solution.    

Conversely, many Ad Ops teams spend considerable time insuring ad creatives behave properly.  Expanding ads that don’t expand, companion ads that don’t cooperate with one another, and third-party reporting discrepancies are a few examples of the many integration challenges. The trend toward increased use of remnant networks and highly interactive creative only exacerbate these problems.  

Ad Delivery is the technical mechanism by which banners are inserted onto a page.  Although server-side delivery is common in mobile contexts, typically ads are inserted client-side using either Javascript, Iframes or a combination of the two.  As they relate to the challenges facing Ad Ops teams, each of these techniques has its own advantages and disadvantages. 

Our upcoming Webcast: iFrames, JavaScript and Beyond: What it means for delivery will equip you with the information you need to help you choose between these different techniques.  Topics will include:

  • A summary of the various implementations available including standard tagging, friendly iframes and asynchronous script tags.
  • The pros and cons of each Ad Delivery technique including compatibility, performance, security and data leakage. 
  • Use real-time, end-user monitoring to
    • Guard your audience information.
    • Measure real-world performance.

Visit the event page for more information or to register up for the Webcast: iFrames, JavaScript and Beyond: What it means for delivery.