Je viens de rentrer d’une visite Ã Paris. If that doesnâ€™t read as, â€œIâ€™ve just got back from a visit to Parisâ€ then youâ€™ll know O-levels werenâ€™t as good as the rose-tinted view of the dumming down brigade suggests. That, or Iâ€™ve just forgotten everything Mrs Taylor taught me about cats sitting on tables or buying one-way tickets to La Rochelle.
A Paris, j’ai rencontrÃ© des gens trÃ¨s sympathiques. But, I wasnâ€™t there just to be friendly, I was there for the second part of the pan-European tour for Microsoft Advertisingâ€™s regular outreach sessions, MSA Today. And, in case youâ€™re imagining musician-on-a-bus type touring, it was date two of two (the first being last week in the UK) and so a â€˜tourâ€™ is perhaps a little â€œlicence artistiqueâ€ on my part.
I was part of a group of people showcasing Microsoft Advertisingâ€™s offerings to publishers: a set of tools that help media ownerâ€™s understand advertising inventory; delivery premium advertising content and monetise remnant/discretionary inventory. Itâ€™s a neat set of tools that you can find more about here.
To give a bit more background to what I noted last week, while working on the presentation (which has been made available over at Microsoft), I became increasingly convinced that one particular piece of terminology was incorrect: the industry refers to some of that technology as an ad-server and, for most publishers, that name isnâ€™t accurate. And before Iâ€™m accused of being pedantic, I think we (those of us work in the business of helping publishers manage advertising inventory) are doing ourselves a disservice by not properly describing what weâ€™re doing and what value we are bringing.
I appreciate that my distinction â€“ certainly in technical terms â€“ is overly specific. But for most publishers and ad-server can be said to do around about six things and in the vast majority of cases the publisher system never actually serves an advertisement (my definition here requires the ad-sever to hold the advertising creative and provide the asset or the URL of the asset back to the userâ€™s browser). And I am talking about publisher ad-servers here; the equivalents for buy-side, optimisation or network players in this space might â€˜serveâ€™ the ad more often than not.
And now youâ€™re asking â€œPourquoi est-ce important?â€ (or something similar). I believe the serving aspect diminishes the value because itâ€™s seen as a technical not a business process. Not that it should, the development and innovation behind serving digital advertisements is often overlooked but nonetheless weâ€™re dealing with realities in this small space of the industry.
A publisher needs a system that provides order management; that provides inventory analysis (both pre and post-sale); provides workflow tracking for the ad operations team; provides reporting and insight on delivery, sales and finance and, finally, makes the decision on which advertisement should be shown through fast analysis of targeting rules and the browserâ€™s request. In the world in which we operate today, at the point of selection the publisherâ€™s system hands-off responsibility for delivery to the advertiser (buy-side) or networkâ€™s delivery system which takes responsibility for telling the browser where to load the ad from.
When we take publisher tools into a multi-platform world (which, to some extent was the point of my pitch for Microsoft) weâ€™re taking them further and further away from having responsibly for â€˜servingâ€™. In the IPTV world, in the online video world and, to a large extent, in the mobile world publisher tools are making a decision and letting something else do the technical side of the delivery. This is not to play down the important of solid, reliable and timely delivery but itâ€™s just not how publisher â€˜ad-serversâ€™ have evolved. In the cable television space weâ€™re already talking about a legacy web â€˜ad-serverâ€™ as being a ad-decision service and that, more accurately, reflects what weâ€™re doing.
Again, I am trying not to be pedantic about this but selection, targeting, analysis, prediction and workflow management are sophisticated tools that power publisherâ€™s businesses. The serving is really the last item, admittedly vital, in the chain but often it is not done by the publisherâ€™s system as we know it today. Why is it not a referred to as a delivery analytics platform or a decisioning system?
I really do wonder if we are doing ourselves a disservice in underplaying the business systems weâ€™re providing. Back when we were just rotating ads every few seconds, and I once worked on a system which selected the ad based on the numerical value of the second you requested it, our tools were primarily a mechanism to deliver. Now they are a mechanism to mange, process, refine, analyse and invoice. Systems have been â€“ rightly â€“ integrated into CRM and billing systems as well as into content management and analytics platforms. The value a publisher â€˜ad-serverâ€™ brings is infinitely better than those systems of old yet our terminology hasnâ€™t changed.
As an industry we need to be better at highlighting our real value. I donâ€™t believe â€˜ad-serverâ€™ serves is well any longer. Itâ€™s time to change.
Part One of this piece was written after the UK version of the presentations and can be read in That’s Not An Ad-Server.
Disclaimer: the views here are my own and are not necessarily the opinions of my employer (who sent me) nor customers (who I spoke to while there). You have read the full disclosure, haven’t you?