Use * syntax for faster search
Page History
...
How am I affected? On May 7, 2025, users will begin seeing a new read only field for the following creative endpoints affecting GET, POST, PUT, and PATCH PATCH responses:
- /creatives
- /creatives/{id}
...
What is it? On March 11th, 2025, the platform will add support for app-ads.txt into the existing ads.txt targeting key. This change will result in the deprecation of some of the targeting values for this key, which will occur on June 10th, 2025, 90 days after the release of the new values. This update aims to make ads.txt and app-ads.txt targeting more efficient and streamlined. 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? As of March 11th, 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 June 10th, 2025. The impacted endpoints are listed below:
...