Yandex substitutes AUCTION_LOSS only in lurl and AUCTION_MIN_TO_WIN only in nurl or lurl.

What it means

Yandex substitutes AUCTION_LOSS only in lurl and AUCTION_MIN_TO_WIN only in nurl or lurl. 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 macro spelling and placement for this endpoint. Remove extra occurrences or unsupported contexts.

Example that trips it

{
  "id": "yandex-request",
  "cur": "USD",
  "seatbid": [
    {
      "bid": [
        {
          "id": "bid",
          "impid": "1",
          "price": 1,
          "ext": {
            "signaldata": "{\"cache_id\":\"opaque-ad\"}"
          },
          "nurl": "https://events.example/?loss=${AUCTION_LOSS}"
        }
      ]
    }
  ]
}

Profile yandex-sdk-bidding, OpenRTB 2.5. The fixture asserts openrtb.profile.yandex.macro_context at seatbid[0].bid[0].nurl.

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.