SupplyChain.complete
Whether the chain reaches all the way back to the owner of the site, app, or other medium: 1 means every node is present, 0 means at least one upstream hop is missing. Required.
Field facts
- Path
source.schain.complete- Object
- SupplyChain
- Type
- integer
- Requirement
- Required
- Added
- OpenRTB 2.6-202204
- Spec section
- 3.2.25
How it is used
Set 1 only when the first node is the inventory owner's own seller account. If you received a chain marked 0, or no chain at all, the chain you forward stays incomplete after you append your node. Buyers often discount incomplete chains, and the No-Bid Reason Codes list has a value, 16, for declining a request on exactly this ground.
Allowed values
0, 1.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"source": {
"schain": {
"complete": 1
}
}
}Common mistakes
- Claiming 1 when an upstream partner sent no chain overstates what you know and fails buyer audits.
- Omitting the field: it is required, so strict parsers reject the whole object.
- Sending 0 by default on every request. The validator warns on incomplete chains because a missing hop should be rare.
Version history
Added in OpenRTB 2.6-202204, 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.6-202204 | Added in the first 2.6 release, published without a structured text archive; the 2.6-202210 republication is the first tagged text. | ||
| 2.6-202210 to 2.6-202606 | integer | Yes | No |
Related fields
Other SupplyChain fields
For a walkthrough of the whole object, read Supply chain (schain).