Creative subtypes for display
Display creative subtypes say what form a display ad takes: general HTML markup, AMPHTML, a structured image, or a structured native object. The list is used only by AdCOM, in the Display object's ctype (what an ad is) and the display placement's ctype array (what a placement accepts), which makes it an OpenRTB 3.0 signal. OpenRTB 2.x signals the format through the Imp sub-object offered and Bid.mtype.
Values
| Value | Name | What it means |
|---|---|---|
1 | HTML | General HTML markup, sent inline or fetched by URL. |
2 | AMPHTML | AMPHTML markup, the Accelerated Mobile Pages variant of HTML for ads. |
3 | Structured Image Object | A structured image creative described by AdCOM's banner object rather than by markup. |
4 | Structured Native Object | A structured native creative described by AdCOM's native object and its assets. |
How to use it
Values 3 and 4 correspond to the structured banner and native objects inside the AdCOM Display object, which AdCOM prefers over raw markup because the exchange can inspect them. Values 1 and 2 cover markup carried in adm or fetched by URL through curl. A placement that accepts AMPHTML can also say how it renders AMP ads with its ampren field. There is no vendor range in this list.
Common mistakes
- Confusing this list with the audio and video creative subtypes, which describe VAST and DAAST versions, not display formats.
- Declaring 4 for a native ad delivered as HTML markup. That is 1; 4 means the structured native object.
Validation
On OpenRTB 2.6 snapshots, RTBlint reports a value outside this list as openrtb.value.invalid. Paste a request into the tester to check the values you send.
Related lists
- Display context types
- Display placement types
- Native data asset types
- Native image asset types
- Event types
- Event tracking methods
- Click types
- Audit status codes
- Size units
All lists are on the enumerated lists index.