Developer Center (English) > Announcement > Release date for YDN API targeting feature enhancement

ここから本文です
        

Feb-14-2019

Release date for YDN API targeting feature enhancement

*Update as of February 27, 2019
The enhancement has been released as scheduled.
-----------------------------------------------------
Document Number: APIE-FY18-2063

Dear customer,

Thank you for using Yahoo! JAPAN Promotional Ads.

The release date has been decided for the enhancements that will
be made to the targeting feature in Yahoo! JAPAN Display Ad Network
(YDN), previously announced in "YDN targeting feature enhancement
(Document Number: APIE-FY18-2013)". Please see below for details.

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


1. Product:
YDN API

2. Schedule:
February 26, 2019 (Tue) 10:00 PM - February 27, 2019 (Wed) 7:00 AM (JST)
 *Schedule may change without prior notice.
 *System error may occur when using YDN API during the maintenance.

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

4. Overview:
The following changes will be made on targeting feature in YDN.

4-1. Bid Adjustment setting for each predicted user
  Within gender and age targeting, setting individual bid adjustment
  for predicted users of the selected gender or age will be available.
  Difference between the existing predictive targeting is below.

  <Before>
  Setting bid adjustment collectively for users of the selected
  gender or age and predicted users.
  The display on the UI will be "Male (predicted)".
  <After>
  Setting bid adjustment individually for users of the selected
  gender or age and predicted users.
  The display on the UI will be divided into "Male" and "Male
  (predicted)".
  *Targeting predicted users only is not available.

  Example setting after effective date
  Adjust bid on gender targeting to deliver ads mainly to male users.
  - Male: Increase by 50%
  - Male (predicted): Increase by 25%
  *For the case above, setting only "Male (predicted)" will not be
  allowed. Please set "Male" and "Male (predicted)" together.

  "EstimateFlg" which is used on "AgeTarget" and on "GenderTarget"
  of YDN API "AdGroupTargetService" will have following changes on
  its values.
  <Before>
  - PAUSED : Predictive targeting is not available
  - ACTIVE : Predictive targeting is available
  <After>
  - PAUSED : Deliver ads to users as designated gender or ages
  - ACTIVE : Deliver ads to users who can be estimated as designated
        gender or ages

  After the effective date, you need to set both "PAUSED" and
  "ACTIVE" when you set targeting for estimated users.
  Setting "ACTIVE" only is not available.
 
  This change above will be applied to all available versions.

4-2. Changes in 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.
   *Operation history will also be displayed as above.

  Due to this change, the current format of the download file will
  not be valid so please download the latest file to import data
  after the effective date.
  Please download the latest file from BulkService to import data
  after the effective date.

  *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-3. Changes in 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.

(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:
 Targeting in YDN enables you to deliver ads to users who meet
 the specified conditions such as gender and location. Effective
 advertising can be expected by narrowing down the target for ad
 delivery to potential customers of the service/product, and by
 adjusting bids depending on the conditions.
 Please refer to the help pages below for more details.
 - Targeting Overview 
 - Set Bid Adjustment Rate for Each Targeting
  

If you have any questions, please contact us.

Sincerely,
Yahoo! JAPAN API support team

        
Text ends here Top of page