Archive for April, 2006

in Direct Media Exchange

What is RMX Direct?

Sunday, April 9th, 2006
By Pat McCarthy
April 9th, 2006

Our last post discussed a little bit why we’re creating RMX Direct. Now it’s time to get into some of the details of what RMXD will actually do to help solve problems for publishers and help them earn more money.

We wanted a simple and easy way for publishers to work with networks on the Yield Manager platform, so we’re building a product that goes through the following initial process:

Initial Setup

  1. Sign up - The user will enter in their payment information, and the URLs for sites they want to run ads on.
  2. Creative settings - User sets their global creative banning settings for all networks they’ll work with. For example, if you don’t want dating ads, you can ban the entire dating category for all networks.
  3. Establish network relationships - At this point a publisher will be choosing which networks on Yield Manager they’d like to receive ads from. We’ll include information about each network such as revenue share, payment terms, types of payment, areas of strength, overall volume on Yield Manager, and other things we can think of to make the decision on whether to work with a network easy for the publisher.
  4. Get ad tags - You can just get one tag for each ad size to start serving ads for all the networks you are working with instead of needing to manage tags for each network.

Auctioning - Let’s say for example you’re a publisher who chooses to work with five networks. Each time you send an impression to RMXD, it will now be auctioned off to all the advertisers of all five networks you are directly working with who are interested in that type of impression. This means there is more direct competition for each impression, and in many cases this means a revenue share cut between networks that is occurring on Yield Manager now is cut out so that more money ends up going to the publisher.

Reporting - After running impressions, you can now login to RMXD again and check some stats. We plan on offering a set of most commonly run reports along with an advanced reporting option to create custom reports. We also plan on going a step further after our initial launch and offering RSS reporting, a Firefox extension to get your stats, a system tray stats application, and blogging platform plugins to view stats directly in your blogging admin interface or content management system interface. Why not see your ad stats where you want to see them?

The Future - We have lots of ideas for additional things we can add to RMXD. We’ve got some social/sharing ideas in mind, as well as all kinds of features we could add. However, we want to be careful with this. We’d like to know what users want, what they really need, and what’s really important as to not create something so complex and cluttered it’s no longer easy to use.

in API

“Backup” of production SOAP server

Tuesday, April 4th, 2006
By Ilya Martynov
April 4th, 2006

We are trying very hard to avoid breaking existing SOAP clients when releasing a new version of SOAP server. In case if the incompatible change which is known to break an existing SOAP client had to be introduced we warn our clients in advance. Still there is a chance that new production version breaks existing SOAP clients unexpectedly. To help in this case starting from version 0.16 we provide a “backup” - an instance of production SOAP server which still runs the previous version (see the annoncement for links on WSDLs). So if you happen to run into your client application being broken after a release please report the problem immediately to rmapi-users@rt.iponweb.net and switch to “backup” version. This would allow you to keep your client application working while we are fixing the compatibility problem.

in API

Release 0.16 is out

Tuesday, April 4th, 2006
By Ilya Martynov
April 4th, 2006

New APIs:

  • Added PixelService with add(), get(), update(), setCreatives(), getCreatives(), setPiggybackPixels(), getPiggybackPixels() operations. Added TargetProfile.set/getTargetPixels() API.

Updated APIs:

  • (INCOMPATIBLE CHANGE) The server doesn’t preset creative.advertiser_entity_id, campaign.advertiser_entity_id to currently logged in entity anymore when adding creatives or campaigns. It is also possible now to explicitly pass line_item.buyer_entity_id when adding a line item. Old behavior made sense for SMA-only case but doesn’t work well in the general case.
  • (INCOMPATIBLE CHANGE) As no external clients use Creative service yet we took an opportunity to break compatibility and rework this service to support more creative fields, add new validation rules and rework they way clients set creative content for creatives (add/delCreativeContent() APIs are gone). Most of the planned changes for this service are part of this release but some of them are not finished yet and will be a part of the next release. Particallary not all validation rules have been implemented and uploading supporting files is not ready yet (add/delSupportingFiles() API).

Updated documentation:

  • Region table lists IDs of countries regions belong to.
  • Mention in contact service documentation for how long sessions persist after login.

Bugfixes:

  • (INCOMPATIBLE CHANGE) Names of varios objects (advertisers, publishers, campaigns, line items, etc) were not checked to be non-empty strings.
  • Wrong error message was shown when accessing the API with session token set to NULL.

API documentation: http://api.yieldmanager.com/doc/.

WSDLs for the production version:

WSDLs for the previous production version:

Test version UI: http://api.yieldmanager.com/test-ui/.

WSDLs for the test version:

in Direct Media Exchange

Why Are We Making RMX Direct?

Saturday, April 1st, 2006
By Pat McCarthy
April 1st, 2006

It’s time to get a bit more specific about the product known as RMX Direct that we’re building here at Right Media. First, before I get into what the application specifically is, let’s do an overview of the state of the ad network and web publisher relationship. Most web publishers today work with multiple ad networks. This occurs for a number of reasons, but primarily because single networks can’t monetize all of a publisher’s impressions, networks specialize in different areas, and because publishers like to make sure they are making the most money possible and they don’t trust that one network alone will do that for them.

So, what ends up happening is publishers either create a daisy chain of networks that pass impressions they don’t want from one network to the other, or they choose to allocate a percentage of their inventory to each network based on performance.

Neither one of those solutions is truly ideal. Not to mention the other hassles that crop up like having to manage ad tags from each network, having to log in to each network to check stats, and getting paid at different times by each network. It’s a hassle.

Right Media has made a lot of progress in the last year creating a gigantic auction-based advertising marketplace called Yield Manager. Yield Manager currently has around 50 ad networks as part of this marketplace, hundreds of advertisers, and thousands of publishers. Up until this point though, publishers on Yield Manager were “owned” by a particular network, and all ads being served to them had to come through the network that “owned” them, even if it was another network’s advertiser that won that auction. While these publishers are still getting the benefit of having their inventory auctioned up to many networks and advertisers on Yield Manager, they still have had to work with multiple networks, manage multiple tags, and get paid from each network individually.
An email that I’d receive about once a week would go something like this:

“Hi, I am currently working with 5 networks that use Yield Manager to serve their ads. Is there a way I can combine this all into one thing?”

The answer has actually been “Yes, if you use your enterprise level publisher solution which does full ad serving and is overkill for most small to medium sized publishers, and it has a fee. But in your case, no there isn’t a way.”

Now, RMXD is going to solve this problem. We’ll get to how in the next post.