Site.page
The full URL of the page where the impression will appear, including scheme and path. It is the most specific location signal a web request carries.
Field facts
- Path
site.page- Object
- Site
- Type
- string
- Requirement
- Optional
- Added
- OpenRTB 2.0
- Spec section
- 3.2.13
How it is used
Buyers use the page URL for contextual classification, brand safety crawling, and page-level blocking. It should be the top-level page the user sees, not the URL of an iframe or ad server. Strip personal data from query strings before sending; some sellers trim the URL to its path for that reason.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"site": {
"page": "https://news.example.com/local/2026/11/07/transit-vote"
}
}Common mistakes
- Swapping the fields: a bare hostname in page and the full URL in
Site.domain. The validator warns on the domain. - Sending the ad server's iframe URL instead of the top page, which makes every impression look like it came from one page.
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 | string | Recommended | No |
| 2.1 | string be | Recommended | No |
| 2.2 | string | Recommended | No |
| 2.3 to 2.3.1 | string | No | No |
| 2.4 | string | No | No |
| 2.5 | string | No | No |
| 2.6-202210 to 2.6-202303 | srting | No | No |
| 2.6-202309 to 2.6-202606 | string | No | No |