ADJUST_DEAL_MARGIN has no OpenRTB field to write to
Margin is not part of the OpenRTB Deal object, so the orchestrator has to apply it out of band and no validator can check the result.
What it means
The mutation declares ADJUST_DEAL_MARGIN. The ARTF payload for it is well defined, but OpenRTB 2.6's Deal object has no margin field, so there is nowhere in the auction for the value to land.
Why it matters
This is a gap between the two specifications rather than a defect in the payload. It matters because the rest of a mutation set can be verified end to end, and this one cannot: whatever the orchestrator does with the margin happens in its own systems, invisible to anything that inspects the resulting bid request.
How to fix it
Nothing to fix in the mutation. Expect the value to be applied out of band, and do not rely on reading it back from the auction.
Example that trips it
{ "intent": "ADJUST_DEAL_MARGIN", "op": "OPERATION_REPLACE", "path": "/imp/imp-1/pmp/deals/deal-premium", "adjust_deal": { "margin": { "value": 12.0, "calculation_type": "PERCENT" } } }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.