Developer Center (English) > Announcement > Additional information on YDN Targeting feature enhancement

ここから本文です
        

Jan-22-2019

Additional information on YDN Targeting feature enhancement

Document Number: APIE-FY18-2044

Dear customer,

Thank you for using Yahoo! JAPAN Promotional Ads.

There are some additional note on the enhancement previously announced on "YDN targeting feature enhancement (Document Number : APIE-FY18-2013)" for YDN API users. Please see below for details.

Once again, thank you for using Yahoo! JAPAN Promotional Ads.


1. Product:
Yahoo! JAPAN Display Ad Network (YDN)

2. Versions to be effected:
All available versions (V201806, V201809, V201812)

3. Schedule:
Late February, 2019
* Please wait for further announcements regarding details.
The date may change without prior notice.

4. Overview:
For YDN API users, please confirm the following points regarding this enhancement on Targeting feature.

4-1. Change of Download File
These changes will be made on Download File as part of enhancement.

  • A new item "Targeting" will be added.
  • Existing item "Predictive Targeting" will be renamed to "Predicted Users".
  • The setting data of Age Targeting and Gender Targeting is currently shown in one line. However after the effective date, setting data of Age and Gender Targeting will each be shown in two lines by predicted user and confirmed user.

*The update of download file in detail is thus below.


With this change, the current format of Download File will be invalid. Please download the latest file from BulkService to import data after the effective date.

4-2. Change Response
The response and requests of mutate (add)/replace of AdGroupTargetService will be changed, to set/respond each of confirmed and predicted users.
When using AdGroupTargetService, please confirm and change your program if necessary.
*Sample codes of the response and requests are as follows:

(1)Sample of response : currently provided

<ns2:values>
   <ns1:operationSucceeded>true</ns1:operationSucceeded>
   <ns2:adGroupTargetList>
      <ns2:accountId>1234567890</ns2:accountId>
      <ns2:campaignId>10001</ns2:campaignId>
      <ns2:adGroupId>20001</ns2:adGroupId>
      <ns2:bidMultiplier>1</ns2:bidMultiplier>
      <ns2:target xsi:type="ns2:GenderTarget">
         <ns2:type>GENDER_TARGET</ns2:type>
         <ns2:targetId>aa111111</ns2:targetId>
         <ns2:gender>ST_MALE</ns2:gender>
         <ns2:estimateFlg>ACTIVE</ns2:estimateFlg>
      </ns2:target>
   </ns2:adGroupTargetList>
</ns2:values>


(2)Sample of response : after the scheduled update

<ns2:values>
   <ns1:operationSucceeded>true</ns1:operationSucceeded>
   <ns2:adGroupTargetList>
      <ns2:accountId>1234567890</ns2:accountId>
      <ns2:campaignId>10001</ns2:campaignId>
      <ns2:adGroupId>20001</ns2:adGroupId>
      <ns2:bidMultiplier>1</ns2:bidMultiplier>
      <ns2:target xsi:type="ns2:GenderTarget">
         <ns2:type>GENDER_TARGET</ns2:type>
         <ns2:targetId>aa111110</ns2:targetId>
         <ns2:gender>ST_MALE</ns2:gender>
         <ns2:estimateFlg>PAUSED</ns2:estimateFlg>
      </ns2:target>
   </ns2:adGroupTargetList>
</ns2:values>
<ns2:values>
   <ns1:operationSucceeded>true</ns1:operationSucceeded>
   <ns2:adGroupTargetList>
      <ns2:accountId>1234567890</ns2:accountId>
      <ns2:campaignId>10001</ns2:campaignId>
      <ns2:adGroupId>20001</ns2:adGroupId>
      <ns2:bidMultiplier>1</ns2:bidMultiplier>
      <ns2:target xsi:type="ns2:GenderTarget">
         <ns2:type>GENDER_TARGET</ns2:type>
         <ns2:targetId>aa111111</ns2:targetId>
         <ns2:gender>ST_MALE</ns2:gender>
         <ns2:estimateFlg>ACTIVE</ns2:estimateFlg>
      </ns2:target>
   </ns2:adGroupTargetList>
</ns2:values>

(3)Sample of request, mutate (add) and replace: currently provided

<ns2:operand>
   <ns2:campaignId>10001</ns2:campaignId>
   <ns2:adGroupId>20001</ns2:adGroupId>
   <ns2:bidMultiplier>1</ns2:bidMultiplier>
   <ns2:target xsi:type="ns2:GenderTarget">
         <ns2:type>GENDER_TARGET</ns2:type>
         <ns2:targetId>aa111111</ns2:targetId>
         <ns2:gender>ST_MALE</ns2:gender>
         <ns2:estimateFlg>ACTIVE</ns2:estimateFlg>
      </ns2:target>
</ns2:operand>

(4)Sample of request, mutate (add) and replace: after the scheduled update

<ns2:operand>
   <ns2:campaignId>10001</ns2:campaignId>
   <ns2:adGroupId>20001</ns2:adGroupId>
   <ns2:bidMultiplier>1</ns2:bidMultiplier>
   <ns2:target xsi:type="ns2:GenderTarget">
         <ns2:type>GENDER_TARGET</ns2:type>
         <ns2:targetId>aa111110</ns2:targetId>
         <ns2:gender>ST_MALE</ns2:gender>
         <ns2:estimateFlg>PAUSED</ns2:estimateFlg>
      </ns2:target>
</ns2:operand>
<ns2:operand>
   <ns2:campaignId>10001</ns2:campaignId>
   <ns2:adGroupId>20001</ns2:adGroupId>
   <ns2:bidMultiplier>1</ns2:bidMultiplier>
   <ns2:target xsi:type="ns2:GenderTarget">
         <ns2:type>GENDER_TARGET</ns2:type>
         <ns2:targetId>aa111111</ns2:targetId>
         <ns2:gender>ST_MALE</ns2:gender>
         <ns2:estimateFlg>ACTIVE</ns2:estimateFlg>
      </ns2:target>
</ns2:operand>


5. Remarks:
- Previous notification of this enhancement is available on the following page.
"YDN targeting feature enhancement"


If you have any questions, please contact us.

Sincerely,
Yahoo! JAPAN API support team

        
Text ends here Top of page