Vungle ext.ifv and ext.idfv must contain the same IDFV.

What it means

Vungle ext.ifv and ext.idfv must contain the same IDFV. 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 an option offered by the matching request. Check the request and response together at the reported path.

Example that trips it

{
  "id": "vungle-request",
  "at": 1,
  "tmax": 300,
  "cur": [
    "USD"
  ],
  "source": {},
  "app": {
    "id": "publisher-app",
    "bundle": "123456789",
    "cat": [
      "IAB9"
    ],
    "publisher": {
      "id": "publisher"
    }
  },
  "device": {
    "ua": "Mozilla/5.0 (iPhone)",
    "ip": "203.0.113.2",
    "w": 1080,
    "h": 1920,
    "connectiontype": 2,
    "os": "iOS",
    "ext": {
      "ifv": "idfv",
      "idfv": "other",
      "atts": 2
    }
  },
  "imp": [
    {
      "id": "1",
      "displaymanager": "Vungle",
      "displaymanagerver": "7.4.1",
      "tagid": "placement",
      "bidfloor": 0,
      "bidfloorcur": "USD",
      "secure": 1,
      "clickbrowser": 0,
      "ext": {
        "pcta": 0
      },
      "banner": {
        "w": 320,
        "h": 50,
        "format": [
          {
            "w": 320,
            "h": 50
          }
        ],
        "id": "1",
        "mimes": [
          "text/html"
        ]
      }
    }
  ]
}

Profile vungle, OpenRTB 2.5. The fixture asserts openrtb.profile.vungle.idfv_mismatch at device.ext.idfv.

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.