Yahoo! JAPAN Ads API | Developer Center
日本語Display Ads API v14 Release Note
Version released
V14
Date
June 18, 2024
Changes on Yahoo! JAPAN Ads Display Ads API
More about objects and other details are described in the reference document.
1. New list type "Ad action users" for audience list targeting
We support the "Ad action users" which are users who took action on specific ads and are stored as an audience list. You can use this list for the ad delivery targeting.
*This feature is already available in the Campaign Management Tool. See the following announcement for details.
Audience list "Ad action users" will be available
Service
AudienceListService
AdGroupTargetService
Changes
- Added "Ad action users" to AudienceListType.
- Added "Ad action" to SourceType of AudienceListService.
- Changed reachPeriod of AudienceListService to dataDuration.
2. SKAdNetwork reports
You can check the values such as "Installs" measured by SKAdNetwork in the performance reports. Values are available only on a per-campaign basis.
*This feature is already available in the Campaign Management Tool. See the following announcement for details.
Add features to SKAdNetwork
Service
ReportDefinitionService
StatsService
Changes
- Added an "App report" with metrics related to SKAdNetwork to ReportDefinitionServiceReportType.
- Added the metrics related to the SKAdNetwork to the analytics value available in StatsService.
3. Optimize ad delivery using SKAdNetwork
We support the feature that optimizes ad delivery to maximize the installs based on SKAdNetwork.
*This feature is already available in the Campaign Management Tool. See the following announcement for details.
Add features to SKAdNetwork
Service
CampaignService
Changes
We added an item for setting to optimize ad delivery by SKAdNetwork to the add and modify campaign.
4. Add features to "Customer data" in the audience list
You can create an audience list that includes phone number data. We changed some of the formats of files to be imported into the audience list. You can't view upload status before 31 days.
*This feature is already available in the Campaign Management Tool. See the following announcement for details.
Adding features to "Customer data" in the audience list
Service
AudienceListService
Changes
- We support the upload of phone numbers in the audience list. The following name has been changed:
MAIL_ADDRESS to MAIL_ADDRESS_AND_PHONE_NUMBER - Removed the retargetingTagId field from the UploadUserListJob of the AudienceListService.
- Removed the targetingTagId from the upload parameters.
- Changed the upload status available with getUploadUserListStatus to the last 30 days.
5. End of audience category analytics
Along with the end of the "Audience category targeting," we no longer offer audience category analytics. We also removed items that are no longer available.
Service
StatsService
Changes
Removed AUDIENCE_CATEGORY from StatsServiceTargetType.
6. Remove app measurement vendor "METAPS"
We removed app measurement vendors that are not available in Display Ads.
Service
AppLinkService
AudienceListService
Changes
Removed "METAPS" from the AppVendor (app measurement vendor) Enum value.
7. Yahoo! JAPAN Tag Manager (V11 and V12)
Yahoo! JAPAN Tag Manager will end, and the following features of v11 and v12 will no longer be available after July 1, 2024.
There is no change after v13 because the relevant items have already been removed.
Service
AudienceListService（uploadUserList）
Changes
- The uploadType "CUSTOM_UID_KEY" will not be available.
- CustomEntityId will not be available.
8. Maintenance
Added a field "containDataConnectionStopped" to the AudienceListService to indicate whether the combination and similar lists contain lists that have stopped data connection.
Comments
There are no online seminars for this release.
End of Display Ads API v12
Display Ads API v12 will end with the following schedule:
Support end date: June 12, 2024
End of life date: End of October, 2024 (scheduled)
*Wait for further announcements with detailed schedules.
Display Ads API v11 will end with the following schedule:
End of life date: July 2, 2024
*Support for this version has already ended.