We’re integrated with a large number of publishers, some large enough to have their own engineering teams, and most who have limited technical resources. Although we’ve done as much as we can to isolate ourselves from the publishers’ choices, occasionally we’ll get a surprise.
We’re Guests; No Commenting on the Artwork
The publishers we work with own the page, we’re just visiting. And like any good guest, we need to be polite and respectful. Don’t like a library they’re using? Don’t like how they’ve structured their JS? Sorry, we’re guests in their homes. It’s on us to ensure smooth interoperability. It’s all too common to see broken ads which take away from the fun and utility of publisher pages by slowing down page load or distracting the user from the main purpose of the page.
This philosophy of being a good guest has informed many of our design decisions, including:
- Loading our content after the publisher’s page has loaded
- Ensuring we utilize no-conflict modes of our depencies (e.g. jQuery)
- Authoring our own no-conflict modes (if necessary)
The Wild West
- Keep Your Friends Close and Your 3rd Parties Closer
- jQuery vs jQuery
- RequireJS and jQuery - a Journey in noConflict Mode