Use * syntax for faster search
Page History
| Tip | ||||
|---|---|---|---|---|
| ||||
To view this changelog as an RSS feed, add the following URL [source link] to an RSS reader. |
May 12, 2025
Release Update to Ads.txt Targeting Key
What is it? The release of the API targeting key changes to support app-ads.txt, originally announced on February 10th, 2025, will go live on May 13th, 2025. This change will result in the deprecation of some of the targeting values for this key, which will occur on August 12th, 2025. The updates to the targeting values are listed below:
| Old Targeting Label | Old Targeting Value | New Targeting Label | New Targeting Value |
|---|---|---|---|
| No Domain | 0 | Unknown | 9 |
| No Ads.txt File | 1 | Unauthorized | 8 |
| Ads.txt File Not Scanned | 2 | Unauthorized | 8 |
| No Advertising Allowed | 3 | Unauthorized | 8 |
| Missing Publisher ID | 4 | Unknown | 9 |
| Not Authorized | 5 | Unauthorized | 8 |
| Authorized - Reseller | 6 | No Change | No Change |
| Authorized - Direct | 7 | No Change | No Change |
How am I affected? On May 13th, 2025, the migration to the new targeting values can begin. Any existing calls using the deprecated targeting values after this date will be translated to the new targeting values to ease the transition while adjustments are made to the API calls. This translation will continue until the deprecation date of August 12th, 2025. The impacted endpoints are listed below:
- /ref/ads-txt
- /targeting-expressions
- /targeting-expressions/{id}
Resource(s): List of Targeting Modules and Keys
May 5, 2025
New Field on Creative Vendor Fees
What is it? A new field called vendor_fees/read_only will start being returned in API responses for some creatives endpoints. This new field will help API users know if a vendor fee is read only or editable.
How am I affected? On May 77th, 2025, users will begin seeing a new read only field for the following creative endpoints affecting GET, POST, PUT, and PATCH responses:
...
What is it? The upcoming changes to the ads.txt API targeting key have been shifted, and a new release and deprecation date will be shared soon. As a reminder, the new targeting keys will align with the release of app-ads.txt. For more details, refer to the "Ads.txt Targeting Key Update" from February 1010th.
How am I affected? A new release date will be shared soon. In the meantime, please continue using the current targeting values for your API calls.
...
How am I affected? On March 3131st, 2025, a fix will be implemented that will no longer reset bidding.pacing_behavior, bidding.multiplier, and bidding.catchup_behavior when a PATCH call is made to update bidding.pacing, bidding.custom, or bidding.bid_shading_control. Any change to bidding.strategy will continue to reset bidding.pacing_behavior, bidding.multiplier, and bidding.catchup_behavior back to their default values. The affected endpoints are listed below:
...
How am I affected? On March 3131st, 2025, a fix will be implemented that will prevent using the PATCH method to update active advertisers if they don't have a declared advertiser category or advertiser domain. The affected endpoints are listed below:
...
What is it? The release of the API targeting key changes originally announced on February 1010th, 2025 is being temporarily delayed. The new release date and deprecation date are provided below. For more details, users can refer to the "Ads.txt Targeting Key Update" from February 10.
How am I affected?
- New release date: April 88th, 2025
- New deprecation date: July 88th, 2025
Resource(s): List of Targeting Modules and Keys
...