Equativ prioritizes the mainline field when both mainline and legacy values are present.

What it means

Equativ prioritizes the mainline field when both mainline and legacy values are present. 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

Review the documented processing behavior or source ambiguity before changing the payload. Confirm account-dependent exceptions with the destination.

Example that trips it

{
  "id": "r",
  "imp": [
    {
      "id": "i",
      "tagid": "placement",
      "banner": {
        "w": 300,
        "h": 250
      }
    }
  ],
  "site": {
    "domain": "publisher.example",
    "page": "https://publisher.example/page",
    "publisher": {
      "id": "1234"
    }
  },
  "device": {
    "ip": "203.0.113.2"
  },
  "user": {
    "buyeruid": "matched-user"
  },
  "regs": {
    "ext": {
      "gdpr": 0
    },
    "gdpr": 0
  }
}

Profile equativ, OpenRTB 2.6-202606. The fixture asserts openrtb.profile.equativ.mainline_precedence at regs.ext.gdpr.

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.

• Primary protocol documentation
• Replayable source fixture

Back to the full diagnostic code reference.