Release Notes

 

For information about the changes to the Bing Ads services for each release, see the following sections.

For information about the changes to the Bing Ads services included in this release, see the following sections.

Bing Ads API Version 11 Preview

System_CAPS_ICON_important.jpg Important

This is preview documentation for Bing Ads API Version 11, which is currently only available in the sandbox environment. Features in sandbox are subject to change prior to general availability in the production environment. Bing Ads API Version 11 release to production is planned for the first week of May 2017, so stay tuned for more details in the coming weeks.

A preview of the Bing Ads API Version 11 is released to sandbox. For more details, see Migrating to Bing Ads API Version 11 and Version 11 API Reference.

Bing Ads PHP Software Development Kit (SDK)

The Bing Ads PHP SDK is now available.

For details please see the blog post and Getting Started Using PHP with Bing Ads Services.

For information about the changes to the Bing Ads services included in this release, see the following sections.

Campaign and Ad Group Languages

System_CAPS_ICON_note.jpg Note

Not everyone has this feature yet. If you don’t, don’t worry. It’s coming soon.

Starting in late Q1 or early Q2 calendar year 2017, Bing Ads will begin piloting a new feature to support multiple languages at the campaign level. If languages are set at both the ad group and campaign level, the ad group-level language will override the campaign-level language. The customer is enabled for the pilot if the GetCustomerPilotFeatures response includes pilot number 310.

IMPORTANT: Pilot participants will be able to set multiple languages at the campaign level, and will be able to delete the ad group level language. If your application depends on ad group language being set, then you must prepare for the possibility that ad group language will be empty. More specific dates and implementation details will be provided later through the Bing Ads API Blog, and in the meantime you should update your application right away to support the change.

Also note that as a one time migration when the customer is added to pilot, campaign languages are set to the union of all individual ad group languages. For example if you have three ad groups with language set to English, German, and French, then at the time of pilot enablement this campaign's languages will be set to a list including English, German, and French.

Bulk Version 10

For details about how to add and update campaign and ad group languages using the Bulk API, see the Campaign and Ad Group reference documentation.

Campaign Management Version 10

For details about how to add and update campaign and ad group languages using the Campaign Management API, see the Campaign and AdGroup reference documentation.

New Reporting Columns for Bing Shopping Campaigns

The AdDistribution and TopVsOther columns have been added to the ProductDimensionPerformanceReportColumn value set. The AdDistribution column has been added to the ProductPartitionPerformanceReportColumn value set.

Software Development Kit (SDK) Updates

The Bing Ads .NET, Java, and Python SDKs are updated with support for bulk upload of remarketing lists using the BulkRemarketingList class. Upload is already supported by the Bulk service, and now the SDK is also enabled.

For information about the changes to the Bing Ads services included in this release, see the following sections.

Remarketing List Exclusions

Remarketing in Paid Search lets you improve your return on investment by optimizing your campaigns for specific audiences, which are the people who have visited your website before. In a previous release we only supported ad group remarketing list associations. Support is now added to the Campaign Management API for ad group remarketing list exclusions. For example you might want to include all users who visited a page within the last 60 days but not those who visited last week. For more information about Remarketing APIs, see the UET and Remarketing Guide.

System_CAPS_ICON_note.jpg Note

Not everyone has this feature yet. If you don’t, don’t worry. It’s coming soon.

System_CAPS_ICON_note.jpg Note

Remarketing list exclusions are not supported with the Bulk API. You can use the Campaign Management API to set exclusions.

Campaign Management API Version 10 for Remarketing List Exclusions

The IsExcluded element of the AdGroupRemarketingListAssociation object is now supported. If this element is set to True, then the AdGroupRemarketingListAssociation is an exclusion, and otherwise the audience is included.

To add, get, update, or delete the AdGroupRemarketingListAssociation between your remarketing list and ad group (whether associations or exclusions), use the respective AddAdGroupRemarketingListAssociations, GetAdGroupRemarketingListAssociations, UpdateAdGroupRemarketingListAssociations, and DeleteAdGroupRemarketingListAssociations operations.

System_CAPS_ICON_note.jpg Note

With GetAdGroupRemarketingListAssociations, the inclusive ad group remarketing list associations will always be returned. If you set the ReturnExclusions request element to True then ad group remarketing list exclusions will also be returned in the list of results.

For information about the changes to the Bing Ads services included in this release, see the following sections.

Add and Modify Remarketing Lists

Remarketing in Paid Search lets you improve your return on investment by optimizing your campaigns for specific audiences, which are the people who have visited your website before. In a previous release we only supported adding and modifying the ad group remarketing list associations. Support is now added to the Campaign Management and Bulk APIs for adding, updating, and deleting remarketing lists. For more information about Remarketing APIs, see the UET and Remarketing Guide.

Bulk API Version 10 for Remarketing Lists

Upload support is added for the Remarketing List Bulk record.

The Template field is added for both Bulk download and upload. Previously the Template field was not included in the downloaded Remarketing List record. You can use the Template field to set the remarketing rule with conditions used to determine who to add to your remarketing list. For example you can set custom events or page visitors rules.

Campaign Management API Version 10 for Remarketing Lists

The respective AddRemarketingLists, UpdateRemarketingLists, and DeleteRemarketingLists operations are supported for adding, updating, and deleting RemarketingList objects.

The Rule element is added to the RemarketingList object. A rule includes conditions used to determine who to add to your remarketing list. You can choose one of the four types of rules to target different audiences: CustomEventsRule, PageVisitorsRule, PageVisitorsWhoDidNotVisitAnotherPageRule, and PageVisitorsWhoVisitedAnotherPageRule. The Rule element is not returned in the RemarketingList object by default. You must include Rule in the optional ReturnAdditionalFields flags when calling the GetRemarketingLists operation.

Dynamic Search Ads

Dynamic Search Ads are coming to Bing Ads. You will be able to create a new type of campaign where the ad copy is automatically generated from the content on your website. A preview of the Bulk APIs are now available as described in the next section. A preview of the Campaign Management APIs for DSA was released in September.

System_CAPS_ICON_note.jpg Note

Not everyone has this feature yet. If you don’t, don’t worry. It’s coming soon.

Before you can use dynamic search ads, you must upgrade to Final Urls. For more information, see URL Tracking with Upgraded URLs.

Bulk API Version 10 for Dynamic Search Ads

The following Bulk records are added for managing dynamic search ads campaigns.

To get started with dynamic search ads, first you'll need to define a Campaign record with the Campaign Type field set to DynamicSearchAds. When you create the campaign, you'll also need to specify the Domain Language and Website fields.

Next, define an Ad Group within the dynamic search ads campaign. You can add one or more Ad Group Dynamic Search Ad Target records for the parent ad group that helps determine whether or not to serve dynamic search ads.

If you want to exclude certain portions of your website, you can add negative targets at the campaign and/or ad group level using the respective Campaign Negative Dynamic Search Ad Target and Ad Group Negative Dynamic Search Ad Target records. The Campaign Negative Dynamic Search Ad Target at the campaign level applies to all ad groups within the campaign; however, if you define ad group level Ad Group Negative Dynamic Search Ad Target, the campaign target is ignored for that ad group.

For any of the Ad Group Dynamic Search Ad Target, Ad Group Negative Dynamic Search Ad Target, and Campaign Negative Dynamic Search Ad Target records, you can choose whether you want the target argument to match partial URLs, page content, page title, or categories that Bing thinks applies to your website. To discover the categories that you can use for targets (positive or negative), call the GetDomainCategories operation with the Ad Insight service.

Finally you can define a Dynamic Search Ad record assigned to the ad group. The ad title and display URL are generated automatically based on the website domain and language that you want to target.

Geographical Location Codes Breaking Changes

Starting Monday December 19th, we require updated target codes for the US postal codes listed below. If you have targets defined in one or more of these locations, please make sure to update them in your application so that your ads may serve correctly in these locations. If you attempt to add or update targets with the deprecated codes, the operation will return an error. When you retrieve targets the new target code will be returned.

Postal CodeDeprecated Target CodeNew Target Code
0380403804, ME US03804, NH US
2038920389, MD US20389, DC US
2031020310, VA US20310, DC US
2040620406, VA US20406, DC US
2020720207, MD US20207, DC US
2033020330, VA US20330, DC US
4529845298, KY US45298, OH US
4527745277, KY US45277, OH US
2006920069, VA US20069, DC US
2004120041, VA US20041, DC US
2059920599, MD US20599, DC US
2045320453, VA US20453, DC US
2007020070, VA US20070, DC US
2020620206, VA US20206, DC US
2030120301, VA US20301, DC US
2035020350, VA US20350, DC US
2023320233, MD US20233, DC US
4084340843, KY US40843, VA US
2005820058, MD US20058, DC US

Please reach out to support, the Bing Ads API Development Forum, or your account manager if you have any questions or concerns.

Get Geographical Location Codes for Targeting

The GetGeoLocationsFileUrl operation is now available with the Campaign Management service. The operation returns a temporary URL that you can use to download a file that contains the supported geographical location targeting codes.

New Reporting Columns for Bing Shopping Campaigns

The BenchmarkBid, BenchmarkCtr, ImpressionLostToBudgetPercent, ImpressionLostToRankPercent, and ImpressionSharePercent columns have been added to the ProductDimensionPerformanceReportColumn and ProductPartitionPerformanceReportColumn value sets.

Software Development Kit (SDK) Updates

The Bing Ads .NET, Java, and Python SDKs are updated with support for the following features.

  • The Campaign Management service proxies are updated to support adding and updating remarketing lists. Note: The SDK class BulkRemarketingList does not yet support the required Template field, and therefore the SDK cannot be used for bulk upload. Support will be added in early calendar 2017.
  • The Campaign Management service proxies are updated to support the GetGeoLocationsFileUrl operation.
  • The Reporting service proxies are updated to support new columns for Bing Shopping campaigns.
  • The BulkAdGroupDynamicSearchAdTarget, BulkAdGroupNegativeDynamicSearchAdTarget, BulkCampaignNegativeDynamicSearchAdTarget, and BulkDynamicSearchAd objects are added to the SDK for reading and writing the corresponding Dynamic Search Ads Bulk file records.
  • The Java and Python SDKs are updated to support encoded redirection URI per the Github community pull request.

For information about the changes to the Bing Ads services included in this release, see the following sections.

New Reporting Columns for Low Quality Clicks

The LowQualityGeneralClicks and LowQualitySophisticatedClicks columns have been added to the AccountPerformanceReportColumn and CampaignPerformanceReportColumn value sets.

For information about the changes to the Bing Ads services included in this release, see the following sections.

Expanded Device Targeting

We are now giving you more control in setting bid adjustments by device, so you can more effectively manage your campaigns across each device type. Most significantly, you will be able to target tablets separately from PC with different bid adjustments. We are expanding the range to +900% for each device type – PC, Tablet, and Mobile, as well as adding the ability to completely opt out (set to -100%) from displaying ads on Tablet and Mobile.

Bulk API Version 10 for Expanded Device Targeting

You can use the Bid Adjustment field within the following Bulk record types to manage device targeting with the Bulk API.

Campaign Management API Version 10 for Expanded Device Targeting

You can use BidAdjustment element of the DeviceOSTargetBid object to manage device targeting with the Campaign Management API.

For information about the changes to the Bing Ads services included in this release, see the following sections.

Dynamic Search Ads

Dynamic Search Ads are coming to Bing Ads. You will be able to create a new type of campaign where the ad copy is automatically generated from the content on your website. A preview of the Campaign Management APIs are now available.

System_CAPS_ICON_note.jpg Note

Not everyone has this feature yet. If you don’t, don’t worry. It’s coming soon.

Before you can use dynamic search ads, you must upgrade to Final Urls. For more information, see URL Tracking with Upgraded URLs.

Campaign Management API Version 10 for Dynamic Search Ads

To get started with dynamic search ads, first you'll need to add a new Campaign with its type set to DynamicSearchAds. When you create the campaign, you'll need to include a DynamicSearchAdsSetting that specifies the target website domain and language. The new DynamicSearchAds value is added to the CampaignType value set.

Next, create a new AdGroup within the dynamic search ads campaign. You can add one or more Webpage criterion to each ad group that helps determine whether or not to serve dynamic search ads, by calling the AddAdGroupCriterions operation.

If you want to exclude certain portions of your website, you can add negative Webpage criterion at the campaign and/or ad group level using the respective AddCampaignCriterions and AddAdGroupCriterions service operations. The negative Webpage criterion at the campaign level applies to all ad groups within the campaign; however, if you define ad group level negative Webpage criterion, the campaign criterion is ignored for that ad group.

Whether the criterion is positive or negative, you can choose whether you want the criterion argument to match partial URLs, page content, page title, or categories that Bing thinks applies to your website. To discover the categories that you can use for Webpage criterion (positive or negative), use the GetDomainCategories operation with the Ad Insight service.

Finally you can add a DynamicSearchAd into the ad group. The ad title and display URL are generated automatically based on the website domain and language that you want to target.

Software Development Kit (SDK) Updates

The Bing Ads .NET, Java, and Python SDKs are updated with support for the following features.

  • Service proxies are added to the Campaign Management API for managing Dynamic Search Ads campaigns.

For information about the changes to the Bing Ads services included in this release, see the following sections.

New Reporting Columns for Shared Budgets

The BudgetAssociationStatus, BudgetName, and BudgetStatus columns have been added to the CampaignPerformanceReportColumn value set.

Ad Extension Scheduling

Ad extension scheduling is coming to Bing Ads. You will be able to set day and time ranges indicating when you want the ad extension to be shown with your ads. A preview of the Bulk and Campaign Management APIs are now available.

Bulk API Version 10 for Ad Extension Scheduling

The Ad Schedule, Start Date, End Date, and Use Searcher Time Zone columns are added to each of the Ad Extension Bulk record types.

Campaign Management API Version 10 for Ad Extension Scheduling

The Schedule and DayTime objects are added to the Campaign Management service for ad extension scheduling. The Scheduling element is added to the AdExtension base class and inherited by each of the following ad extensions.

The Scheduling element of the SiteLinksAdExtension is ignored, and you should use the Scheduling element of each nested SiteLink nested within the SiteLink.

Note: The Scheduling element is not returned with any ad extension by default. You must include Scheduling in the optional ReturnAdditionalFields flags when calling GetAdExtensionsAssociations and GetAdExtensionsByIds.

Software Development Kit (SDK) Updates

The Bing Ads .NET, Java, and Python SDKs are updated with support for the following features.

  • Service proxies are added to the Reporting APIs with additional columns for shared budgets.
  • Service proxies are added to the Campaign Management and Bulk APIs for managing ad extension scheduling. In addition to service proxy updates, support is added to the ad extension BulkEntity objects (e.g. BulkAppAdExtension) for reading and writing the Ad Schedule, Start Date, End Date, and Use Searcher Time Zone columns in each ad extension Bulk file record.
  • The BulkSitelink2AdExtension, BulkAdGroupSitelink2AdExtension, and BulkCampaignSitelink2AdExtension objects are added to the SDK for reading and writing the corresponding Sitelink2 Ad Extension, Ad Group Sitelink2 Ad Extension, and Campaign Sitelink2 Ad Extension Bulk file records.
  • The BulkBudget object is added to the SDK for reading and writing the corresponding Budget Bulk file record. Also the BulkCampaign object is updated with support for reading and writing the Budget Id column in the Campaign Bulk file record.

For information about the changes to the Bing Ads services included in this release, see the following sections.

Expanded Text Ads

The expanded text ad format works seamlessly on mobile, tablet and desktop devices so you can focus more on crafting your longer ad copy and optimizing your ad text to better engage your customers before they click your ad.

System_CAPS_ICON_note.jpg Note

Before you can use expanded text ads, you must upgrade to Final Urls. For more information, see URL Tracking with Upgraded URLs.

Bulk API Version 10 for Expanded Text Ads

The following Bulk record is added for managing expanded text ads.

You can download the new record using either the ExpandedTextAds or Ads BulkDownloadEntity values.

Campaign Management API Version 10 for Expanded Text Ads

The ExpandedTextAd object is derived from the Ad base class and can be managed with any of the existing ad operations e.g. AddAds, DeleteAds, and UpdateAds.

You can include ExpandedText as an AdType in the AdTypes request element of the following operations to retrieve expanded text ads.

Reporting API for Expanded Text Ads

New Reporting Columns and Filter are added for Expanded Text Ads.

Bulk Download for Individual Ad Types

The AppInstallAds, ExpandedTextAds, ProductAds, and TextAds values are added to the BulkDownloadEntity value set. You can download one or more types by specifying only the types you want, or you can continue to use the Ads value to return all current and future ad types.

Sitelink2 Migration Preview

System_CAPS_ICON_important.jpg Important

At the end of Q3 calendar year 2017, Bing Ads will upgrade all sitelinks ad extensions (contains multiple sitelinks per ad extension) to sitelink2 ad extensions (contains one sitelink per ad extension). You must be prepared for migration to sitelink2 ad extensions by September 30th. If you are interested in upgrading earlier, please reach out to your account manager or contact support. Please check back for more details at the Bing Ads API Blog.

The API interface for sitelink2 migration has been released as a preview. For more information about how to prepare for migration please see Upgrade from Multiple Sitelinks to One Sitelink Per Extension.

Bulk API Version 10 for Sitelink2 Migration Preview

You should use the GetAccountMigrationStatuses operation with the Campaign Management service to determine which sitelink data model is in effect for each account. For more information about how to prepare for migration and interpret the status results please see Upgrade from Multiple Sitelinks to One Sitelink Per Extension.

When using the Bulk service you must use the Sitelink2AdExtensions, AdGroupSitelink2AdExtensions, and CampaignSitelink2AdExtensions values of the BulkDownloadEntity value set to download the corresponding Sitelink2 Ad Extension, Ad Group Sitelink2 Ad Extension, and Campaign Sitelink2 Ad Extension records in a Bulk file.

Campaign Management API Version 10 for Sitelink2 Migration Preview

You should use the GetAccountMigrationStatuses operation to determine which sitelink data model is in effect for each account. For more information about how to prepare for migration and interpret the status results please see Upgrade from Multiple Sitelinks to One Sitelink Per Extension.

The SiteLinksAdExtension object is the previous data type with multiple sitelinks per extension that will be deprecated, and the Sitelink2AdExtension object is now added to represent one sitelink per ad extension.

To retrieve Sitelink2AdExtension objects you must use the Sitelink2AdExtension value of the AdExtensionsTypeFilter value set when calling the GetAdExtensionIdsByAccountId, GetAdExtensionsAssociations, and GetAdExtensionsByIds operations.

New Reporting Columns for Upgraded URLs

The TrackingTemplate and CustomParameters columns for upgraded URLs are added to the following reports.

Report RequestReport FilterReport Column
ProductPartitionPerformanceReportRequestProductPartitionPerformanceReportFilterProductPartitionPerformanceReportColumn
ProductPartitionUnitPerformanceReportRequestProductPartitionUnitPerformanceReportFilterProductPartitionUnitPerformanceReportColumn

Also the FinalURL, FinalMobileURL, FinalAppURL columns are added to the AdDynamicTextPerformanceReportColumn value set.

Universal Event Tracking

Before you can track conversions or target audiences using a remarketing list, you need to create a Universal Event Tracking (UET) tag in Bing Ads (web application or API) and then add the UET tag tracking code to every page of your website. For information about setting up UET tags using the Bing Ads web application, see How do I create a UET tag?.

Campaign Management API Version 10 for Universal Event Tracking

The following operations are added and reserved for future use.

After you retreive the tracking script from the add or get tag operation, the next step is to add the UET tag tracking code to your website. We recommend that you, or your website administrator, add it to your entire website in either the head or body sections. If your website has a master page, then that is the best place to add it because you add it once and it is included on all pages. For more information, see How do I add the UET tag to my website?

Conversion Goals

One of the biggest value propositions of UET is that it lets you install one tag on your website to track multiple types of conversions. Once the UET tag tracking code is added to your website, Bing Ads can log page visits and any custom events (such as downloading a white paper, subscribing to a newsletter etc).

However, not all actions are created equal. You probably have a subset of actions that you consider more important to a successful advertising campaigns. These may include making purchases, filling out a lead form or watching a video. This is where conversion goals can help. Conversion goals allow you to specify which actions (recorded by UET) to count as conversions. For more information about Conversion Goals, see What are conversion goals and goal types?.

Campaign Management API Version 10 for Conversion Goals

The following conversion goal data objects are added and are reserved for future use. The ConversionGoal is the base class from which all goals are derived.

The following operations are added for managing conversion goals and are reserved for future use.

Software Development Kit (SDK) Updates

The Bing Ads .NET, Java, and Python SDKs are updated with support for the following features.

  • Service proxies are added to the Campaign Management, Bulk, and Reporting APIs for managing expanded text ads. In addition to service proxy updates, the BulkExpandedTextAd object is added to the SDK for reading and writing the corresponding Expanded Text Ad Bulk file record.
  • Service proxies are added to the Bulk API for downloading individual ad types as an alternative to downloading all ad types.
  • Service proxies are added to the Campaign Management and Bulk APIs for managing one sitelink per ad extension.
  • Service proxies are added to the Reporting APIs with additional columns for aggregating data by final URLs.
  • Service proxies are added to the Campaign Management API for adding, getting, and updating universal event tracking tags. At this time the proxies are reserved for future use, and we plan to announce availability soon.
  • Service proxies are added to the Campaign Management API for adding, getting, and updating conversion goals. At this time the proxies are reserved for future use, and we plan to announce availability soon.
  • The BulkStructuredSnippetAdExtension, BulkAdGroupStructuredSnippetAdExtension, and BulkStructuredSnippetAdExtension objects are added to the SDK for reading and writing the corresponding Structured Snippet Ad Extension, Ad Group Structured Snippet Ad Extension, and Campaign Structured Snippet Ad Extension Bulk file records.
  • The BulkRemarketingList and BulkAdGroupRemarketingListAssociation objects are added to the SDK for reading and writing the corresponding Remarketing List and Ad Group Remarketing List Association Bulk file records.

Only for the Bing Ads .NET SDK and the Bing Ads Java SDK the DownloadHttpTimeout property is added to ReportingServiceManager, ReportingDownloadOperation, BulkServiceManager, and BulkOperation classes. Additionally the UploadHttpTimeout property is added to the BulkServiceManager class. The default timeout value for each is 100,000 milliseconds (100 seconds). You might want to change the timeout property to avoid HTTP timeout exceptions if you are downloading or uploading large files. **Note: ** The HTTP timeout differs from the existing CancellationToken which is used to limit the amount of time spent asynchronously polling for the server side process completion of an upload or download request.

For information about the changes to the Bing Ads services included in this release, see the following sections.

Sunset Version 9 Phase I

The Ad Intelligence, Bulk, Campaign Management, and Optimizer Version 9 services were sunset on June 30, 2016. For details on what has changed in version 10, see Migrating from Bing Ads API Version 9 to Version 10. If you have any questions, please feel free to contact support or post something in the Bing Ads API developer forum. Please note that the Customer Billing, Customer Management, and Reporting Version 9 services are still available. Later this summer we will announce details about the upgrade path for those services.

Remarketing Associations

Remarketing in Paid Search lets you improve your return on investment by optimizing your campaigns for specific audiences, which are the people who have visited your website before. Support is added to the Campaign Management and Bulk APIs for associating remarketing lists with ad groups in your search advertising campaigns. For more information about Remarketing APIs, see the UET and Remarketing Guide..

System_CAPS_ICON_note.jpg Note

The Reporting API already lets you get remarketing data with the AudiencePerformanceReportRequest.

Bulk API Version 10 for Remarketing Associations

The following Bulk records are added for retrieving remarketing lists and managing remarketing list associations.

The new Remarketing Targeting Setting field is also added to the existing Ad Group record.

You can download these records using the respective RemarketingLists, AdGroupRemarketingListAssociations, and AdGroups BulkDownloadEntity values.

Campaign Management API Version 10 for Remarketing Associations

The following operations are added for retrieving remarketing lists (RemarketingList) and managing remarketing list associations (AdGroupRemarketingListAssociation).

Bid Strategy Type

Support is added to the Campaign Management and Bulk APIs for setting up the bid strategy type for how you want to manage your bids.

System_CAPS_ICON_note.jpg Note

This feature is not supported for campaigns of type Shopping.

System_CAPS_ICON_tip.jpg Tip

You can set your campaign’s bid strategy to Enhanced CPC and then, at any time, set an individual ad group’s or keyword’s bid strategy to Manual CPC.

Bulk API Version 10 for Bid Strategy Type

The new Bid Strategy Type field is added to these existing Bulk records.

You can download these records using the respective AdGroups, Campaigns, and Keywords BulkDownloadEntity values.

Campaign Management API Version 10 for Bid Strategy Type

The BiddingScheme object is added and defines the base object of a bidding scheme for how you want to manage your bids. A bidding scheme is known as a bid strategy type in the Bing Ads web application.

Do not try to instantiate a BiddingScheme. You can create one or more following objects that derive from it.

The following objects derived from BiddingScheme are reserved for future use.

Reporting API Version 9 for Bid Strategy Type

The new BidStrategyType column and BidStrategyTypeReportFilter are added to the following reports.

Report RequestReport FilterReport Column
KeywordPerformanceReportRequestKeywordPerformanceReportFilterKeywordPerformanceReportColumn
ShareOfVoiceReportRequestShareOfVoiceReportFilterShareOfVoiceReportColumn
SitePerformanceReportRequestSitePerformanceReportFilterSitePerformanceReportColumn

Structured Snippets

Support is added to the Campaign Management and Bulk APIs for managing structured snippet ad extensions. A structured snippet ad extension pairs one header with between 3 and 10 snippet values that tell customers more about your business.

In the following example, Courses is the header, and .NET, Java, Python, and PHP are examples of individual values.

Courses: .NET, Java, Python, PHP

You can associate a structured snippet ad extension with one or more campaigns and ad groups. Each campaign or ad group can be associated with between 1 and 20 structured snippet ad extensions. A text ad will only include one structured snippet (one headline with 3 - 10 values) per impression.

System_CAPS_ICON_note.jpg Note

The Reporting API already lets you get ad extensions data, for example with the AdExtensionByAdReportRequest.

Bulk API Version 10 for Structured Snippets

The following Bulk records are added for managing structured snippets.

You can download these records using the respective StructuredSnippets, AdGroupStructuredSnippets, and CampaignStructuredSnippets BulkDownloadEntity values.

Campaign Management API Version 10 for Structured Snippets

You can use the existing Campaign Management operations such as AddAdExtensions and SetAdExtensionsAssociations for managing structured snippets (StructuredSnippetAdExtension).

Shared Budget

Shared budgets are coming to Bing Ads in the third quarter of calendar year 2016. With shared budgets you will be able to set a single daily budget that can be used by any campaign within the same account. This will enable you to efficiently distribute a single daily budget across all campaigns or across a defined group of campaigns within your Bing Ads account.

System_CAPS_ICON_note.jpg Note

Although support for shared budgets is not yet available, a preview of the service contract is added to the Campaign Management and Bulk APIs.

System_CAPS_ICON_important.jpg Important

To avoid a breaking change when updating campaigns, you might need to prepare for the introduction of shared budgets in the Bing Ads platform, even if you do not plan to use shared budgets right away.

In the context of shared budgets, the budget amount is a read-only property that is always returned regardless of whether or not the campaign uses a shared budget. When a campaign is associated to a shared budget the amount returned is that of the shared budget. If you try to update the budget amount of a campaign that has a shared budget, the service will return the CampaignServiceCannotUpdateSharedBudget error code. You can continue to update the budget amount for unshared budgets, and you can make other updates to the campaign regardless of whether the budget is shared. To determine whether the campaign uses a shared budget, check the value of the BudgetId element (Campaign object) or Budget Id field (Bulk (Campaign object) record).

Bulk API Version 10 for Shared Budget

The Budget Bulk record is added for managing shared budgets.

The new Budget Id and Budget Name fields are also added to the existing Campaign record.

You can download these records using the respective Budgets and Campaigns BulkDownloadEntity values.

Campaign Management API Version 10 for Shared Budget

The following operations are added for managing shared budgets (Budget).

Bing Shopping Campaign Countries

The GetBSCCountries operation is added, and returns the list of supported sales country codes for Bing Shopping campaigns.

Software Development Kit (SDK) Updates

The Bing Ads .NET, Java, and Python SDKs are updated with support for the following features.

  • The Ad Intelligence, Bulk, Campaign Management, and Optimizer Version 9 service proxies have been removed from the SDKs, because each service sunsets on June 30, 2016. Important: The default version for the ServiceClient in the Python SDK has been updated from v9 to v10.
  • Service proxies are added to the Campaign Management and Bulk APIs for associating remarketing lists with ad groups in your search advertising campaigns.
  • Service proxies are added to the Campaign Management, Bulk, and Reporting APIs for managing bid strategy types. In addition to service proxy updates, support for the new Bid Strategy Type field is added to each of the BulkCampaign, BulkAdGroup, and BulkKeyword SDK objects.
  • Support for the Ad Format Preference field is added to the BulkTextAd SDK object. For more information about managing the ad format preference in bulk, see the Text Ad record.
  • Service proxies are added to the Campaign Management and Bulk APIs for managing structured snippet ad extensions.
  • Service proxies are added to the Campaign Management and Bulk APIs for managing shared budgets.
  • Service proxies are added to the Campaign Management API for getting the list of supported sales country codes for Bing Shopping campaigns.

For information about the changes to the Bing Ads services included in this release, see the following sections.

Reporting Version 9

Reporting Status Filters

You can filter the negative keyword conflict report by the status of your account, campaign, ad group, or keyword. The NegativeKeywordConflictReportFilter is added to the NegativeKeywordConflictReportRequest data object.

Software Development Kit (SDK) Updates

The Bing Ads .NET, Java, and Python SDKs are updated with support for the following features.

  • Reporting API interface updates for the month of May.
  • Added support to download and upload the Bulk record type App Install Ad by reading and writing the new BulkAppInstallAd SDK object.
  • Added support for setting the 'state' parameter in OAuthAuthorization subclasses to help prevent cross site request forgery (CSRF).
  • Added support for constructing OAuthAuthorization subclasses using an existing access token.

Additionally the Java SDK added Bulk format version verification. The BulkFileReader will now return UnsupportedOperationException if the Bulk format version in the given CSV file is not supported by the corresponding version of Bulk API. For example, Bulk API V10 only supports Bulk format version 4.0.

Show: