Shared Ad Extensions and New Features in Bulk Service

  • Article

Bing Ads introduced new Bulk Upload and Download methods for campaign management in v9 that supports the popular data exchange formats CSV and TSV. We have several customers who have already migrated to the new bulk features, and have been successfully managing their campaigns during this holiday season. Customers who had migrated to new bulk features have provided feedback on enhancements to bulk service that could improve campaign management experience in their tools. In response to our customer feedback, we are glad to announce that the following new capabilities will be available in the upcoming release of bulk which is scheduled to ship in Jan 2014.

Next version of Bulk Service supports the following new capabilities:

  1. Versioning of file format
  2. Shared Ad Extensions (AKA Libraries)
  3. Negative Id to cross-reference rows in the input file
  4. More detailed state of processing

File Format Version:

This release will introduce the versioning concept for file format. Bulk schema will support a new entity type called ‘Format Version’ to indicate the usage of the file.

Shared Ad Extensions:

The new Shared Ad Extension feature allows to create ad extensions individually, and associate the same with several campaigns and ad groups to manage the ad extension quota more efficiently. Customers seeking the shared ad extension behavior will be required to use the latest file format version (2.0) to obtain the shared ad extension behavior.

Negative ID:

Schema supports usage of negative IDs in the existing ‘ID’ column for new entities, so that those new entities can be cross referenced in associations using ‘ID’ and ‘Parent ID’ columns of their child entities.

Ex: New campaign can have ID= ‘-123’, which can be referenced as ‘Parent ID=-123’ in creating an Ad Group.

Detail state of processing:

We are also introducing two new methods called GetDetailedBulkUploadStatus and GetDetailedBulkDownloadStatus to support status element ‘PercentComplete’ which indicates the current state of file processing. These new methods replacethe usage of GetBulkUploadStatus and GetDownloadStatus which will be deprecated in the future.

The upcoming release will NOT cause any change in behavior of the API or bulk file format for existing customers. However, we strongly recommend our API Customers and Tool Providers to use the latest features.

These new features will be available in Sandbox in few weeks with corresponding documentation details in MSDN. Please stay tuned to bulk service documentationfor more details.

 

Thanks

Ravi Modalavalasa

Program Manager, Bing Ads