A Google bid must select ext.billing_id when its impression offers multiple billing IDs.

What it means

A Google bid must select ext.billing_id when its impression offers multiple billing IDs. 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

Supply the missing information through the documented field or permitted alternative for this direction.

Example that trips it

Request:
{
  "id": "req-depth",
  "imp": [
    {
      "id": "1",
      "banner": {
        "w": 300,
        "h": 250
      },
      "ext": {
        "billing_id": [
          "123",
          "124"
        ]
      }
    }
  ]
}

Response:
{
  "id": "req-depth",
  "seatbid": [
    {
      "bid": [
        {
          "id": "bid-1",
          "impid": "1",
          "price": 1,
          "adomain": [
            "test.invalid"
          ]
        }
      ]
    }
  ]
}

Profile google-ab, OpenRTB 2.6-202606. The fixture asserts openrtb.profile.google.billing_id_required at seatbid[0].bid[0].ext.billing_id.

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.