Vungle SKAdNetwork campaign must be an integer string in the version-specific range (1 through 100 before 4.0, 0 through 9999 in 4.0 and later).
Vungle SKAdNetwork campaign must be an integer string in the version-specific range (1 through 100 before 4.0, 0 through 9999 in 4.0 and later).
What it means
Vungle SKAdNetwork campaign must be an integer string in the version-specific range (1 through 100 before 4.0, 0 through 9999 in 4.0 and later). 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 the documented field type, value and representation at the reported path for this integration direction.
Example that trips it
{
"id": "vungle-request",
"seatbid": [
{
"bid": [
{
"id": "buyer-bid",
"impid": "1",
"price": 1,
"adm": "<div>Creative</div>",
"adomain": [
"advertiser.example"
],
"ext": {
"skadn": {
"version": "3.0",
"itunesitem": "987654321",
"sourceapp": "123456789",
"network": "network.skadnetwork",
"campaign": "101",
"fidelities": [
{
"fidelity": 1,
"nonce": "44f6469a-5be4-4679-abb8-03af9b497b12",
"timestamp": "1648110176239",
"signature": "illustrative-signature"
}
]
}
},
"bundle": "987654321"
}
]
}
]
}Profile vungle, OpenRTB 2.5. The fixture asserts openrtb.profile.vungle.skadn_campaign at seatbid[0].bid[0].ext.skadn.campaign.
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.
Back to the full diagnostic code reference.