2025
Ads.txt Targeting Key Update
What is it? On March 11th, Beeswax will add support for app-ads.txt into our 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, 90 days after the release of the new values. With this we aim to make ads.txt and app-ads.txt targeting more efficient and streamlined to use. 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? The impacted endpoints are:
- /ref/ads-txt
- /targeting-expressions
- /targeting-expressions/{id}
As of March 11th, you will be able to start making this migration to the new targeting values. Any existing calls using the deprecated targeting values after this date will be translated to the new targeting values to ease in the transition as you work to make adjustments to your API calls. We will continue this translation up until the deprecation date of June 10th.
Resource(s): List of Targeting Modules and Keys