Unity accepts at most three decimal places in bid price.
Unity accepts at most three decimal places in bid price.
What it means
Unity accepts at most three decimal places in bid price. This check applies to the selected vendor contract and integration direction.
Why it matters
The declared profile checks the published partner contract alongside canonical OpenRTB. It does not verify runtime approval or account configuration.
How to fix it
Use the documented field type, value and representation at the reported path for this integration direction.
Example that trips it
{
"id": "unity-request",
"cur": "USD",
"seatbid": [
{
"seat": "buyer",
"bid": [
{
"id": "buyer-bid",
"impid": "1",
"price": 1.2345,
"adm": "<div>Creative</div>",
"cat": [
"IAB9"
],
"adomain": [
"advertiser.example"
],
"burl": "https://bidder.example/bill",
"w": 320,
"h": 50,
"ext": {
"crtype": "HTML"
}
}
]
}
]
}Profile unity, OpenRTB 2.6-202606. The fixture asserts openrtb.profile.unity.price_precision at seatbid[0].bid[0].price.
Check your payload
Paste a bid request or response into the tester to see whether this code fires against it, or gate on the id in CI with the CLI: the id is stable, wording is not.
Back to the full diagnostic code reference.