InMobi documents recent history first; its advertiser example conflicts with this ordering.

What it means

InMobi documents recent history first; its advertiser example conflicts with this ordering. 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": "source-boundary",
  "imp": [
    {
      "id": "1",
      "tagid": "placement",
      "banner": {
        "w": 320,
        "h": 50
      }
    }
  ],
  "app": {
    "bundle": "com.publisher.game"
  },
  "device": {
    "ua": "ua",
    "lmt": 0,
    "ip": "192.0.2.1",
    "ext": {
      "advertiserrelevancy": [
        {
          "lastbidtime": 100
        },
        {
          "lastbidtime": 200
        }
      ]
    }
  }
}

Profile inmobi, OpenRTB 2.6-202606. The fixture asserts openrtb.profile.inmobi.history_order at device.ext.advertiserrelevancy.

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.