Wednesday, 31 July 2013

Ad Exchanges and Real Time Bidding The Next Big Thing?


Ad Exchanges and Real Time Bidding The 


Next Big Thing


There is a great deal of buzz in the industry around Ad Exchanges and the technology associated with them. However, it is not well understood how they operate and what the benefits to publishers and advertisers are. In researching this topic, we found that while Real Time Bidding (RTB) receives a great deal of attention, there are other attributes of Ad Exchanges that are not widely discussed, yet have the potential to make a major impact on the digital marketing ecosystem. We’ll attempt to clarify some of the concepts used in the Ad Exchange technology stack in this article. First let’s examine traditional Ad Networks.

How Ad Networks Operate

In the Ad Network model, the building blocks are the traditional components of web advertising: Web Content Servers, Publisher Ad Servers, Advertiser (third party) Ad Servers, Database Providers, Cookies, Tracking Pixels and Content Delivery Networks (CDN).
The process generally works as follows (simplified for clarity):
User begins to load a web page.
Web page issues a request for an advertisement from the Publisher’s Ad Server which logs the request and returns a “NET TAG”.
Web page issues request to the Ad Network Server, which processes its pixel, reads and/or drops its cookie, queries its database and applies targeting (demographic, geographic, contextual, behavioral or all of the above) algorithms. It then applies the rules set in the contract with the advertiser. If it finds a profitable match it issues an ADV TAG and logs the transaction. If it does not find a match, the Ad Network may pass the request on to a partner Network, which repeats the process to determine if it has a profitable ad to display and so on until a network claims the impression. This processes typically involves multiple http requests and redirects, which impact load time negatively.
Web page processes the ADV TAG resulting in the Advertiser Ad Server either serving the ad or handing off the request to a Content Delivery Network (CDN).
The browser loads the ad, if the user hasn’t already moved on to another page.
Whew!
This architecture has evolved as the online advertising industry has matured. At this point, it has become what tech types refer to as a “kluge”- a process which is inefficient, slow to serve creative, problematic to traffic, difficult to report upon and expensive relative to the real cost of the media. Add in secondary networks, yield management techniques and third party data sources and you have a cumbersome architecture that does not scale well.

What Ad Exchanges Do

If you’ve read this far, you now understand one of the most important (if not often publicized) rationales for Ad Exchanges: Efficiency. Suppose instead of the “Round Robin” approach described above, there was a centralized mechanism for aggregating the impressions offered across multiple Ad Networks and matching them (based on the advertisers target, budget and placement requirements) with the most appropriate ads?  What if this mechanism existed in the cloud with a well understood API (application programming interface) for audience targeting data and there was dynamic auction functionality around pricing which allowed the publisher to supply his impression to the highest bidder at any given instant? Add self serve applications for ad creation, traffic, campaign management and reporting and you have the basic components an Ad Exchange or Demand Side Platform (DSP)

Real Time Bidding (RTB)

Real Time Bidding is a dynamic auction process where each impression is bid for in (near) real time versus astatic auction where the impressions are typically bundled in groups of 1,000. The potential advantages are cost efficiency, higher performance and greater granularity with targeting and measurement.

Demand Side Platforms (DSP)

Demand side platforms (DSPs) give buyers direct RTB access to multiple sources of inventory. They typically streamline ad operations with applications that simplify workflow and reporting. These products are directed at agencies, agency holding companies and large advertisers (the buyers). The technology stack that powers an Ad Exchange can also provide the foundation for a DSP, thus there is a synergy for plays in both spaces.

Supply Side Platforms (SSP)

Large publishers incorporate yield management techniques to increase ad revenue. This typically involves managing multiple networks. The SSP play uses the data generated from impression level bidding to help the publisher increase the value of his inventory by being on target. Applications to manage ad operations are also bundled into these solutions. Again, the technology is adapted from the Ad Exchange tech stack.


Obstacles to Adoption

While this technology sounds promising, there are arguments against Ad Exchanges:
Questionable ability to appropriately value premium inventory.
Devaluation of direct sales efforts.
Fear of the commoditization of inventory (allegedly suppressing price).
Suitability of addressing Branding as well as Direct Response objectives and goals.
While the jury is certainly still out, sentiments on these issues are leaning in a positive direction based upon these assumptions:
Homepage takeovers, guarantees and deep integration on major properties will continue to command premium pricing and require the efforts of direct sales teams to package, promote and manage.
Because Ad Exchanges increase reach and provide hooks for multiple third party data sources to plug in to the ecosystem, the ability of the architecture to leverage RTB functionality with accurate targeting potentiallyraises the value of inventory. Perhaps advertisers will pay more to reach consumers that have been qualified by current, actionable data and are therefore more likely to have immediate brand interest or purchase intent.
The tactical advantages of Ad Exchanges potentially make branding campaigns across premium inventory more effective by broadening reach. Additionally the tools for targeting, traffic, frequency capping, rotation and reporting are ROI enhancing to brand as well as direct response efforts.

The Players

The technology supporting Ad Exchanges is complex and expensive. In order to scale up to handle the level of traffic enterprise clients demand, software engineers often have to code tools from scratch. Open source and/or off the shelf databases just can’t handle the load.
Therefore, it’s no surprise that the big three (Google, Yahoo and Microsoft) are taking the lead in building out Ad Exchange infrastructure. Their deep benches and pockets allow them to invest the resources necessary to make technology like RTB actually work.
Yahoo’s Right Media was arguably the first out of the gate with an exchange. With broad reach across the Yahoo network it is well positioned and has recently committed to offering more premium inventory.

Google AdEx leverages the DoubleClick Ad Serving platform with RTB. As is typical with Google, the technology stack is the most sophisticated of the top tier exchanges.

Microsoft AdECN is Microsoft’s Ad Exchange for the Microsoft Media Network.

AdMeld helps premium publishers maximize revenue from their ad inventory, reduce operating costs and eliminate unwanted ads by giving publishers access to demand from ad networks, exchanges and DSPs.

PubMatic is an ad monetization and management solution which combines impression-level ad auction technology, brand protection tools and ad operations support.

The Rubicon Project offers Supply and Demand platforms with integrated API’s for data providers.

ContextWeb provides real-time contextual targeting.

AdBrite is an advertising exchange focused targeting and optimization, has real-time bidding, API functionality and a self-service account management interface.

OpenX combines ad serving and yield management with RTB.

Media Math is a demand side buying and analytics platform that aggregates the AdEx, Right Media and AdECN exchanges.

DataXu offers a real-time ad optimization platform which manages buys on an impression-by-impression basis across AdEX and Right Media.

AppNexus is single-point integration to exchanges and inventory aggregators, including Google’s DoubleClick, Microsoft’s AdECN, and others.

Turn is a demand side platform with targeting, exchange integration and analytics.

Audience Science specializes in segmentation and targeting data.

x+1 is a targeting platform for advertisers and publishers. They also build dynamically assembled 
landing pages and micro-sites based on demographic and behavioral data.

Triggit integrates with Ad Exchanges via its RTB Platform.

Invite Media’s Bid Manager is a RTB buying application.

Thanks to adexchanger.com and mikeonads.com for the knowledge.

Tuesday, 30 July 2013

Difference between DoubleClick for Publishers/DFP Premium and DFP Small Business

DoubleClick for Publisher is the overall brand then there's DFP Small Business and DFP Premium.
DFP Small business is the free product, you do need a Google Adsense account, but you don't have to run AdSense on your sites. 
DFP Small Business is a free, self-managed publishing solution that provides ad management and serving needs. The product is free for publishers who serve less than 90 million monthly impressions. 

For publishers who exceed this limit, they use the DFP premium solution, and are required to pay for their incremental ad serving volume. This solution is for publishers with larger sales teams and complex sales operations who usually require advanced feature sets, greater levels of customization, and enhanced service options from DFP Support team.

There are many features that are not available to DFP SB yet

  • 5 level ad unit hierarchy,
  • Complex key-value targeting (like exact or approx match),
  • Video ad trafficking,
  • Out-of-page/Overlay,
  • reporting on uniques, etc



But these are things that a big publisher would need as a result of billions of impression served via their DFP account.

Monday, 29 July 2013

What is Invite Media

Invite Media

Invite Media is a display advertising and exchange bidding company that was acquired by DoubleClick, a subsidiary of Google Inc. on June 3rd, 2010 for $81 million. Prior to Google's acquisition, Invite Media partnered up with AlmondNet, a data aggregator and intellectual property licensor.

A smarter, more efficient way to buy media

Invite Media is a high impact demand-side platform that enables advertisers, agencies and agency trading desks to use real-time bidding to buy and optimize online media.
Buyers can use Invite Media's technology to set up and manage automated strategies to help facilitate intelligent buying across all major sources of real-time bidded inventory, all in a single interface. With the ability to apply data from any major source, plus the freedom to create business rules for bidding and optimization, Invite Media gives buyers flexible control over campaign performance.
Top agencies and advertisers rely on Invite Media's transparent universal buying platform, Bid Manager, to use their own and third-party data while gaining efficiency and scale from an integrated workflow and reporting system.
Now backed by Google's global infrastructure, Invite Media provides the reach, scale and speed buyers need to get optimal results.

With Invite Media, you can:
·         Connect with your precise audience wherever they are
·         Gain full visibility into all costs and sites in your buys
·         Set global controls such as universal frequency capping for de-duplicated reach
·         Use real-time reporting to gain greater insights into your campaigns and customers
·         Streamline your workflow with a platform designed for speed and efficiency
·         Leverage the technology, expertise and resources of a proven partner

Sunday, 28 July 2013

Google Publisher Tag

The Google Publisher Tag is used to define available ad slots on your organization's website/network. Placing a tag on a page creates a communication path between the ad server and a user’s browser. When a page containing a Google Publisher Tag is rendered, the following sequence of events occurs:
1.     A request is made from the user's browser to the ad server for gpt.js, the tagging JavaScript.
2.     The tagging JavaScript builds and sends one or more requests (depending on whether single-request mode is enabled) to the ad server for ads tagged on the page.
3.     The ad server recognizes the ad units and any custom targeting contained within the request.
4.     The ad server selects and returns the best matching ad.
5.     The JavaScript code associated with the ad tag displays the ad on the page.


What are the benefits of using the new Google Publisher Tags?
There are multiple benefits of using these new tags:
  • Faster page loads - An asynchronous JavaScript fetch means that instead of waiting for the JavaScript to be returned from the DoubleClick servers, the page continues rendering and loads the ads into iframes when the creatives are returned from the server.
  • Google Publisher Console - The tag comes with a built-in debugging and support tool called the Google Publisher Console, which is enabled on all pages containing the Google Publisher Tag.
To activate the Publisher Console, load your webpage containing Google Publisher Tags into a browser and append ? google_console= 1 to the URL and use the keyboard shortcut Ctrl+F10 to toggle the console. Alternatively, you can append ? google_force_console= 1 to your page's URL. This causes the console to be automatically displayed when the page is loaded, rather than requiring the keyboard shortcut.
The console provides checks for common tagging errors, visual highlights of all ad units and creatives on the page to help with debugging, and an alternative point of entry into the DFP front-end.

  • Single request mode - Single request mode means that instead of sending individual ad requests to DoubleClick servers, the browser is able to send one request notifying the server of all ad units on the page. This enables advanced roadblocking and improves page load time.

Thursday, 25 July 2013

Event Tracking in Google Analytics | An Overview with Examples

The code for tracking Events corresponds to the Google Analytics version you are running on your site, either through the supported current Asynchronous Snippet before the tag or the outdated Traditional (pageTracker.) Snippet before  the tag.
·         Event Tracking is the Google Analytics component for tracking non-pageview website visitor engagement, such as: PDF downloads, dynamic engagement through AJAX, form submits that do not have a thank you page, hosted videos or visitor actions within Flash.
·         Events are triggered, recorded and sent to the Google Analytics data warehouse through OnClick javascripting. Every link you want to track separately, such as PDF download or Form Submit, set an OnClick command that also triggers Google Analytics Event Tracker.
·         Tracked Events in Google Analytics have to be classified or stored as: Categories and Action type. Both Category and Action are required and need to be defined for every Event set and tracked.

·         Each Event can also have additional meta data such as a Label and a Value. These optional attributes of a Google Analytics Event have to also be set at the same time as the Category and Action but are not required.

This post deals only with the current supported Google Analytics Asynchronous Code Snippet.

Event Tracking Code Samples

Tracking PDF Downloads with Google Analytics Event Tracking:

<a href="http://www.domain.com/example.pdf" onClick="_gaq.push(['_trackEvent', 'Whitepapers', 'Download', 'Name of PDF', 2.25]);">Download PDF Link Name</a>

The above code will track every time that specific PDF is downloaded into the Category "Whitepapers" as a Download, will track the name of the PDF and assign a value of 2.25 this number can be calculated against marketing spend to acquire a prospect that then downloads your marketing material, and generates a lead.


Event Tracking Code Components

Required:

category = top level type of event that contains all actions specific to the event, such as whitepapers vs specs
action = types of event behavior that are contained within a category, such as download

Optional:

label = name of the specific event that is captured by the action, such as PDF name
value = an number given to the action captured with the event, either value of event or counter


Event Tracking Limitations

Per visitor session only 500 (pageviews + events) interactions can be tracked. When tracking interactions or engagements within flash animations with many interaction points keep track of event tracking volume limitations.

Formatting Spotlight Activity Tag for DART for Advertisers or DoubleClick DFA

The DoubleClick DART for Advertisers (DFA) Spotlight Activity Tag is the primary conversion tracking methodology for both DART Display Ad and Paid Search Management. There are two types of Spotlight Activity Tags: Counter (which utilizes the counter type: standard, unique, per session) and Sales. Included are examples of both types of Spotlight Activity Tags in order to illuminate the differences between them. These will be dissected in order to highlight the similarities and differences between the two types of Activity Tags. 


We recommend using the Counter Tag format for Lead Generation "Thank You" page tracking and the Sales Tag format on eCommerce receipt pages.


Spotlight Counter Activity Tag: 
<img src="http://ad.co.doubleclick.net/activity;src=1234567;type=abcde123; cat=fghij456;u1=[friendlyname1];u2=[friendlyname2];ord=[Random Number]?" width="1" height="1"/>
Spotlight Sales Activity Tag: 
<img src="http://ad.co.doubleclick.net/activity;src=1234567;type=abcde123; cat=fghij456;u1=[friendlyname1];u2=[friendlyname2];qty=[Quantity]; cost=[Revenue];ord=[OrderID]?" width="1" height="1"/>

Anatomy of a Spotlight Activity Tag: 
<img src="http://ad.co.doubleclick.net/activity;src=1234567;type=abcde123; cat=fghij456;u1=[friendlyname1];u2=[friendlyname2];qty=[Quantity]; cost=[Revenue];ord=[OrderID]?" width="1" height="1"/>
Elements shared by both Tag Types:

img src: This the typical HTML image tag. The src parameter identifies the URL where the image is located for the Spotlight Tag it is the tracking pixel which is a 1x1 GIF.

ad.co.doubleclick.net: This is the URL of the DART ad server.

co: This is a country code for the ad server tracking the conversion event associated with the Spotlight Tag. DART DFA employs the standard two-letter country codes denoted through the IOS (International Organization for Standardization). For those advertisers in the United States, a country code is not necessary and the server URL is going to be   ad.doubleclick.net

activity: the final URL location parameter which specifies this type of tag as a Spotlight Activity Tag.

src=1234567: This is the advertiser to whom to attribute the conversion to. This value will always be your advertiser ID.

type=abcde123: This variable denotes the advertisers activity group for the particular Spotlight Tag. This has to be eight characters. Typically this is the first 5 letters of the activity group with an appended 3-digit random number. 

cat=fghij456: This variable denotes the advertisers activity tag string for the particular Spotlight Tag. This has to be eight characters. Typically this is the first 5 letters of the activity name with an appended 3-digit random number.  

u1=[friendlyname1];u2=[friendlyname2]: These are Key-values where any data can be passed back to DART. These custom variable have to fall with the brackets.

Here are the elements unique to sales activities:

qty=[Quantity]: This important eCom parameter is used to count sales activity. 
    * For counting transactions as a whole, regardless the number of items ordered then, the parameter is always qty=1.
    * For counting individual items or units sold, then the parameter is always going to be qty=[Quantity], at this point the Quantity has to be dynamically inserting by the back end shopping cart receipt generating logic and is has to be coded by the advertisers IT.

cost=[Revenue]: Same as with Quantity the Revenue figure has to be dynamically inserted by the back end shopping cart receipt generating logic and is has to be coded by the advertisers IT. The Revenue figure is the sale amount once the order or purchase has been processed by the shopping cart and is to be found on the receipt or order confirmation.

ord=[orderID]: As with the previous two variables the Order ID has to be dynamically inserted by the back end shopping cart receipt generating logic and is has to be coded by the advertisers IT. Each order needs to have a trackable unique OrderID.

Tuesday, 23 July 2013

How to Traffic Mediaplex Creatives in DoubleClick DFP

Mediaplex is a third party ad serving service – you’re bound to be asked to traffic MediaPlex creatives at some point, so here are the guidelines.
Mediaplex tags do not come with macros already inserted, so you will need to insert them yourself: use random numbers (%n) to bust caching and %c count clicks. The tags should arrive with detailed instructions as to where to insert these elements.
In DFP, you will need to traffic these tags as custom rich media creatives: once you have created the campaign, create a new ad and select “Standard” as product type, fill in the ad details, then assign to it a “custom” creative where you can enter the tags discussed below.

1) Standard/Banner tags
In general the tags will arrive in a format such as this for a simple Ad Creative ( Image GIF or JPG):
<a href=”http://altfarm.mediaplex.com/ad/ck/1234-12345-1234-1?mpt=[CACHEBUSTER]“>
<img src=”http://altfarm.mediaplex.com/ad/bn/1234-12345-1234-1?mpt=[CACHEBUSTER]” alt=”Click Here”></a>
This A HREF/IMG SRC combination maybe trafficked in the Rich Media field in DART or (more simply) as a Redirect Creative.
To traffic as a Redirect creative simply extract the 2 URLs from the code above, replace [CACHEBUSTER] with %n and insert the appropriate URLs into your redirect creative. The A HREF URL is the Click Through and the IMG SRC URL is the Image Redirect.
e.g. Redirect URLs for Sample Mediaplex Creative.
Click Through = http://altfarm.mediaplex.com/ad/ck/1234-12345-1234-1?mpt=%n
Image = http://altfarm.mediaplex.com/ad/bn/1234-12345-1234-1?mpt=%n
Alternatively, if you wish to traffic your ad in the Rich Media field you should take the entire Mediaplex code fragment, replacing %n where necessary. As the creative is being set in the Rich Media field it is necessary to indicate to DART where the clickthrough is to be counted by placing the %c…%3a%2f%2f macro on the A HREF URL.
e.g. Rich Media Code for Sample Mediaplex Creative.
<a href=”%chttp%3a%2f%2faltfarm.mediaplex.com/ad/ck/1234-12345-1234-1?mpt%n”>
<img src=”http://altfarm.mediaplex.com/ad/bn/1234-12345-1234-1?mpt=%n” alt=”Click Here”></a>
For Richmedia ads ( such as Flash banner,expandables, popups, layers …), tags will more often be sent as Iframe/Ilayer, Iframe/Javascript or Javascript only tags.
To ensure accurate tracking, you are required to implement a Cache Buster on your end. Please replace all occurrences of [CACHEBUSTER] in the ad tags below with our %n macro.
To track clicks using the iframe/ilayer/script tags provided, please insert our redirect string %c as the value following “mpvc=”.
Alternatively for the A HREF/IMG call in these tags, do the same modifications as described just above for trafficking the redirect tag in the Richmedia field.
2) IFRAME/ILAYER tags
Initial code:
<!– Begin of Mediaplex Iframe/Ilayer insertion order fragment –>
<nolayer>
<iframe src=”http://altfarm.mediaplex.com/ad/fm/0-0-0-0?mpt=[CACHEBUSTER]&mpvc=” width=728 height=90 marginwidth=0 marginheight=0 hspace=0 vspace=0 frameborder=0 scrolling=no bordercolor=”#000000″>
<a href=”http://altfarm.mediaplex.com/ad/ck/0-0-0-0?mpt=[CACHEBUSTER]“>
<img src=”http://altfarm.mediaplex.com/ad/bn/0-0-0-0?mpt=[CACHEBUSTER]” alt=”Click Here” border=”0″></a>
</iframe>
</nolayer>
<ilayer src=”http://altfarm.mediaplex.com/ad/fm/0-0-0-0?mpt=[CACHEBUSTER]&mpvc=” width=728 height=90></ilayer>
<!– End of Mediaplex Iframe/Ilayer fragment –>
Modified code:
<!– Begin of Mediaplex Iframe/Ilayer insertion order fragment –>
<nolayer>
<iframe src=”http://altfarm.mediaplex.com/ad/fm/0-0-0-0?mpt=%n&mpvc=%c” width=728 height=90 marginwidth=0 marginheight=0 hspace=0 vspace=0 frameborder=0 scrolling=no bordercolor=”#000000″>
<a href=”%chttp%3a%2f%2faltfarm.mediaplex.com/ad/ck/0-0-0-0?mpt=%n”>
<img src=”http://altfarm.mediaplex.com/ad/bn/0-0-0-0?mpt=%n” alt=”Click Here” border=”0″>
</a>
</iframe>
</nolayer>
<ilayer src=”http://altfarm.mediaplex.com/ad/fm/0-0-0-0?mpt=%n&mpvc=%c” width=728 height=90></ilayer>
<!– End of Mediaplex Iframe/Ilayer fragment –>
3) IFRAME/JAVASCRIPT tags
Initial code:
<!– Begin of Mediaplex Iframe/JavaScript insertion order fragment –>
<iframe src=”http://altfarm.mediaplex.com/ad/fm/0-0-0-0?mpt=[CACHEBUSTER]&mpvc=” width=728 height=90 marginwidth=0 marginheight=0 hspace=0 vspace=0 frameborder=0 scrolling=no bordercolor=”#000000″>
<script language=”JavaScript1.1″ src=”http://altfarm.mediaplex.com/ad/js/0-0-0-0?mpt=[CACHEBUSTER]&mpvc=”>
</script>
<noscript>
<a href=”http://altfarm.mediaplex.com/ad/ck/0-0-0-0?mpt=[CACHEBUSTER]“>
<img src=”http://altfarm.mediaplex.com/ad/bn/0-0-0-0?mpt=[CACHEBUSTER]” alt=”Click Here” border=”0″></a>
</noscript>
</iframe>
Modified code:
<!– Begin of Mediaplex Iframe/JavaScript insertion order fragment –>
<iframe src=”http://altfarm.mediaplex.com/ad/fm/0-0-0-0?mpt=%n&mpvc=%c” width=728 height=90 marginwidth=0 marginheight=0 hspace=0 vspace=0 frameborder=0 scrolling=no bordercolor=”#000000″>
<script language=”JavaScript1.1″ src=”http://altfarm.mediaplex.com/ad/js/0-0-0-0?mpt=%n&mpvc=%c”>
</script>
<noscript>
<a href=”%chttp%3a%2f%2faltfarm.mediaplex.com/ad/ck/0-0-0-0?mpt=%n”>
<img src=”http://altfarm.mediaplex.com/ad/bn/0-0-0-0?mpt=%n” alt=”Click Here” border=”0″>
</a>
</noscript>
</iframe>
4) JAVASCRIPT only tags
Initial code:
<!– JavaScript Only –>
<script language=”JavaScript1.1″ src=”http://altfarm.mediaplex.com/ad/js/4214-21200-8666-0?mpt=[CACHEBUSTER]&mpvc=”></script>
<noscript>
<a href=”http://altfarm.mediaplex.com/ad/ck/0-0-0-0?mpt=[CACHEBUSTER]“>
<img src=”http://altfarm.mediaplex.com/ad/bn/0-0-0-0?mpt=[CACHEBUSTER]” alt=”Click Here” border=”0″></a>
</noscript>
Modified code:
<!– JavaScript Only –>
<script language=”JavaScript1.1″ src=”http://altfarm.mediaplex.com/ad/js/0-0-0-0?mpt=%n&mpvc=%c”>
</script>
<noscript>
<a href=”%chttp%3a%2f%2faltfarm.mediaplex.com/ad/ck/0-0-0-0?mpt=%n”>
<img src=”http://altfarm.mediaplex.com/ad/bn/0-0-0-0?mpt=%n” alt=”Click Here” border=”0″>
</a>
</noscript>

Change to AdWords Enhanced CPC removes bid cap to account for location & audience

  AdWords users will notice a new alert in their accounts notifying them of changes to Enhanced CPC bidding.  The notice...