Version 0.07 has several new services: insertion order, line item,
publisher, site and section.

All available WSDLs are at:

• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.07/campaign.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.07/contact.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.07/creative.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.07/delivery_rules.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.07/insertion_order.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.07/line_item.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.07/publisher.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.07/section.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.07/site.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.07/target_profile.php?wsdl

Interim SVN based release with PublisherService is now live at http://ct.yieldmanager.com/ilyaphp/manage/soap/

In addition to 0.06 services it has new publisher service, with WSDL located here: http://ct.yieldmanager.com/ilyaphp/manage/soap/publisher.php?wsdl

Supported operations on publishers:

1). int add(publisher) - receives ‘publisher’ structure (see below) and creates new publisher and returns new YM’s ID

2). publisher get(int publisher_id) - receives publisher’s ID and returns ‘publisher’

3). array_of_int listAll() - returns list of all publishers ids visible to the requestor

Publisher’s businness object is a big structure with lots of fields in it. In terms of DB the publisher structure aggregates several tables (i.e. two addresses, billing info, some metadata etc). Fields, starting with ‘billing_’, stand for billing info, fields starting with ‘bank_’ is for banking data.

When new is publisher created a number of structure’s fields are ignored (i.e. created_on, id etc) - because they are set up automaticaly.

We expect this structure to change a bit in the future.

Note, that at this stage we do not support integration codese, all business objects are refferred to by YieldManager ID. It it our hope to add support for codes as well later.

For the last few years, search advertising has really been the star of the media and online world. Even though throughout the whole time CPM-based display advertising has been steadily chugging along as a very large chunk of online spending.

There are many great things about search advertising, but one problem is that it can be limiting in some ways. There is a finite amount of searches on target keywords from major engines, and so when marketers want to grow and use more budget, they’re left broadening the keyword base or raising bids. Both of those tactics often hurt their ROI.

This is one of the reasons people are predicting that CPM advertising will grow in 2006. That sure wouldn’t be a bad thing for this product.

In an article entitled “eBay Pitches eBiz, Big Advertisers Consider Online Media Auction Service,” Joe Mandese discusses the history of attempts to create auction exchanges for media, and a presentation given recently by eBay on the topic.

Since we’re not exactly publicity hounds, no one can blame Joe for not touching on the fact that we’ve built exactly what the article describes—the first and only active exchange marketplace for advertising—the Yield Manager Marketplace.

Those who know us know that we’ve been talking about this concept, and building an exchange marketplace, for the last 2 years. An article like this makes me wonder if we’re not a little too conservative when it comes to communications. The fact of the matter is that we’re operating an exchange for online media through which over 35 billion impressions will be bought and sold this month—people should know about it! Still, I’m glad that the topic is finally getting more attention.

The fact that this is being talked about is good for our industry. The more we discuss the inefficiency in today’s models of buying and selling advertising, the more likely we’ll be as an industry to find a solution that actually addresses the problem.

Kudos to those driving this discussion forward.