AddAds Service Operation - Campaign Management

Adds one or more ads to an ad group.


Standard Text Ads have been deprecated in favor of Expanded Text Ads (EXTAs). Support for adding and updating standard text ads (STAs) ended on July 31, 2017. Now, advertisers can get and delete, but can no longer add new STAs or update existing standard text ads with Destination URLs. One exception to the rule, is that you can still update the STA status e.g. from Active to Paused. Otherwise attempts to add or update STAs will result in the CampaignServiceAdTypeInvalid error.

It is important to note that all your existing STAs will continue to serve alongside EXTAs for the foreseeable future. While there is no date on when STAs will stop serving, you can expect an update to all of our customers well in advance once we make the decision to sunset serving STAs.

Request Elements

The AddAdsRequest object defines the body and header elements of the service operation request. The elements must be in the same order as shown in the Request SOAP.

Request Body Elements

Element Description Data Type
AdGroupId The identifier of the ad group to add the ads to. long
Ads An array of up to 50 ads that you want added to the ad group. Ad array

Request Header Elements

Element Description Data Type
AuthenticationToken The OAuth access token that represents a Microsoft Account user who has permissions to Bing Ads accounts. string
CustomerAccountId The identifier of the account that owns the entities in the request. This header element must have the same value as the AccountId body element when both are required. string
CustomerId The identifier of the customer that contains and owns the account. If you manage an account of another customer, you should use that customer ID instead of your own customer ID. string
DeveloperToken The developer token used to access the Bing Ads API. string
Password The Bing Ads managed user's sign-in password. string
UserName The Bing Ads managed user's sign-in name. You must not set this element to a Microsoft account or email address. string


The UserName and Password header elements are deprecated. In future versions of the API, Bing Ads will transition exclusively to Microsoft Account (email address) authentication. For more information, see Authentication with OAuth. UserName and Password are still required for Bing Ads managed credentials, but they are not applicable for Microsoft account authentication. To authenticate a Microsoft account, use the AuthenticationToken] header instead of UserName and Password.


The CustomerAccountId and CustomerId are required for most service operations, and as a best practice you should always specify them in the request.

Response Elements

The AddAdsResponse object defines the body and header elements of the service operation response. The elements are returned in the same order as shown in the Response SOAP.

Response Body Elements

Element Description Data Type
AdIds A list of unique system identifiers corresponding to the ads that were added.

The list of identifiers corresponds directly to the list of ads in the request. Items of the list may be returned as null. For each list index where an ad was not added, the corresponding element will be null.
long array
PartialErrors An array of BatchError objects that contain details for any request items that were not successful.

The list of errors do not correspond directly to the list of items in the request. The list can be empty if there were no errors, or can include one or more error objects corresponding to each unsuccessful list item in the request.
BatchError array

Response Header Elements

Element Description Data Type
TrackingId The identifier of the log entry that contains the details of the API call. string

Request SOAP

The following template shows the order of the body and header elements for the SOAP request.

<s:Envelope xmlns:i="" xmlns:s="">
  <s:Header xmlns="">
    <Action mustUnderstand="1">AddAds</Action>
    <ApplicationToken i:nil="false">ValueHere</ApplicationToken>
    <AuthenticationToken i:nil="false">ValueHere</AuthenticationToken>
    <CustomerAccountId i:nil="false">ValueHere</CustomerAccountId>
    <CustomerId i:nil="false">ValueHere</CustomerId>
    <DeveloperToken i:nil="false">ValueHere</DeveloperToken>
    <Password i:nil="false">ValueHere</Password>
    <UserName i:nil="false">ValueHere</UserName>
    <AddAdsRequest xmlns="">
      <Ads i:nil="false">
        <Ad i:type="-- derived type specified here with the appropriate prefix --">
          <AdFormatPreference i:nil="false">ValueHere</AdFormatPreference>
          <DevicePreference i:nil="false">ValueHere</DevicePreference>
          <EditorialStatus i:nil="false">ValueHere</EditorialStatus>
          <FinalAppUrls xmlns:e121="" i:nil="false">
              <e121:OsType i:nil="false">ValueHere</e121:OsType>
              <e121:Url i:nil="false">ValueHere</e121:Url>
          <FinalMobileUrls i:nil="false" xmlns:a1="">
          <FinalUrls i:nil="false" xmlns:a1="">
          <ForwardCompatibilityMap xmlns:e122="" i:nil="false">
              <e122:key i:nil="false">ValueHere</e122:key>
              <e122:value i:nil="false">ValueHere</e122:value>
          <Id i:nil="false">ValueHere</Id>
          <Status i:nil="false">ValueHere</Status>
          <TrackingUrlTemplate i:nil="false">ValueHere</TrackingUrlTemplate>
          <Type i:nil="false">ValueHere</Type>
          <UrlCustomParameters xmlns:e123="" i:nil="false">
            <e123:Parameters i:nil="false">
                <e123:Key i:nil="false">ValueHere</e123:Key>
                <e123:Value i:nil="false">ValueHere</e123:Value>
          <!--These fields are applicable if the derived type attribute is set to TextAd-->
          <DestinationUrl i:nil="false">ValueHere</DestinationUrl>
          <DisplayUrl i:nil="false">ValueHere</DisplayUrl>
          <Text i:nil="false">ValueHere</Text>
          <Title i:nil="false">ValueHere</Title>
          <!--This field is applicable if the derived type attribute is set to ProductAd-->
          <PromotionalText i:nil="false">ValueHere</PromotionalText>
          <!--These fields are applicable if the derived type attribute is set to AppInstallAd-->
          <AppPlatform i:nil="false">ValueHere</AppPlatform>
          <AppStoreId i:nil="false">ValueHere</AppStoreId>
          <Text i:nil="false">ValueHere</Text>
          <Title i:nil="false">ValueHere</Title>
          <!--These fields are applicable if the derived type attribute is set to ExpandedTextAd-->
          <DisplayUrl i:nil="false">ValueHere</DisplayUrl>
          <Path1 i:nil="false">ValueHere</Path1>
          <Path2 i:nil="false">ValueHere</Path2>
          <Text i:nil="false">ValueHere</Text>
          <TitlePart1 i:nil="false">ValueHere</TitlePart1>
          <TitlePart2 i:nil="false">ValueHere</TitlePart2>
          <!--These fields are applicable if the derived type attribute is set to DynamicSearchAd-->
          <Path1 i:nil="false">ValueHere</Path1>
          <Path2 i:nil="false">ValueHere</Path2>
          <Text i:nil="false">ValueHere</Text>

Response SOAP

The following template shows the order of the body and header elements for the SOAP response.

<s:Envelope xmlns:s="">
  <s:Header xmlns="">
    <TrackingId d3p1:nil="false" xmlns:d3p1="">ValueHere</TrackingId>
    <AddAdsResponse xmlns="">
      <AdIds d4p1:nil="false" xmlns:a1="" xmlns:d4p1="">
      <PartialErrors d4p1:nil="false" xmlns:d4p1="">
        <BatchError d4p1:type="-- derived type specified here with the appropriate prefix --">
          <Details d4p1:nil="false">ValueHere</Details>
          <ErrorCode d4p1:nil="false">ValueHere</ErrorCode>
          <FieldPath d4p1:nil="false">ValueHere</FieldPath>
          <ForwardCompatibilityMap xmlns:e124="" d4p1:nil="false">
              <e124:key d4p1:nil="false">ValueHere</e124:key>
              <e124:value d4p1:nil="false">ValueHere</e124:value>
          <Message d4p1:nil="false">ValueHere</Message>
          <Type d4p1:nil="false">ValueHere</Type>
          <!--These fields are applicable if the derived type attribute is set to EditorialError-->
          <Appealable d4p1:nil="false">ValueHere</Appealable>
          <DisapprovedText d4p1:nil="false">ValueHere</DisapprovedText>
          <Location d4p1:nil="false">ValueHere</Location>
          <PublisherCountry d4p1:nil="false">ValueHere</PublisherCountry>

Code Syntax

The example syntax can be used with Bing Ads SDKs. See Bing Ads Code Examples for more examples.

public async Task<AddAdsResponse> AddAdsAsync(
    long adGroupId,
    IList<Ad> ads)
    var request = new AddAdsRequest
        AdGroupId = adGroupId,
        Ads = ads

    return (await CampaignManagementService.CallAsync((s, r) => s.AddAdsAsync(r), request));
static AddAdsResponse addAds(
    java.lang.Long adGroupId,
    ArrayOfAd ads) throws RemoteException, Exception
    AddAdsRequest request = new AddAdsRequest();


    return CampaignManagementService.getService().addAds(request);
static function AddAds(

    $GLOBALS['Proxy'] = $GLOBALS['CampaignManagementProxy'];

    $request = new AddAdsRequest();

    $request->AdGroupId = $adGroupId;
    $request->Ads = $ads;

    return $GLOBALS['CampaignManagementProxy']->GetService()->AddAds($request);


Service: CampaignManagementService.svc v11