The OpenRTB Native Asset Cheat Sheet Every PMP Bid Ops Engineer Needs

On November 9, 2026, AdMesh released an OpenRTB 2.6 adapter capable of handling Native 1.2 format, allowing DSPs to backfill conversational inventory without a customized integration. The communication remains consistent with the JSON string in imp.native.request and the native markup object (or another encoded string) in bid.adm when the media type (mtype) is 4.

Native routing does not alter asset matching. An incomplete response, even with correct field types, will result in the bid being discarded. This cheat sheet provides a mapping between publisher requests and required responses for native PMP and in-app deals, ensuring adherence to the native contract. It is intended for bid ops engineers who encounter native line items, Prebid ortb2Imp, or forwarded imp.native blobs.

The focus is on identifying non-negotiable IDs and subtypes before creative studios build markup. To validate native requests and responses, utilize the RTBlint tool, which checks both the request and response payloads, ensuring pairing of asset IDs, subtypes, and tracker methods. This validation process is independent of IAB Tech Lab and AgenticAdvertising.org but is recommended for ensuring the integrity of native ad delivery.