openrtb.2.4.imp.secure.ssl

What it means

OpenRTB 2.4 introduced imp.secure, which openRTB 2.4 broadened SSL and secure-asset expectations for creatives..

Why it matters

imp.secure is only defined from 2.4 onward. Used against an earlier version it is not valid, and a consumer below 2.4 treats it as an unknown field.

How to fix it

Target OpenRTB 2.4 or later when you send imp.secure, and make sure the value matches the type and any enum the specification defines for it.

Paste your bid request into the tester and select OpenRTB 2.4 to see whether this rule fires against your payload.

Reference

• Specification section: Release highlights
• Source: IAB Tech Lab OpenRTB standards page

Back to the full rule catalog.