Magnite xAPI requires HTTPS impression trackers when the referenced impression is secure.

What it means

Magnite xAPI requires HTTPS impression trackers when the referenced impression is secure. 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

Request:
{
  "id": "request-1",
  "imp": [
    {
      "id": "imp-1",
      "banner": {
        "w": 300,
        "h": 250
      },
      "secure": 1
    }
  ]
}

Response:
{
  "id": "request-1",
  "seatbid": [
    {
      "seat": "buyer-code",
      "bid": [
        {
          "id": "bid-1",
          "impid": "imp-1",
          "price": 1.5,
          "ext": {
            "rp": {
              "imptrackers": [
                "//tracker.example/i"
              ]
            }
          }
        }
      ]
    }
  ]
}

Profile magnite, OpenRTB 2.6-202606. The fixture asserts openrtb.profile.magnite.insecure_tracker at seatbid[0].bid[0].ext.rp.imptrackers[0].

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.