Release Notes

 

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

For information about this month's changes to Bing Ads services, see the following sections.

Bing Ads Software Development Kit (SDK) Updates

The Bing Ads .NET, Java, PHP, and Python SDKs are updated with support for the following features. Unless otherwise noted the changes only apply to Bing Ads API version 11. Some objects are reserved for future use, so please refer to the service reference documentation for availability details.

  • The Reporting service proxies are updated to support new columns for location targeting.
  • For the Bing Ads .NET SDK - Fixed the Bulk download DateTime parser for compatibility with localized time zone settings.
  • For the Bing Ads Java SDK - Added an option to automatically delete the temporary bulk file used by BulkServiceManager for upload and download per the Github community pull request.
  • For the Bing Ads Java SDK - Implemented internal retry logic for creating a new service with the wsdl.

For information about this month's changes to Bing Ads services, see the following sections.

Bing Ads Software Development Kit (SDK) Updates

The Bing Ads .NET, Java, and Python SDKs are updated with support for the following features. Unless otherwise noted the changes only apply to Bing Ads API version 11. Some objects are reserved for future use, so please refer to the service reference documentation for availability details.

  • The Campaign Management service proxies are updated to support inherited bid strategy type.
  • The Reporting service proxies are updated to support new columns for Bing Shopping campaigns.
  • New version 11 bulk labels objects are added i.e., BulkLabel, BulkCampaignLabel, BulkAdGroupLabel, BulkKeywordLabel, BulkAppInstallAdLabel, BulkDynamicSearchAdLabel, BulkExpandedTextAdLabel, BulkProductAdLabel, and BulkTextAdLabel objects are added to the SDK for reading and writing the corresponding Bulk file records.
  • A new version 11 bulk offline conversion object is added i.e., the BulkOfflineConversion object is added to the SDK for writing and uploading the corresponding Bulk file record.
  • For the Bing Ads .NET SDK - Fixed the mapping for expired ad groups in the BulkAdGroup object. Previously if the ad group status in the bulk file was Expired, the SDK mapped and returned the value as Deleted. Prior to Bing Ads API version 10, expired ad groups were returned with a deleted status by design for backwards compatibility.

Increase in subdomain limit for website exclusions

The limit of subdomains allowed in a website exclusion increased from two to three, based on customer requests. This will enable you to exclude URLs based on two-part top-level domains (TLDs) such as .co.uk. The number of allowed subdirectories remains unchanged at two.

For example, the following are valid URLs,

  • one.two.three.contoso.com/1/2
  • www.two.three.contoso.com/1/2
  • one.two.contoso.co.uk/1/2

The following are invalid URLs:

  • one.two.three.contoso.co.uk/1/2 (too many subdomains)
  • one.two.three.contoso.com/1/2/3 (too many subdirectories)

For reference documentation, please see CampaignNegativeSites and AdGroupNegativeSites.

Geographical Locations File Version 2.0

The GetGeoLocationsFileUrl operation now supports version 2.0. County location IDs are only available in version 2.0.

For more details about the contents of each file version, see Geographical Location Codes.

System_CAPS_ICON_important.jpg Important

The locations file Version 1.0 is deprecated in favor of version 2.0. After October 31, 2017 version 1.0 will be sunset and only 2.0 will be supported.

New Reporting Columns for Location Targeting

The County, LocationId, and PostalCode columns have been added to the GeographicPerformanceReportColumn value set.

The County, LocationId, PostalCode, QueryIntentCounty, QueryIntentPostalCode, and QueryIntentLocationId columns have been added to the UserLocationPerformanceReportColumn value set.

For information about this month's changes to Bing Ads services, see the following sections.

Keyword Planner

Support for keyword planner operations is added. The Keyword Planner was already available in the Bing Ads web application, and now support is added for Bing Ads API version 11.

System_CAPS_ICON_note.jpg Note

Keyword Planner features are currently available to customers in the United States, United Kingdom, Canada, Australia, France, and Germany.

Given a list of existing keywords, the GetKeywordIdeas operation suggests new ad groups and keywords based on your existing keywords, website, and product category. You can also request historical statistics for keywords e.g., monthly searches, competition, average CPC, and ad impression share. You can use the returned suggested keyword bids as input to the GetKeywordTrafficEstimates operation.

The result is a KeywordIdea list. Each keyword idea includes historical statistics for keywords e.g., monthly searches, competition, average CPC, and ad impression share. Whereas the Bing Ads web application returns a 12 month average of the historical monthly search counts, each KeywordIdea includes a list of monthly search counts. You can use each count individually or average them for parity with the Bing Ads web application's calculation.

Once you have already settled on an initial set of keywords, the GetKeywordTrafficEstimates operation provides traffic estimates for keywords e.g., average CPC, average position, clicks, CTR, impressions, and total cost. As input you provide the keyword, bid, language, location, and network, with optional campaign budget and negative keyword filters.

The result is a KeywordEstimate list for each AdGroupEstimate, which are all nested within one CampaignEstimate. Each keyword estimate includes a minimum and maximum TrafficEstimate. As previously mentioned, the traffic estimates for keywords include average CPC, average position, clicks, CTR, impressions, and total cost.

For more details see the Keyword Ideas and Traffic Estimates technical guide.

Labels

Support for labels is added. Labels let you organize campaigns, ad groups, ads, and keywords into groups based on whatever is important to you. You can then filter and run reports on your labels to get the data that is most meaningful to you.

System_CAPS_ICON_note.jpg Note

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

Bulk API Version 11 for Labels

You can use the following Bulk record types to manage labels with the Bulk API.

Campaign Management API Version 11 for Labels

You can add, delete, get, and update labels (Label objects) with the corresponding operations.

You can set, get, and delete label associations (LabelAssociation objects) with the corresponding operations.

Offline Conversion Import

Support for Offline Conversion Import is added. Use offline conversions to track the full impact and benefit of your search ads. It allows you to import offline conversions derived from a search click back into Bing Ads.

System_CAPS_ICON_note.jpg Note

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

To set up offine conversion tracking, create an offline conversion goal with the Campaign Management service or via the Bing Ads web application, wait two hours, and then send Bing Ads the offline conversion data with either the Campaign Management service or Bulk service.

You must also enable MSCLKID Auto Tagging. Every time you create a new OfflineConversionGoal via either the Bing Ads web application or Campaign Management API, the MSCLKID Auto Tagging is enabled automatically. You can enable or disable auto tagging using either the Campaign Management service or Bulk service.

For more information, see Tracking offline conversions.

Bulk API Version 11 for Offline Conversions

You can send Bing Ads the offline conversion data by uploading one or more Offline Conversion Bulk records.

To manage the MSCLKID Auto Tagging, use the MSCLKID Auto Tagging Enabled field of the Account Bulk record.

Campaign Management API Version 11 for Offline Conversions

You can manage OfflineConversionGoal objects with the previously shipped conversion goal service operations e.g. AddConversionGoals.

You can send Bing Ads the offline conversion data by submitting OfflineConversion data via the ApplyOfflineConversions operation.

To manage the MSCLKID Auto Tagging, use the corresponding AccountProperty (MSCLKIDAutoTaggingEnabled) via the GetAccountProperties and SetAccountProperties operations.

New Reporting Columns for Bing Shopping Campaigns

The ReturnOnAdSpend, BidStrategyType, LocalStoreCode, and StoreId columns have been added to the ProductDimensionPerformanceReportColumn value set.

The ReturnOnAdSpend, BidStrategyType, and LocalStoreCode columns have been added to the ProductPartitionPerformanceReportColumn value set.

The ReturnOnAdSpend, BidStrategyType, and LocalStoreCode columns have been added to the ProductPartitionUnitPerformanceReportColumn value set.

Inherited Bid Strategy Type

You can get the bid strategy type that is inherited from each ad group or keyword's parent campaign or ad group. This value is equal to the parent campaign or ad group's Bid Strategy Type field. Possible values are EnhancedCpc, ManualCpc, MaxClicks, MaxConversions, and TargetCpa.

Bulk API Version 11 for Inherited Bid Strategy Type

The Inherited Bid Strategy Type field is added to the Ad Group and Keyword records.

Campaign Management API Version 11 for Inherited Bid Strategy Type

The InheritedBidStrategyType element is added to the InheritFromParentBiddingScheme object. This element is not returned by default. You must include InheritedBidStrategyType in the ReturnAdditionalFields optional request element when calling GetAdGroupsByCampaignId, GetAdGroupsByIds, GetKeywordsByAdGroupId, GetKeywordsByEditorialStatus, and GetKeywordsByIds.

Bing Ads Software Development Kit (SDK) Updates

The Bing Ads .NET, Java, and Python SDKs are updated with support for the following features. Unless otherwise noted the changes only apply to Bing Ads API version 11. Some objects are reserved for future use, so please refer to the service reference documentation for availability details.

Breaking Changes

System_CAPS_ICON_important.jpg Important

Before you upgrade to the latest SDK please note the following breaking changes.

  • The Status property of the BulkCampaignProductScope object is removed. The Bulk file Status field is now mapped to the Status element of the BiddableCampaignCriterion of the BulkCampaignProductScope.
  • All BulkEntity derived SDK objects (except BulkAdGroupProductPartition) which previously contained the AdGroupCriterion or CampaignCriterion property are updated as either Biddable or Negative. Both the type and the name are updated e.g. BulkAdGroupAgeCriterion has property name BiddableAdGroupCriterion and data type BiddableAdGroupCriterion. The purpose is to be clear about the supported data type per bulk entity up front, rather than causing friction later i.e., runtime errors due to mismatch of BulkEntity to concrete criterion type. Several bulk entities were updated during the May 2017 release; and the remaining mappings are fixed with this release.

Non Breaking Changes

  • The Ad Insight service proxies are updated to support the keyword planner.
  • The Bulk service proxies are updated to support labels.
  • The Campaign Management service proxies are updated to support labels.
  • The Bulk service proxies are updated to support offline conversions.
  • The Campaign Management service proxies are updated to support offline conversions.
  • Support is added for Bulk entity mapping of multiple campaign languages i.e., updated mapping of the Language field in the Bulk file to the BulkCampaign and BulkAdGroup. Note: Support is added for Bing Ads API version 10 and 11.
  • Support is added for Bulk entity mapping of MaxConversions, MaxCpc, and TargetCpa bid strategy types i.e., mapping of the Bid Strategy Type, Bid Strategy MaxCpc, and Bid Strategy TargetCpa fields in the Bulk file to the BulkCampaign. Note: Support is added for Bing Ads API version 10 and 11.
  • Support is added for Bulk entity mapping of LocalInventoryAdsEnabled for Bing Shopping campaigns i.e., mapping of the LocalInventoryAdsEnabled field in the Bulk file to the BulkCampaign.
  • Performance data mapping is added to the BulkAdGroupRemarketingListAssociation object.
  • New version 11 bulk audience objects are added i.e., BulkAdGroupNegativeRemarketingListAssociation, BulkCustomAudience, BulkAdGroupCustomAudience, BulkAdGroupNegativeCustomAudience, BulkInMarketAudience, BulkAdGroupInMarketAudience, and BulkAdGroupNegativeInMarketAudience objects are added to the SDK for reading and writing the corresponding Bulk file records.
  • New version 11 bulk price ad extension objects are added i.e., BulkPriceAdExtension, BulkCampaignPriceAdExtension, and BulkAdGroupPriceAdExtension objects are added to the SDK for reading and writing the corresponding Bulk file records.
  • New version 11 bulk account level ad extension objects are added i.e., BulkAccountAppAdExtension, BulkAccountCalloutAdExtension, BulkAccountImageAdExtension, BulkAccountLocationAdExtension, BulkAccountPriceAdExtension, BulkAccountReviewAdExtension, and BulkAccountSitelink2AdExtension objects are added to the SDK for reading and writing the corresponding Bulk file records.

For information about this month's changes to Bing Ads services, see the following sections.

Bing Ads API Version 11 General Availability

Bing Ads API Version 11 is released to production. For more details, see Migrating to Bing Ads API Version 11 and Version 11 API Reference.

System_CAPS_ICON_important.jpg Important

With the availability of Bing Ads API version 11, the previous versions of the API (v10 for Ad Insight, Bulk, and Campaign Management services and v9 for Customer Billing, Customer Management, and Reporting services) are now deprecated. We will sunset (i.e., shut down these services) on October 31st. To avoid any disruption to your tools after the older services sunset, migrate to the v11 services as soon as possible. For more information, see Migrating to Bing Ads API Version 11.

Bing Ads PHP Software Development Kit (SDK)

The Bing Ads .NET, Java, and PHP SDKs are updated with support for Bing Ads API Version 11 web service addresses. This release enables you to upgrade existing features from version 9 and 10 to version 11.

Bulk entity support for new version 11 features e.g. BulkPriceAdExtension will be added to the .NET, Java, and Python SDKs in a future release.

Dynamic Search Ads Reports

The the following reports are added for Dynamic Search Ads.

Report RequestReport FilterReport Column
DSAAutoTargetPerformanceReportRequestDSAAutoTargetPerformanceReportFilterDSAAutoTargetPerformanceReportColumn
DSACategoryPerformanceReportRequestDSACategoryPerformanceReportFilterDSACategoryPerformanceReportColumn
DSASearchQueryPerformanceReportRequestDSASearchQueryPerformanceReportFilterDSASearchQueryPerformanceReportColumn

For information about this month's changes to Bing Ads services, see the following sections.

Bing Ads API Version 11 Preview

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.

Bing Shopping Product Search Query Performance Report

The Product Search Query performance report is now available for Bing Shopping Campaigns. Submit the ProductPartitionPerformanceReportRequest to see what your audience is searching for when your product ads are shown.

For information about this month's changes to Bing Ads services, 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 this month's changes to Bing Ads services, 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

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

Campaign Management API 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 this month's changes to Bing Ads services, 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 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 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

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

Bulk API 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.
  • 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 this month's changes to Bing Ads services, 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 this month's changes to Bing Ads services, 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 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 for Expanded Device Targeting

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

Show: