Managing Editorial Review and Appeals
For an ad to be eligible to be served, it must meet the editorial guidelines of the market that it serves. The same is true for ad extensions and keywords. For editorial guidelines by market, see Editorial Guidelines.
For information about the editorial review process and how to determine whether the entity passed or failed the review, see the following sections.
To find ads or keywords that failed the editorial review process, call the respective GetAdsByEditorialStatus or GetKeywordsByEditorialStatus operation. Set the EditorialStatus element to Disapproved.
To determine the reason why an ad or keyword failed the review and whether it’s appealable, call the respective GetEditorialReasonsByIds operation. The operation returns an array of EditorialReasonCollection objects. The rejection is appealable if the AppealStatus element of EditorialReasonCollection is set to Appealable. For possible status values, see AppealStatus.
For a list of the possible reason codes for an ad or keyword that failed editorial review, see Bing Ads Editorial Failure Reason Codes. The codes can be returned in the ReasonCode element of the EditorialReason object.
If the failure is appealable, call the AppealEditorialRejections operation to appeal the rejection. You can request a maximum of 2,000 appeals per account per 24-hour rolling window. For example, if you request 2,000 appeals at 10:00 AM PST today, you cannot request new appeals until after 10:00 AM PST tomorrow. The maximum number of appeals that you can have pending for a single account is 10,000.
You cannot call AppealEditorialRejections to appeal ad extensions that failed editorial review.
Entities and Delivery Status
For example after adding a new keyword or ad which must go through the offline review process, read operations such as GetKeywordsByIds or GetAdsByIds will return Disapproved, and the delivery status in the web application will indicate that the entity is pending editorial review. The delivery status in the web application will indicate that the entity is disapproved if and when all elements of the keyword or ad are rejected.
If you have updated a previously approved and active keyword or ad, and if any element of that entity must go through the offline review process, then read operations such as GetKeywordsByIds or GetAdsByIds will return Inactive and the delivery status in the web application will indicate that the entity is pending editorial review.
For an entity undergoing offline review the editorial status may be either Active or Inactive, determined respectively by whether a reviewable term is considered to have a low or high risk of rejection.
Ad Editorial Review
Before an ad can be served, it must pass editorial review. An initial review is performed at the time you add the ad to an ad group. If the ad fails the initial review, the AddAds operation throws an editorial fault, which identifies the editorial issue. If the initial review succeeds, the ad is added to the ad group.
The ad then goes through an in-depth review in the background. To find ads that failed the more in-depth review, call the GetAdsByEditorialStatus operation. To determine the reason why an ad failed the review and whether it’s appealable, call the GetEditorialReasonsByIds operation.
If the status of an ad group is Draft, the ads will begin the in-depth review when you update its status to Paused or Active.
If an ad is updated, it is subject to the same review process as a new ad. Effectively the ad is paused unless or until the updated ad copy is immediately approved.
Ad Extension Editorial Review
When you associate an ad extension with a campaign or ad group, the extension goes through an initial editorial review. The review is performed for each publisher country that supports the languages specified in the campaign’s ad groups. If the extension fails the initial review, the operation fails and returns an editorial fault. The fault’s Details element contains the term that failed review. If the extension passes the initial review, the extension then goes through an in-depth, offline editorial review.
If the IconMediaId or ImageMediaId elements of a LocationAdExtension are set with custom media, the location ad extension validations are done offline. Otherwise all ad extension editorial validations occur up front when associated with an entity.
Because the editorial review is conducted in the context of the campaign or ad group, the extension is reviewed each time you associate the extension with a campaign or ad group. In addition, the extension associated with a campaign will go through a review anytime you add to the campaign an ad group which specifies a different language, or you target a different country at the campaign or ad group level.
To determine whether the extension passed the in-depth review with associated entities, call the GetAdExtensionsAssociations operation. The response contains one or more lists of AdExtensionAssociation objects. The extension passed editorial review if the EditorialStatus element is set to Active. If the status is set to ActiveLimited or Disapproved, call the GetAdExtensionsEditorialReasons operation to identify the countries where the extension failed review and the reason for the failure.
Keyword Editorial Review
When you add keywords, they go through an initial editorial review. If a keyword fails the initial review, the AddKeywords operation fails and throws an editorial fault that identifies the editorial issues. If the initial review succeeds, the keywords are added to the ad group. They then go through an in-depth review in the background.
To find keywords that failed the more in-depth review, call the GetKeywordsByEditorialStatus operation. To determine the reason why a keyword failed the review and whether it’s appealable, call the GetEditorialReasonsByIds operation.
If the status of an ad group is Draft, the keywords will begin the in-depth review when you update its status to Paused or Active.