-
So this is some really exciting news about a project I've been working on at the washingtonpost that went live earlier this year: active script-level interventions in web ads. Basically, we're going in, checking for bad performing code and fixing it before it can impact users. WapoEngineering/1133359994005598209Permalink On twitter.com
♻️ 11 Retweets
❤️ 63 Favorites
Mood +1 🙂
-
Details are at the link, but this is a project that comes out of experimentation I've been working on for years. When ads have a negative, but non-malicious, impact on the user experience, publishers often feel helpless to fix what's coming through the ad frame. But not us.Permalink On twitter.com
❤️ 9 Favorites
Mood -4 🙁
-
I note this in the post: over one-third of the ads that reach our users in the iOS app were using code that caused excessive CPU use! That's a lot of ads! Ads that had a significant impact on the user experience. Ads that now continue to work fine, & without the negative impactPermalink On twitter.com
❤️ 7 Favorites
Mood +2 🙂
-
Active, real-time, intervention in ad code execution is a huge deal, and to do so and see it have no negative impact on the ads themselves opens up a whole new realm of possibilities as to what we can do with technology to make the ad experience better, everywhere!On twitter.com
❤️ 5 Favorites
Mood +1 🙂
-
I'm very excited about how our protocol here opens up new possibilities on a very fundamental level for how we work with ad code at the point it impacts users! To see this rolled out and working realizes the next step towards a very different way for us to work with ad tech.Permalink On twitter.com
❤️ 4 Favorites
Mood +3 🙂
-
Permalink
On twitter.com
❤️ 5 Favorites
Mood 0