2 out of 4 rated this helpful - Rate this topic

Release Notes

Version 8 R5 (April 2013)

Campaign Management

Product Ads

The Product Ads feature lets you create ad campaigns that advertise the products found in a customer’s Bing Merchant Center store. A product ad is similar to a text ad except that the delivery engine generates the ad’s contents based on the product details that it finds in the Bing Merchant Center store. A product ad includes details about the product, an image, and optional promotional text.

System_CLiX_note Note

To add or get product ad extensions, the customer must be a member of the Product Ad pilot program. For more information, see Managing Product Ads.

Product ads programming elements include the following campaign management service operations.

Product ads programming elements include the following campaign management data objects.

Product ads programming elements include the following campaign management value sets.

System_CLiX_note Note

To use the product ads feature you may also use existing campaign management programming elements, for example AddAds and AdAddExtensions.

Ad Extensions

Added the UpdateAdExtensions operation.

Call Tracking

Added IsCallTrackingEnabled and RequireTollFreeTrackingNumber elements to the CallAdExtension object.

Media

Added the following service operations to add and retrieve up to 10 media objects per call.

Deprecated the following image service operations.

Customer Management

Account Number

The Number element of the Account object now has the form xxxxxxxx, where xxxxxxxx is a series of any eight alphanumeric characters.

System_CLiX_note Note

Prior to this release the account number was restricted to the form Xnnnnnnn, where nnnnnnn is a series of digits.

Optimizer

Keyword Competition

The Competition element of the KeywordOpportunity object is returning data. Prior to this release it was designated for future use. You can get this data by calling the GetKeywordOpportunities operation.

Keyword competition is an indicator of how many advertisers are bidding on a particular keyword. Highly competitive keywords are more popular among advertisers and, therefore, tend to require larger bids to get the better ad positions. Keywords with medium or low competition might offer advertisers a better return on investment (ROI).

Reporting

Product Ads

Added the ProductTargetPerformanceReportRequest object, ProductTargetPerformanceReportFilter object, and ProductTargetPerformanceReportColumn value set. The product target report can be used to get performance metrics about your product ads campaigns. For more information, see . Managing Product Ads.

Version 8 R4.8 (March 2013)

Ad Intelligence

Ad Group Level Bid Estimates

For GetEstimatedBidByKeywords, you can now request estimates for keyword level bids, ad group level bids, or both. By default the service will continue to return an array of KeywordEstimatedBid, and you can override the default to get AdGroupEstimatedBid via the GetBidsAtLevel element of GetEstimatedBidByKeywords.

System_CLiX_important Important

The introduction of AdGroupEstimatedBid in the GetEstimatedBidByKeywordsResponse may break some clients. Please ensure that your application is ready to handle the new response element.

Increased Bid Coverage

For GetEstimatedBidByKeywordIds and GetEstimatedBidByKeywords, you can request high bid coverage in which case an estimated minimum bid will be returned for all requested keywords, or stay with the default bid coverage where estimates may not be returned for all requested keywords. For increased bid coverage, set the GetIncreasedBidCoverage element of GetEstimatedBidByKeywordIds or GetEstimatedBidByKeywords to true and handle possible NULL values returned.

For more information, see Get Increased Bid Coverage.

Campaign Management

Location Ad Extension Coordinates No Longer Read-only

Previously, the service determined the business’ coordinates from the specified address. Now, you have the option to specify the coordinates if known. Specifying the coordinates can save time because you do not have to confirm whether the service successfully determined the coordinates (the extension is not used until the coordinates are determined). This change affects the following data objects.

Reporting

Added Columns for Keyword Performance Report

Added AccountStatus, CampaignStatus, AdGroupStatus, and KeywordStatus to the KeywordPerformanceReportColumn Value Set.

Added Network to the KeywordPerformanceReportColumn Value Set. If you include the Network column, the report will include a column that contains the network of the ad group that owns the ad.

Added TopVsOther to the KeywordPerformanceReportColumn Value Set. If you include the TopVsOther column, the report will include a column that indicates whether the ad impression appeared in a top position or elsewhere.

Added the Call Detail Report

The call detail report is provided for advertisers in the ClickToCallOnly pilot. There is one row or record in the report for each call made to the tracked number. You can include details in the report such as call duration and phone spend. For more information, see the CallDetailReportRequest request. For a list of entities and elements that the report can include, see the Remarks section in CallDetailReportColumn.

Added Optional Columns for Call Tracking

Added AverageCpp, ClickCalls, ManualCalls, PhoneCalls, PhoneImpressions, PhoneSpend, Ptr and TotalCostPhoneAndClicks to the AccountPerformanceReportColumn, AdGroupPerformanceReportColumn, and CampaignPerformanceReportColumn value sets.

Version 8 R4.7 (February 2013)

Bulk

Updated the schema to support location and call ad extensions. The download will include only location and call ad extensions that are associated with a campaign.

Campaign Management

Changes to Ad Extensions

Removed the Location Ad Extensions Limit on Add

The AddAdExtensions operation no longer restricts the number of location ad extensions that you can add per call to 10. Previously, you could add 100 ad extensions, but only 10 of them could be location ad extensions. You can still add only 100 ad extensions, but there is now no restriction to the number of them that can be location ad extensions.

In addition, the service used to determine the location’s geographical coordinates when you called AddAdExtensions. If the service could not determine the coordinates, AddAdExtensions would fail. Now, the service determines the coordinates after the extensions are added. To check whether the service successfully determined the coordinates, call the GetAdExtensionsByIds or GetAdExtensionsByCampaignIds operation to get the LocationAdExtension object. The service successfully determined the coordinates if the GeoCodeStatus element is set to Complete. It can take from seconds to minutes for the service to determine the coordinates.

New operation to get an account’s extensions

Added the GetAdExtensionIdsByAccountId operation, which returns an account’s ad extensions. You can request all of the account’s ad extensions or only those that are associated with a campaign. Previously, you had to maintain your own list of ad extension IDs.

Reporting

Updated Ad Extension Report Columns

The ad extension reports now support the ClickType column. The ClickType column identifies the item within the ad extension that the user clicked. For example, the column will contain Click to Direction if the user clicked a location ad extension’s address. The following value sets include the ClickType column.

Added the list of location and call ad extension property IDs to the AdExtensionPropertyId column description (see AdExtensionDimensionReportColumn).

Version 8 R4.6 (January 2013)

Added support for the following markets.

  • Indonesia

  • Malaysia

  • Philippines

  • Taiwan

  • Thailand

  • Vietnam

The following topics were updated with information to support these new markets.

  • Match Type and Bid Values – Added bid values for each country’s currency, except for the Vietnam Dong, which is not supported.

  • Language Values – Added TraditionalChinese for Taiwan. The other countries use English.

  • Publisher Country Values – Added the country and its country code and support language.

  • TextAd – Added maximum string lengths for the Text and Title fields to support Traditional Chinese.

  • CurrencyType Value Set – Marked each country’s currency as supported, except for the Vietnam Dong, which is not supported.

  • State/Province Codes – Added state codes for each country. The codes are used to specify customer and user addresses.

In addition, the Country Codes file that contains the location targeting codes was updated to reflect these new distribution channels. For information about downloading the Country Codes file, see Country Codes.

Version 8 R4.5 (November 2012)

Ad Intelligence

Increased the Number of Keywords that SuggestKeywordsFromExistingKeywords Returns

Increased the number of keywords that the SuggestKeywordsFromExistingKeywords operation can return from 100 to 200. If SuggestionType is set to 4, you can request a maximum of 200 suggestions per keyword. If the suggestion type is set to 1, 2, or 3, the maximum number of keyword suggestions that you can request remains 100.

Added a Brand Filter to SuggestKeywordsFromExistingKeywords and SuggestKeywordsForUrl

Added the ExcludeBrand element to the SuggestKeywordsForUrlRequest message and SuggestKeywordsFromExistingKeywordsRequest message. The element determines whether to include brand keywords in the list of suggested keywords.

Added Optional Elements to GetEstimatedBidByKeywords and GetEstimatedPositionByKeywords

Added the AdGroupId and CampaignId elements to the GetEstimatedBidByKeywordsRequest and GetEstimatedPositionByKeywordsRequest messages. Setting these optional elements can improve the accuracy of the suggested bid and position by factoring in the ad group’s performance data over the last seven days to determine how well the keyword might have performed in the ad group. Providing the context of the ad group where you might use the keyword provides better accuracy than factoring in how well the keyword performed among all advertisers.

Campaign Management

Business Targeting Being Removed

Business location targeting will no longer be supported beginning April 2013. Any existing business targets will automatically be converted to radius targets (in the same target object). Please update your application accordingly. For more information, see Business Targeting.

Added New Ad Extension Types

You can include the following new extensions in a text ad.

  • CallAdExtension – Text ads will include a phone number. The phone number is clickable on hi-fi mobile devices.

  • LocationAdExtension – Text ads will include the business’ address and a phone number. The phone number is clickable on hi-fi mobile devices.

For more information about these new extensions, see Ad Extensions.

System_CLiX_note Note

To use these extensions, you must be a member of the location ad extension v2 and call ad extension v2 pilot programs.

System_CLiX_note Note

If you call the SetCampaignAdExtensions and GetCampaignAdExtensions operations to set and get location and call ad extensions, you must migrate your application from using the old version of AdExtension to using version 2 of the location and call ad extensions by April 2013. For more information, see Ad_Extensions_V1.

Transitioning from Metro Codes to DMA® Codes

Bing Ads is transitioning from metro codes to DMA® codes for the United States. You must update your application to use the new DMA® codes by April 2013. All campaigns that reference metro codes will be automatically migrated to the new DMA® codes by April 2013. If you use the old codes after the migration, your application will stop working.

For details about the migration, see the Coming Soon: Bing Ads API is Migrating from Metro to DMA® Targeting blog post.

For links to the new country codes file that contains the DMA codes, and to a Microsoft Excel spreadsheet that maps the old metro and city codes to the new DMA and city codes, see Country Codes.

If you haven’t already read the Added Location Version to Get Target Requests release notes included in the Version 8 R4.3 notes, please do so. It contains possible breaking changes related to the transition to DMA codes.

Reporting

Added QualityImpact to the Keyword Performance Report

Added the QualityImpact column to the keyword performance report. The QualityImpact column indicates the possible increase in the number of impressions that the keyword could receive if its quality score improved above a 5 (underperforming). For more information, see KeywordPerformanceReportColumn.

Added ClickSharePercent to the Share of Voice Report

Added the ClickSharePercent column to the share of voice report. The ClickSharePercent column contains the percentage of clicks that the advertiser gets compared to the percentage of clicks that other advertisers get for the same keyword. For more information, see ShareOfVoiceReportColumn.

Version 8 R4.4 (October 2012)

Campaign Management

Include Site Links in Your Ads

You can now include site links in your ads. By including deep links into your website, you can direct customers to relevant promotional or technical information that may help increase conversions. For details about how to add site links to ads, see Ad Extensions.

Reporting

Added Ad Extension Reports

Ad extensions let you decorate text ads with additional information that helps customers find relevant information about your products and services. For example, you can include deep links into your website to quickly direct your customers to relevant promotional or technical information that may help increase conversions.

You can use the following new reports to get statistics about the effectiveness of the ad extensions you've included in your ads.

  • AdExtensionByAdsReportRequest – Aggregates performance data by ad for a specified time period. By including performance details, such as clicks, conversion, and spend, you can identify ad extensions that are performing well, and those that may need to be adjusted to optimize the monthly budget.

  • AdExtensionByKeywordReportRequest – Aggregates performance data by keyword for a specified time period. By including performance details, such as clicks, conversion, and spend, you can identify ad extensions that are performing well, and those that may need to be adjusted to optimize the monthly budget.

  • AdExtensionDimensionReportRequest – Lists all versions of an ad extension by account. You can use this information along with the performance data from the other two reports to determine which version performed better.

Version 8 R4.3 (September 2012)

Ad Intelligence

Added Support for Germany, Austria, and Switzerland

Added support for Germany, Austria, and Switzerland. For new language and country values, see the following value sets.

Added New Field to SuggestKeywordsFromExistingKeywords

Added the RemoveDuplicates field to the SuggestKeywordsFromExistingKeywordsRequest message. To have the SuggestKeywordsFromExistingKeywords operation return a unique list of keywords, set RemoveDuplicates to true. The default is false.

Redefined the Last30Days Time Interval

Previously, the Last30Days time interval (see TimeInterval) was defined as the previous 30 days (excluding today’s data). Now, it is defined as the previous calendar month. Note that it can take up to 72 hours for the previous calendar month’s data to be available.

You can specify the time interval in the following operations.

Campaign Management

Specify a Destination URL at the Keyword Level

Previously, to specify a destination URL for a keyword, you set the Param1 element of the Keyword object to the destination URL. To use the destination URL in an ad, you would set the DestinationUrl element of the TextAd object to {Param1}. When the ad was displayed, the destination URL would be pulled from the Param1 element of the keyword.

Now, you can explicitly specify the destination URL to use in the ad when the user’s search query matches the keyword. To specify the destination URL of a keyword, you call the SetDestinationUrlToKeywords operation.

The keyword’s destination URL is used if specified; otherwise, the ad’s URL is used.

Note that you can continue to use the Param1 element of the keyword to specify the destination URL of a keyword; however, you are encouraged to begin using the SetDestinationUrlToKeywords operation instead.

You use the following operations to get and set the destination URL of a keyword.

Appeal Editorial Rejections

If an ad or keyword fails editorial review, and the failure is appealable, you can call the AppealEditorialRejections operation to appeal the rejection.

To find ads or keywords that failed the editorial review process, call the GetAdsByEditorialStatus or GetKeywordsByEditorialStatus operation, respectively.

To determine the reason for the failure and whether it’s appealable, call the GetEditorialReasonsByIds operation. The operation returns an EditorialReasonCollection object which includes an AppealStatus element. The rejection is appealable if the status is set to Appealable. For possible status values, see AppealStatus.

Exclude Locations from Location Targets

You can now exclude locations from a location target. For example, if you target the U.S., you can exclude one or more states from being targeted. To exclude a location from a target location, call the SetExclusionsToAssociatedEntities operation. For details, see Exclude Locations from a Location Target.

To get a list of locations that have been excluded from a location target, call the GetExclusionsByAssociatedEntityIds operation.

Added Location Version to Get Target Requests

Added the LocationTargetVersion element to the following request messages. You can use the new element to specify the version of the location codes to return if the target contains location targets. For example, you can request that the operations return metro codes or Nielsen DMA® codes. By default, the operations will return the oldest supported version. Currently, the oldest supported version is metro codes.

Because older versions may not be supported in the future, you should update your application to set this element to Latest to avoid breaking changes.

Optimizer

Added Keyword Opportunities for Ad Groups

Added the GetKeywordOpportunities operation that you can call to identify keywords that are relevant to an ad group. The operation returns KeywordOpportunity objects that contain the suggested keyword, bid value and the estimated monthly volume of user search queries that matches the keyword. Applying the opportunity adds the keyword to the ad group.

Currently, the operation returns only exact-match bid opportunities for the suggested keywords.

Reporting

Added Share of Voice Report

Added the share of voice (SOV) report that aggregates SOV data by keyword and match type for the specified time period. You can use the report’s data to focus on keywords with low impression share. After eliminating share lost to budget, you can use SOV to identify keywords with high impression share lost to rank, bid, keyword relevance, and landing page relevance. You can then adjust your bids and improve your ad copy in order to improve keyword impression share.

To request a SOV report, use the following entities.

Version 8 R4.2 (August 2012)

The following services were updated as part of this release.

Administration Release Notes

The documentation for the Administration service is being removed. In the future (the timing is to be determined), the service will also be removed. If you code against the service, you should remove this dependency.

Ad Intelligence Release Notes

The following operations now support retrieving metrics for tablet devices.

Bulk Release Notes

Updated the Schema

Updated the schema to support ad rotations and ad extensions. The AdGroup complex type now includes an AdRotation element. The ad rotation’s start and end dates are for future use and should be ignored.

The EffectiveEditorialStatus field has been removed from the Ad and Keyword objects.

The EditorialStatus field of the Ad and Keyword objects now includes ActiveLimited as a possible value. The status is set to ActiveLimited if the ad or keyword was partially approved. Partial approval can occur if the ad or keyword passed editorial review for at least one combination of language and publisher country, while other combinations failed. The ad or keyword will be active in the countries where it passed editorial review. There is currently no visibility as to which language and publisher country combinations failed.

Added Support for Downloading Ad Extensions

The AdditionalEntity value set now includes the CampaignSiteLinksAdExtensions flag. Specify the flag in your request to include site link extensions in the download. Only site links that are associated with a campaign are included in the download.

Limited the Size of the Download to 4 Million Keywords

The DownloadCampaignsByAccountIds operation limits the size of the account that you can download to four million keywords. If you try to download an account that contains more than four million keywords, the call will fail with error 3207 (AccountTooBigToDownload). If the call fails, please call the DownloadCampaignsByCampaignIds operation to download the account by campaigns. The Details element of the fault includes a comma-delimited list of the campaign IDs that the account owns.

Limited the Batch Size of DownloadCampaignsByCampaignIds

The number of campaigns that you can request to download in the DownloadCampaignsByCampaignIds operation is now limited to 1,000 campaigns.

Campaign Management Release Notes

Increased the number of Negative Site URLs per Ad Group and Campaign

The number of negative site URLs that you can specify per ad group and campaign has increased from 500 to 2,000.

This increase affects the number of AdGroupNegativeSites and CampaignNegativeSites objects that you can pass to the SetNegativeSitesToAdGroups and SetNegativeSitesToCampaigns operations, respectively.

You can pass a maximum of 5,000 objects. The total number of URLs that you can specify is 30,000; however, you should limit the total number of negative site URLs included in the specified campaigns to 10,000. For example, if you specify 2,000 URLs per campaign, the maximum number of CampaignNegativeSites objects that you should pass is 5.

You Can Now Specify How your Ads Rotate into the Auction.

You can now specify how you want your ads rotated within an ad group. Previously, the best performing ads were rotated into the auction. Now, you can continue favoring best performing ads or you can request that ads be rotated evenly into the auction.

Favoring best performing ads reduces the likelihood that new ads will be rotated into the auction in the near future. If you add seasonal ads or if you want to experiment with the ad copy of underperforming ads, you should request that ads be rotated evenly into the auction to get the ads in front of customers.

Use the following operations to get and set the type of ad rotation applied to an ad group.

Added New Location Target Codes

Added location target codes for the following countries.

  • Denmark

  • Italy

  • Netherlands

  • Norway

  • Spain

  • Sweden

Version 8 R4.1

Increased the Number of Ads per Ad Group

You can add a maximum of 50 ads to an ad group. The previous limit was 20 ads per ad group.

Version 8 R4

The following services were updated or added as part of this release.

Ad Intelligence Release Notes

Possible Breaking Change

Previously, the GetHistoricalKeywordPerformance and GetHistoricalKeywordPerformanceByDevice operations returned the CTR as a percentage (for example, 73) only if you requested data for a single country; otherwise, if you requested data for multiple countries, it returned the CTR as a decimal (for example, 0.73). Now, the operations will return the CTR as a percentage in both cases. If you included code in your application that converted the CTR from a decimal into a percentage, you will need to update your code accordingly.

Bulk Release Notes

Release of the Bulk Service

The Bulk service is a new service that you can use to download the entities of a campaign. You can request data for a list of campaigns or for all campaigns of an account. In addition, you can request that the data include all entities or only those entities that have been modified since your last download request. The entity data is written to a compressed ZIP file that you can then download. For more information, see Bulk Service.

The bulk download feature was moved from the Campaign Management service to this service. If you used the bulk download feature in the Campaign Management service, you will need to update your code to use this service. The following are the primary differences between the Bulk service usage and the Campaign Management usage.

  • Instead of calling the DownloadCampaignHierarchy operation, you will now call the DownloadCampaignsByAccountIds or DownloadCampaignsByCampaignIds operation.

  • You can now download campaign and ad group entities such as negative keywords and targets. For a list of additional entities that you can request in the download, see the AdditionalEntity value set.

  • The schema has been updated to reflect the new entities that you can include in the download. For a copy of the schema, see the Bulk Download Schema value set.

The namespace name is https://adcenter.microsoft.com/v8. For this service’s endpoint addresses, see Web Service Addresses.

This release includes the following operations.

Campaign Management Release Notes

Removed Bulk Download Support

This is a breaking change for members of the BulkDownload pilot program. The bulk download feature has moved to the Bulk service.

The following operations have been removed from the Campaign Management service.

  • DownloadCampaignHierarchy

  • GetDownloadStatus

Version 8 R3

The following services were updated as part of this release.

Ad Intelligence Release Notes

Added New Operations

The following new service operations have been added to enhance keyword research and expansion. These new operations can help you determine a keyword’s category and target users who are searching for keywords on specific device types, in specific locations, and by age and gender.

Updated the SuggestKeywordsFromExistingKeywords Operation

You can now specify the type of suggestions that the SuggestKeywordsFromExistingKeywords operation returns. For example, you can request that it return keywords from other ad groups that include the specified keyword, or return search queries that contain keywords that are related to the specified keyword.

In addition, the maximum number of suggestions that you can request has increased from 5 to 100.

Increased the Number of Allowed Keywords

The maximum number of keywords that you can specify in the following operations has increased from 100 to 1,000.

Added New Positions to AdPosition

Added the Aggregate value to the AdPosition value set. You can use it to aggregate data across ad positions.

Added a New Match Type to MatchType

Added the Aggregate value to the MatchType value set. You can use it to aggregate data across match types.

Added a New Time Period to TimeInterval

Added the LastDay value to the TimeInterval value set. You can use it to specify that you want to get performance data using the previous days data.

Campaign Release Notes

Keywords Now Support URL by Match Type

The way that you specify the match types of a keyword is changing. Previously, you would create a single Keyword object and specify a bid value for each match that you wanted to bid on (for example, exact match or phrase match). If you did not specify a bid value at the keyword-level, the default bid value specified at the ad group level was used.

Now, you must create a Keyword object for each match type that you want to bid on. For example, to bid on the keyword car by using exact match and phrase match, create a Keyword object and set the Text element to car and the ExactMatchBid element to a bid amount. Then, create a second Keyword object and set the Text element to car and PhraseMatchBid to a bid amount. When you add the keywords, you’ll get a unique keyword ID for each keyword and match-type combination.

Because this is a breaking change and will require you to update your campaign management code and may require you to update your reporting code, account managers will work with customers to migrate their accounts. After your accounts are migrated, the new keyword behavior will be enforced.

Note that the new keyword behavior will be enforced for all customers in the German, Austrian, and Swiss markets.

Added an Operation to Check the Data Migration Status

Occasionally, a new feature requires that a customer’s data be restructured. For example, to support the new URL by match type keyword model, if a customer’s keyword object contains more than one match type bid, new keyword objects will need to be created to ensure that each keyword object contains a unique keyword and match type combination.

While the customer’s data is being restructured, the customer will not be allowed to add, delete, update, or get any of their campaign entities. If you try to access an entity of an account that is being restructured, the call will fail with error 2928 (CampaignServiceCustomerDataBeingMigrated). To determine the status of the restructuring process, call the GetAccountMigrationStatuses operation.

Added a Keyword Broad Match Modifier

You can use the broad match modifier to require that specific terms in your keyword be present in the search query. To implement the broad match modifier, include a plus sign (+) in front of every term in the keyword that must be present in the search query. For example, if you bid on “Hawaii hotels”, your ad could be served for the search queries, “Hawaii beach hotels” and “Hawaii rentals.” However, if you changed the keyword to “+Hawaii +hotel”, the keyword would match only “Hawaii beach hotels.” For more information about the broad match type, see Match Type and Bid Values.

Reporting Release Notes

Added the Change History Report

The change history report shows you the campaign entities that you have access to that have been added or deleted. In addition, the report includes the old and new value of the entities whose values have been updated. For more information, see the SearchCampaignChangeHistoryReportRequest request. For a list of entities and elements that the report can include, see the Remarks section in SearchCampaignChangeHistoryReportColumn.

Added the Keyword Migration Report

The keyword migration report shows you the list of your keyword objects that were included in the keyword migration process. The migration process creates new keyword objects for keywords that contain more than one match-type bid. The result is that each keyword object will contain a unique keyword and match-type combination.

The report will include a row for the original keyword object that shows the match type that it retained, and a row for each new keyword and match-type combination created from the original keyword object. If the object was created from another keyword object, the report shows the identifier of the original keyword object.

For more information, see the KeywordMigrationReportRequest request.

Updated the Share of Voice Columns

The following are the changes to the share of voice columns.

  • The ImpressionLostToOthersPercent column is no longer supported.

  • The ImpressionLostToRankPercent data was calculated using the bid ranking and the auction ranking. The bid ranking is now reported in the new ImpressionLostToBidPercent column. For more information about the difference between the two rankings, see the description of each column.

  • The ImpressionLostToRelevancePercent data was calculated using keyword relevance and landing-page relevance. The data is now being reported in the following two new columns and the ImpressionLostToRelevancePercent is no longer supported.

    • ImpressionLostToKeywordRelevancePercent

    • ImpressionLostToLandingPageRelevancePercent

These changes apply to the following reports.

Version 8 R2.3

Campaign Management

Campaign-Level Conversion Tracking is No Longer Supported

Conversion tracking is no longer supported at the campaign level. If you set the ConversionTrackingEnabled element of the Campaign object, the value is ignored.

Calling the SetAnalyticsType operation and setting the Type element of the AccountAnalyticsType object to CampaignLevel will fail.

If your account specifies CampaignLevel analytics at the time of this release, the analytics type will change to Enabled. Your campaign-level conversion tracking script will continue to work and reporting will continue to report conversion data.

For more information about enabling account-level analytics and using goals to track conversions, see Managing Campaign Analytics.

Version 8 R2.2

Negative Keyword Behavior Changed

Previously, if you specified negative keywords at the campaign and ad group level, only the ad group's negative keywords were used to compare to the user’s query. Now, both lists will be used to compare to the user’s query. Campaign-level negative keywords are used if an ad group in the campaign does not specify negative keywords.

Device OS Targeting is No Longer in Pilot

Anyone can now target specific mobile and tablet devices and device-specific operating systems. For information about targeting devices, see the Remarks section of DeviceTarget.

Version 8 R2.1

Increased the Ad’s text length.

The maximum length of an ad’s text, after all parameter substitution strings are resolved, has increased from 70 characters to 71 characters. For information, see the Text element of the TextAd data object.

Version 8 R2

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

Campaign Management

Changes to Daily Budget Calculation

Previously, if you created a campaign and specified a daily budget, the service would calculate the monthly budget limit by multiplying the daily budget by the average number of days in a month (30.4 days).

Beginning with this release, the service will calculate the monthly budget limit by multiplying the daily budget by the number of days in the month. For more information about how the monthly limit is calculated, see the Budget Rules section of the Campaign object.

Changes to Negative Keywords

This feature will be available as early as November 10, 2011.

In addition to supporting a phrase-match comparison to determine whether a negative keyword applies to the search query, you can now choose to use an exact-match comparison. To use an exact-match comparison, enclose the negative keyword in square brackets (for example, [old dog]). For more information, see Negative Keywords.

The user’s query is now compared to both the campaign-level and ad group-level negative keywords — the ad group-level negative keywords will no longer override the campaign-level negative keywords.

Negative keywords are no longer supported at the keyword level. If you add or update negative keywords at the keyword level, the operation will not fail; however, the negative keywords will be ignored.

Added Physical Intent for Location Targeting

The service now supports the HasPhysicalIntent element of the LocationTarget object. The element determines whether the user must be physically located in the targeted location in order for the ad to display. For more information, see LocationTarget.

Changes to the Market Redefinition Pilot

Members of the Market Redefinition pilot no longer use the PublisherCountries element of the AdGroup object to specify the countries where they want the ads in the ad group to display. Instead, if you want your ads to display only in specific countries, use Country targets to identify the countries. To target countries, see LocationTarget.

Added Address and Phone Number to Text Ads

With the release of version 8, if your campaign includes a business location target, the address and phone number of the business is included in the campaign’s text ads. With this release, members of the LocalAttributes and ClickToCallOnly pilot programs can choose whether to include the address and phone number in the text ads. For more information, see the Remarks section of SetCampaignAdExtensions.

In addition, you can specify a different phone number to use in the ad instead of the one specified in the business location target. If the ad is displayed on a high fidelity mobile phone, you can also specify whether to disable the display URL link, so that the click-to-call link is the only clickable link in the ad.

The following are the operations and REST templates that you would use to get and set your preferences for including your business’ address and phone number in text ads.

Added Targeting for Tablet and Smartphone Devices and Operating Systems

This feature will be available as early as November 11, 2011.

By default, ads will target tablet devices, in addition to your current list of devices (computers and smartphones).

If you are a member of the Device OS Targeting pilot program, you can choose whether to target your ads to run on tablets. If you target tablets, you can optionally specify the operating system of the tablets to target.

Also, if you target smartphones, you can now specify the operating system of the smartphones to target.

The following are the operations to use to manage the tablet and smartphone devices that you target. For more information about using these operations, see the Remarks section of DeviceTarget.

For details about backward compatibility, see the Remarks section of DeviceTarget.

Reporting

Added the Negative Keyword Conflict Report

This report will be available as early as November 10, 2011.

The negative-keyword conflict report shows you the negative keywords in your account that conflict with the keywords in your account. For more information, see the NegativeKeywordConflictReportRequest request.

Added Columns to the Account Performance Report

The following columns have been added to the Account Performance report. For details about these columns, see the AccountPerformanceReportColumn value set.

  • DeviceOS

  • ImpressionLostToBudgetPercent

  • ImpressionLostToOthersPercent

  • ImpressionLostToRankPercent

  • ImpressionLostToRelevancePercent

  • ImpressionSharePercent

Added Columns to the Ad Group Performance Report

The following columns have been added to the Ad Group Performance report. For details about these columns, see the AdGroupPerformanceReportColumn value set.

  • DeviceOS

  • HistoricKeywordRelevance

  • HistoricLandingPageRelevance

  • HistoricLandingPageUserExperience

  • HistoricQualityScore

  • ImpressionLostToBudgetPercent

  • ImpressionLostToOthersPercent

  • ImpressionLostToRankPercent

  • ImpressionLostToRelevancePercent

  • ImpressionSharePercent

  • KeywordRelevance

  • LandingPageRelevance

  • LandingPageUserExperience

  • QualityScore

Added Columns to the Campaign Performance Report

The following columns have been added to the Campaign Performance report. For details about these columns, see the CampaignPerformanceReportColumn value set.

  • DeviceOS

  • HistoricKeywordRelevance

  • HistoricLandingPageRelevance

  • HistoricLandingPageUserExperience

  • HistoricQualityScore

  • ImpressionLostToBudgetPercent

  • ImpressionLostToOthersPercent

  • ImpressionLostToRankPercent

  • ImpressionLostToRelevancePercent

  • ImpressionSharePercent

  • KeywordRelevance

  • LandingPageRelevance

  • LandingPageUserExperience

  • QualityScore

Added Columns to the Keyword Performance Report

The following columns have been added to the Keyword Performance report. For details about these columns, see the KeywordPerformanceReportColumn value set.

  • HistoricKeywordRelevance

  • HistoricLandingPageRelevance

  • HistoricLandingPageUserExperience

  • HistoricQualityScore

Added Column to the Search Query Performance Report

The following column has been added to the Search Query Performance report. For details about these columns, see the SearchQueryPerformanceReportColumn value set.

  • KeywordId

Added a Filter Value to DeviceTypeReportFilter

Tablet has been added as a possible filter value to the DeviceTypeReportFilter value set, which lets you filter report data for ads that were displayed on tablet devices.

Version 8 R1

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

Customer Management

Added the FindAccountsOrCustomersInfo Operation

Added the FindAccountsOrCustomersInfo operation, which you can use to get a list of accounts and customers that match the specified filter criteria.

Optimizer

Release of the Optimizer Service

Optimizer is a new service that you can use to find campaign’s whose budgets can be optimized to improve clicks and impressions. The namespace name of the service is https://adcenter.microsoft.com/v8. For the service address, see Web Service Addresses.

This release includes the following operations.

Version 8

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

Ad Intelligence

Added Support for India

You can now specify India as a publisher country when calling the following operations.

The Currency value set now includes the Indian rupee, which you can specify when calling the GetEstimatedBidByKeywords and GetEstimatedPositionByKeywords operations.

Release of the Ad Intelligence Service

Ad Intelligence is a new service that replaces the Keyword Services Platform (KSP). The namespace name is https://adcenter.microsoft.com/v8. For the service address, see Web Service Addresses.

This release includes the following operations.

Administration

Updated the Version Number

The namespace has been changed to reflect the new version number of this release; otherwise, there are no updates to the Administration API. The new namespace name is https://adcenter.microsoft.com/v8.

Campaign Management

Updated the Version Number

The namespace has been changed to reflect the new version number for this release. The new namespace name is https://adcenter.microsoft.com/v8. For the new service address, see Web Service Addresses.

Added Bulk Downloads

You can now download the entities of the specified campaigns or the entities of all of the campaigns in the specified account. You can request all entities of the campaign or only those that have changed since the last time you synced the campaign data. For details, see Bulk Downloads and the following operations.

  • DownloadCampaignHierarchy

  • GetDownloadStatus

This release will not include the ability to download negative keywords, negative site URLs, nor targets.

Changed the Budget Types that You Can Specify for a Campaign

The following budget types have been removed from BudgetLimitType.

  • DailyBudgetWithMaximumMonthlySpend

  • MonthlyBudgetDivideDailyAcrossMonth

The following budget types have been added.

  • DailyBudgetAccelerated

  • DailyBudgetStandard

The DailyBudgetAccelerated type replaces the DailyBudgetWithMaximumMonthlySpend. With this option, the daily budget is spent until it is depleted. If you want the daily budget to be spread throughout the day, you should use the DailyBudgetStandard budget type, which replaces the MonthlyBudgetDivideDailyAcrossMonth budget type.

In both cases, you no longer specify a monthly limit, which the service calculates by multiplying the daily budget by the average number of days in a month.

Changed the Campaign Object

The following elements have been removed from the Campaign object.

  • CashBackInfo

  • ConversionTrackingScript

  • NegativeKeywords

  • NegativeSiteUrls

To get or set the negative keywords and site URLs for a campaign, you now call the following operations.

Changed the AdGroup Object

The following elements have been removed from the AdGroup object.

  • CashBackInfo

  • LanguageAndRegion

  • NegativeKeywords

  • NegativeSiteUrls

To get or set the negative keywords and site URLs for an ad group, you now call the following operations.

The following elements have been added to the AdGroup object.

  • Language

  • Network

  • PublisherCountries

The Language and PublisherCountries elements replace the LanguageAndRegion element for specifying the publisher countries where your ads display—and within those countries—the language-specific websites where your ads display.

Because you now use the Network element to specify the search network where your ads are displayed (for example, owned and operated, syndicated, or both), the GetNetworksByAdGroupIds and SetNetworksToAdGroups operations were removed.

Removed the AdGroupInfo and CampaignInfo Data Objects and the Operations that Return Them

The following operations have been removed because the AdGroup and Campaign objects no longer contain the negative keywords and site URLs.

  • GetAdGroupsInfoByCampaignId

  • GetCampaignsInfoByAccountId

Removed Support for Behavioral and User Segment Targeting

The following operations related to behavioral targeting have been removed.

  • AddBehavioralBids

  • DeleteBehavioralBids

  • GetBehavioralBidsByAdGroupId

  • GetBehavioralBidsByIds

  • PauseBehavioralBids

  • ResumeBehavioralBids

  • UpdateBehavioralBids

The following operations related to user segment targeting have been removed.

  • AddSegments

  • DeleteSegments

  • DeleteUsersFromSegment

  • GetCustomSegments

  • GetSegments

  • GetSegmentsByIds

  • SetUsersToSegments

The Behavior and Segment elements from the Target object have been removed.

The OverridePriority element of the Keyword object has been removed. Because segment targeting was removed, the dynamic substitution values that expand the text, title, and display URL of an ad now come only from the Keyword object.

Other Targeting Changes

In addition to removing behavioral and user segment targeting as described above, new elements were added to the following targeting objects.

  • The HasPhysicalIntent element was added to the LocationTarget object. This element is for future use.

  • The Id and Name elements were added to the RadiusTargetBid object. These elements are for future use.

Changed the Data Type of the Language Element of the GetNormalizedStrings Operation

The Language element of the GetNormalizedStringsRequest message was changed from a Language value set type to a string type. For a list of language values that you can use, see Language Values. You can specify only English and French.

Content Match is no Longer in Pilot

Anyone can specify the content ad distribution model (see AdGroup); however, the content model is limited to the U.S., Canadian, and Indian markets.

Removed all References to the Cashback Feature, Which is no Longer Supported

Removed the GetKeywordEstimatesByBids Operation

You now use the operations in the Ad Intelligence service to get this information.

Customer Billing

Updated the Version Number

Released a new version of the Customer Billing API. The new version number is v8. The namespace name remains https://adcenter.microsoft.com/api/customerbilling. For the new service address, see Web Service Addresses.

Designated the AddInsertionOrder and UpdateInsertionOrder operations as for internal use only.

Customer Management

Updated the Version Number

Released a new version of the Customer Management API. The new version number is v8. The namespace name remains https://adcenter.microsoft.com/api/customermanagement. For the new service address, see Web Service Addresses.

Added New Operations

The following operations have been added.

  • FindAccounts – Gets a list of accounts based on a partial or full account name or number.

  • GetAccessibleCustomer – For internal use only.

  • GetPilotFeaturesCountries – For internal use only.

Changes to the Customer Object

The following Customer element names have been changed.

  • FinancialStatus is now CustomerFinancialStatus.

  • Status is now CustomerLifeCycleStatus.

The MarketCountry and MarketLanguage elements replaced the Market element. These elements determine the default PublisherCountry and Language values to use for ad groups in the customer’s campaigns.

Added the Number element, which contains the system-generated customer number that is used to identify the customer in the Bing Ads web application.

Changes to the Account and AccountInfo Objects

The following Account element names have been changed.

  • FinancialStatus is now AccountFinancialStatus.

  • Status is now AccountLifeCycleStatus.

The following AccountInfo element name has been changed.

  • Status is now AccountLifeCycleStatus.

Changes to the User Object

The following User element name has been changed.

  • Status is now UserLifeCycleStatus.

Changed the Name of the UserStatus Value Set.

The name of the UserStatus value set has been changed to UserLifeCycelStatus. This affects the data type of the UserLifeCycleStatus element of the User object and the StatusFilter element of the GetUsersInfoRequest message.

Added New Language Values

The following language values have been added to the LanguageType value set.

  • Arabic

  • Hebrew

  • Korean

  • Russian

  • Chinese

Added a New Status to AccountLifeCycleStatus

The Pending status has been added to the AccountLifeCycleStatus value set. The status is for internal use only.

Added Pharmaceuticals to the Industry Value Set

Pharmaceuticals has been added to the Industry value set.

Notification

Updated the Version Number

Released a new version of the Notification API. The new version number is v8. The namespace name remains https://adcenter.microsoft.com/api/notifications. For the new service address, see Web Service Addresses.

Updated the Data Type of the BudgetAmount and EstimatedBudgetBalance Elements

Changed the data type from decimal to double for the following elements.

Reporting

Updated the Namespace

The namespace has been changed to reflect the new version number of this release. The new namespace name is https://adcenter.microsoft.com/v8. For the new service address, see Web Service Addresses.

Added New Columns to SearchQueryPerformanceReport

The following columns have been added to the SearchQueryPerformanceReportColumn value set.

ConversionRate

The report will include a column that contains the conversion rate as a percentage. The conversion rate is calculated by dividing the number of conversions by the total number of clicks.

Conversions

The report will include a column that contains the number of conversions.

CostPerConversion

The report will include a column that contains the cost per conversion. The cost per conversion is calculated by dividing the amount spent by the number of conversions.

Did you find this helpful?
(1500 characters remaining)

Community Additions

ADD
© 2013 Microsoft. All rights reserved.