InMobi histories contain at most five entries; purchase and advertiser histories are omitted when empty.

What it means

InMobi histories contain at most five entries; purchase and advertiser histories are omitted when empty. 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

Keep the value within the published boundary described above. Check Unicode character counts where the contract counts characters.

Example that trips it

{
  "id": "depth-request",
  "imp": [
    {
      "id": "1",
      "tagid": "placement-1",
      "banner": {
        "w": 320,
        "h": 50
      }
    }
  ],
  "app": {
    "bundle": "com.publisher.game"
  },
  "device": {
    "ua": "Mozilla/5.0",
    "lmt": 0,
    "ip": "192.0.2.1",
    "ext": {
      "iap": []
    }
  }
}

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

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.