When 3rd Party AdTags Get Amended After Quality Assurance

October 22nd, 2009 | Tags:

How often have you received tags through, QA’d them with your tool of choice and then trafficked them only to find out a day or so later that they’ve stopped working or worse are causing usability issues on your site. You are not alone and even better, it’s may not be your fault either.

A recent issue arose when I got a phone-call at 5.45am with one of Editorial staff complaining that an ad was ‘breaking’ our frontpage. Upon checking this ad (which was indeed ‘breaking’ the page) we see an ad with a text string for a MetrixLab url directly underneath it.

Here’s the bad ad:
Bad MPU... Bad Bad MPU!!!!

Very strange and certainly something that would have shown up in testing/QA. Evidently a user of the 3rd Party Adserver had gone back into the order after sending us the tags and amended them long after we had QA’d and trafficked them into our own Adserver. The issue here is 3rd party ad-networks who allow the amendment of their ads AFTER they’ve been tested and passed by the Publisher’s AdOps team. We fixed the order and all was well by 6.00am however this highlights a dangerous and unregulated practice by Agency Traffickers.

Here are some of the issues that this practice can expose your business to and why allowing tag amendment post trafficking is a very bad idea indeed:

  1. Security: Allowing the post traffickign amendment of tags is siomply asking for potential security problems. Whether is XSS, Malware, Cookie hijacking or whatever the latest technique the script-kids have up their sleeves.
  2. Client branding: When you traffic your ads you’re responsible to make that they work correctly on your site. Any changes after that may impact on to the client’s own brand by showing the ads in unfavourably or not showing them at all.
  3. Lost inventory. The ads are not showing correctly, the client isn’t getting what they’ve paid for and you’re using precious inventory up delivering bad tags, someone’s got to pay.
  4. Publisher’s reputation: Having an ad on your homepage looking like it’s been trafficked by a 3 year old is no going to win you any favours in the board room.

So, how do we make sure that this either a] doesn’t happen again or b] keep an eye on tag changes? well, there’s a coupe of ways.

  1. Enforce a Client sign-off procedure. Get the Agency to contractually agree no changes will be made after tags have been sent to your Trafficking Department.(ideal)
  2. Enforce a Client change alert procedure. If you allow your clients to change tags after trafficking then have them agree to inform you of all changes as and when they make them. (will ultimately fail)
  3. Have someone check each tag each day. (labour intensive)
  4. Build a tool which checks for changes in tag response code. (complicated)

I’ve opted to go for option 4 and will be building a tool which will be able to monitor changes in 3rd party adtags and alert users as and when these changes occur. If you’d like to test this out, please drop me a line or leave a message here and I’ll contact you back. Expect something to be visible at http://tagwatcher.adtools.co.uk/.

Share on Twitter
No comments yet.
You must be logged in to post a comment.
a d v e r t i s e m e n t