The response SKAdNetwork must match a requested skadnetids entry.
The response SKAdNetwork must match a requested skadnetids entry.
What it means
The response SKAdNetwork must match a requested skadnetids entry. 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
Request:
{
"id": "depth-request",
"imp": [
{
"id": "1",
"tagid": "placement-1",
"banner": {
"w": 320,
"h": 50
},
"ext": {
"skadn": {
"versions": [
"4.0"
],
"sourceapp": "987654321",
"skadnetids": [
"example.skadnetwork"
]
}
}
}
],
"app": {
"bundle": "987654321"
},
"device": {
"ua": "Mozilla/5.0",
"lmt": 0,
"ip": "192.0.2.1"
}
}
Response:
{
"id": "depth-request",
"seatbid": [
{
"seat": "buyer-1",
"bid": [
{
"id": "bid-1",
"impid": "1",
"price": 1.2,
"burl": "https://buyer.example/bill",
"cat": [
"IAB1"
],
"crid": "creative-1",
"adomain": [
"advertiser.example"
],
"adm": "<div>banner</div>",
"w": 320,
"h": 50,
"mtype": 1,
"ext": {
"skadn": {
"version": "4.0",
"network": "other.skadnetwork",
"sourceidentifier": "1234",
"itunesitem": "123456789",
"sourceapp": "987654321",
"fidelities": [
{
"fidelity": 0,
"nonce": "00000000-0000-0000-0000-000000000000",
"timestamp": "1775407039",
"signature": "signature-token"
}
]
}
}
}
]
}
]
}Profile inmobi, OpenRTB 2.6-202606. The fixture asserts openrtb.profile.inmobi.skadnetwork_unoffered at seatbid[0].bid[0].ext.skadn.network.
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.