App.domain
A domain associated with the app, such as the app's own website. It is descriptive and does not decide where app-ads.txt is read.
Field facts
- Path
app.domain- Object
- App
- Type
- string
- Requirement
- Optional
- Added
- OpenRTB 2.0
- Spec section
- 3.2.14
How it is used
app-ads.txt crawlers find the developer website through the store listing, not through this field, so a correct App.domain proves nothing about authorization. It is still useful in reporting and for matching apps against lists keyed on domains.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"app": {
"domain": "puzzlequest.example.com"
}
}Common mistakes
- Treating
App.domainas the place to look for app-ads.txt. The developer URL on the store listing decides that. - Sending a full URL with scheme and path instead of a bare domain.
Version history
Added in OpenRTB 2.0, and present in the latest snapshot. The table shows how each version's spec text types the field.
| Versions | Type in the spec | Required | Deprecated |
|---|---|---|---|
| 2.0 to 2.2 | string | No | No |
| 2.3 to 2.3.1 | string | No | No |
| 2.4 | string | No | No |
| 2.5 to 2.6-202606 | string | No | No |