Yahoo! JAPAN Ads API | Developer Center

日本語

Display Ads API v16 Release Note

Version released

v16

Date

February 17, 2025

Key points of this release

*Learn more about objects, etc. in the reference document.
Reference Document

1. Bid strategy "Maximize conversion value" (beta)

We released "Maximize conversion value" (beta) a bid strategy that automatically adjusts bids to maximize the "Conversion value" set in your conversion settings. Target ROAS is also available. You can use both features only after the release. Learn more
Bid strategy "Maximize conversion value" (beta version) will be available

  • Services
    • CampaignService
    • AdGroupService
  • Changes
    • You will be able to specify the bid strategy "MAXIMIZE_CONVERSION_VALUE" (Maximize conversion value).
    • When specifying "MAXIMIZE_CONVERSION_VALUE" as the bid strategy, you can optionally specify "maximizeValuesBiddingScheme.targetRoas" (target ROAS). If not specified, it will be set as "Maximize conversion value" without target value.

2. Audience data connections from LINE Ads and LINE Official Accounts

You can deliver ads using the audience data from LINE Ads and LINE Official Accounts. The Display Ads account and LINE Ads account, or LINE Official Account must be linked to connect the audience data. Learn more in the following announcement.
Audience data connections from LINE Ads and LINE Official Accounts

  • Services
    • AudienceListService /get
    • AdGroupTargetService
  • Changes
    • You can specify BUSINESS_MANAGER in audienceListTypes of AudienceListService /get. In this case, businessManagerAudienceList will return.
    • You can specify BUSINESS_MANAGER in the audienceListType of the AdGroupTargetService.

3. Placement targeting enhancement

You can add ad place names. *This feature is already available in the Campaign Management Tool. Learn more in the following announcement.
Placement targeting enhancement

  • Services
    • PlacementUrlIdeaService/get
  • Changes
    • Add adPlaceName (ad place name) to the response field.
    • You can search by specifying the name of the ad place name in using keyword of the request field.
    • Add the following items to the request field to narrow down the search.
      • keywordFilterTypes: You can narrow down the type (URL and ad place name).
      • adPlaceFilterTypes: You can narrow down the ad place type (main ad place).
      • lang: You can narrow down the language of the ad place.
      • unknownUrlFilterType: You can narrow down unknown URLs (show or hide) in search results.
      • sortFiled: Specifies the item to be sorted.
      • sortType: specifies the sorting method.

4. Change review start timing of images and videos

We changed the start timing of the review process for images and videos to optimize the review process. You can use both features only after the release. See the following announcement for details.
Change review start timing of images and videos

  • Services
    • MediaService
    • VideoService
  • Changes
    • Added PENDING_UNSPECIFIED_AD (pending due to unspecified ad) to approvalStatus.
    • For the following field, the date and time was included at the time of image and video review, but this has changed to the timing when the image and video is associated to the ad and reviewed. The field name changed from v16.
      • MediaService
        creationTime → reviewApplicationDate
      • VideoService
        createdDateTime → reviewApplicationDate
    • In versions prior to v15, the behavior is as follows. Data with PENDING_UNSPECIFIED_AD responds as REVIEW: under review. If REVIEW is specified for approvalStatuses[] of MediaService/get and VideoService/get, PENDING_UNSPECIFIED_AD is also included in the search.

5. Maintenance

    • The download limit for the following two items has changed from 100,000 to 10,000 downloads.
      • FeedDataService/downloadErrorFile
      • FeedService/downloadDisApprovalReasonList
    • Setting a value to displayUrl in AdGroupAdService/add, set had caused an error. This has changed to ignore the setting and cause no error.
    • Changed the Enum value of the placementUrlListType of the AdGroupTargetService as follows. WHITE_LIST → STANDARD_LIST BLACK_LIST → EXCLUSIONS_ONLY_LIST
    • We will postpone the removal of unused report fields from the ReportDefinitionService. Wait for further announcements with detailed schedules.
    • Removed maxItems (maximum number) in some fields that specify Enum values. The fields we removed maxItems are as follows
      • Services Fields that removed maxItems
      AccountService
      • accountTypes
      • accountStatuses
      AccountLinkService
      • accountStatuses
      AccountManagementService
      • accountTypes
      • accountStatuses
      AdGroupService
      • userStatuses
      AdGroupAdService
      • approvalStatuses
      • adTypes
      • mainMediaFormats
      • userStatuses
      AdGroupTargetService
      • targetTypes
      • areaSearchTypes
      AppLinkService
      • appVendors
      AudienceListService
      • jobStatuses
      • audienceListTypes
      • audienceListSizeReaches
      AuditLogService
      • jobStatuses
      BaseAccountService
      • accountStatuses
      BrandLiftService
      • approvalStatuses
      CampaignService
      • userStatuses
      ConversionTrackerService
      • categories
      • conversionTrackerTypes
      • statuses
      DictionaryService
      • audienceListTypes
      FeedDataService
      • uploadStatuses
      GuaranteedAdGroupAdService
      • adTypes
      • mainMediaFormats
      MediaService
      • userStatuses
      ReportDefinitionService
      • reportJobStatuses
      StatsService
      • targetTypes
      VideoService
      • processStatuses
      • userStatuses
    • For features to be added in the near future, we made the following additions. You can use the features only after the release. We will make an announcement once details have been decided.
        • Added new service "CampaignBudgetService."
        • Added the followings to CampaignService.
          • budget/campaignBudgetId,
          • budget/campaignBudgetName
        • Add CAMPAIGN_BUDGET to reportType of ReportDefinitionService.
        • Added UTF8(with BOM)", 'EXCEL_CSV', etc. to the following services.
          • ReportDefinitionService/add
          • AuditLogService/add
          • FeedDataService/downloadErrorFile
        • Added the followings to RecommendationService/get.
          • Added MAXIMIZE_VIEWABLE_IMPRESSIONS to type
          • Added maximizeViewableImpressions to response

    Comments

    We will hold an online seminar to give an overview of API v16 along with the release. See the following announcement for details.
    Yahoo! JAPAN Ads API Webinar March 2025

    End of Display Ads API v14

    Display Ads API v14 will end with the following schedule:

    • Support end date: March 10, 2025
    • End of life date: End of July, 2025 (scheduled)
    *Wait for further announcements with detailed schedules.

    Display Ads API v13 will end with the following schedule:

    • End of life date: March 10, 2025
    *Support for this version has already ended.

Developer Center

Related sites: