AppLovin SKAdNetwork nonce must use UUID format.
AppLovin SKAdNetwork nonce must use UUID format.
What it means
AppLovin SKAdNetwork nonce must use UUID format. 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": "request-1",
"seatbid": [
{
"bid": [
{
"id": "bid-1",
"impid": "1",
"price": 1.5,
"adm": "<div>Ad</div>",
"adomain": [
"advertiser.example"
],
"burl": "https://bidder.example/bill?p=${AUCTION_PRICE}",
"cat": [
"IAB9"
],
"crid": "creative-1",
"bundle": "987654321",
"ext": {
"crtype": "HTML",
"clicktrackers": [
"https://click.example"
],
"skadn": {
"version": "3.0",
"network": "example.skadnetwork",
"campaign": "100",
"itunesitem": "987654321",
"sourceapp": "123456789",
"fidelities": [
{
"fidelity": 1,
"nonce": "not-uuid",
"signature": "signed-value",
"timestamp": "1700000000000"
}
]
}
}
}
]
}
]
}Profile applovin-alx, OpenRTB 2.6-202606. The fixture asserts openrtb.profile.applovin.skadn_nonce at seatbid[0].bid[0].ext.skadn.fidelities[0].nonce.
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.