MobileFuse expects Native Ads 1.2.

What it means

MobileFuse expects Native Ads 1.2. 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",
      "native": {
        "ver": "1.1",
        "request": "{\"ver\": \"1.1\", \"assets\": [{\"id\": 1, \"title\": {\"len\": 25}}]}"
      }
    }
  ],
  "app": {
    "bundle": "com.publisher.game"
  },
  "device": {
    "ua": "ua",
    "lmt": 0,
    "ip": "192.0.2.1"
  }
}

Profile mobilefuse, OpenRTB 2.6-202606. The fixture asserts openrtb.profile.mobilefuse.native_version at imp[0].native.ver.

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.