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.

• GetHistoricalKeywordPerformanceByDevice

• GetHistoricalSearchCountByDevice

• GetKeywordCategories

• GetKeywordDemographics

• GetKeywordLocations

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.

• GetEstimatedBidByKeywordIds

• GetEstimatedBidByKeywords

• GetEstimatedPositionByKeywordIds

• GetEstimatedPositionByKeywords

• GetHistoricalKeywordPerformance

• GetHistoricalSearchCount

• SuggestKeywordsFromExistingKeywords

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.

Keywords Now Support URL by Match Type

adCenter is changing the way that you specify the match types of a keyword. 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, adCenter used the default bid value specified at the ad group level.

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, adCenter will work with customers to migrate their accounts. For information about how your existing keywords will be migrated to the new structure, see URL by Match Type Data Migration. After your accounts are migrated, the new keyword behavior will be enforced.

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

For information about changes that you will need to make to your campaign code to support URL by match type, see the Remarks section of the Keyword object.

For information about changes that you may need to make to your reporting code to support URL by match type, see the Remarks section of KeywordPerformanceReportRequest.

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.

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.

• AccountPerformanceReportColumn

• AdGroupPerformanceReportColumn

• CampaignPerformanceReportColumn

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 have adCenter 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.

adCenter no longer supports negative keywords 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.

• GetCampaignAdExtensions operation

• SetCampaignAdExtensions operation

• GetCampaignAdExtensions REST template

• SetCampaignAdExtensions REST template

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.

• GetDeviceOSTargetsByIds

• UpdateDeviceOSTargets

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

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.

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.

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.

• GetBudgetOpportunities

• ApplyBudgetOpportunities

Added Support for India

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

• GetEstimatedBidByKeywords

• GetEstimatedPositionByKeywords

• GetHistoricalKeywordPerformance

• GetHistoricalSearchCount

• SuggestKeywordsFromExistingKeywords

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.

• GetEstimatedBidByKeywordIds

• GetEstimatedBidByKeywords

• GetEstimatedPositionByKeywordIds

• GetEstimatedPositionByKeywords

• GetHistoricalKeywordPerformance

• GetHistoricalSearchCount

• SuggestKeywordsForUrl

• SuggestKeywordsFromExistingKeywords

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. For the new service address, see Web Service Addresses.

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.

• GetNegativeKeywordsByCampaignIds

• SetNegativeKeywordsToCampaigns

• GetNegativeSitesByCampaignIds

• SetNegativeSitesToCampaigns

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.

• GetNegativeKeywordsByAdGroupIds

• SetNegativeKeywordsToAdGroups

• GetNegativeSitesByAdGroupIds

• SetNegativeSitesToAdGroups

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.

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.

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 adCenter 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.

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.

• The BudgetAmount element of CampaignInfo

• The EstimatedBudgetBalance element of LowBudgetBalanceCampaignInfo

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.