Native response asset id was not in the request

What it means

Response asset ids must be drawn from the request's asset ids. An extra id is not a bonus slot; it is an unsolicited asset.

Why it matters

The renderer only has placeholders for requested ids. An unknown id is ignored or treated as a malformed native response.

How to fix it

Use only ids from the request. Extra creative parts belong on an existing asset (for example a link on that asset), not a new id.

Example that trips it

{ "request": { "native": { "request": "{\"assets\":[{\"id\":1,\"title\":{\"len\":90}}]}" } }, "adm": "{\"link\":{\"url\":\"https://ex\"},\"assets\":[{\"id\":9,\"title\":{\"text\":\"Hi\"}}]}" }

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.

• Native ads reference

Back to the full diagnostic code reference.