Click types

Click types describe whether a placement can be clicked and, if so, where the landing page opens: in an embedded browser or webview, or in the device's native browser. The list is used only by AdCOM placement objects (clktype on display and video placements) in OpenRTB 3.0. OpenRTB 2.x carries a narrower version of the idea in Imp.clickbrowser.

List: Click Types5 values

Values

Value	Name	What it means
`0`	Non-Clickable	The placement cannot be clicked, as on most DOOH screens and many CTV apps.
`1`	Clickable, details unknown	The placement can be clicked, but where the landing page opens is not known; the AdCOM default for display placements.
`2`	Clickable, embedded browser or webview	Clicks open the landing page in a browser view inside the app.
`3`	Clickable, native browser	Clicks hand the user to the device's own browser, outside the app.
`500+`	Vendor-specific codes	Vendor-specific click behaviors agreed between the parties.

How to use it

In AdCOM the display placement's clktype defaults to 1, so a placement that cannot be clicked at all, such as a DOOH screen or many CTV apps, should say 0 explicitly. Buyers use the value to decide whether click-through creatives and landing pages make sense, and app buyers care whether the landing page opens inside the app or hands the user to the system browser. In OpenRTB 2.x, Imp.clickbrowser answers only the second question, using 0 for embedded and 1 for native.

Common mistakes

Copying Imp.clickbrowser values straight into clktype. In 2.x, 0 means embedded browser; in this list, 0 means the placement cannot be clicked. Embedded maps to 2 and native maps to 3.
Leaving clktype at its default of 1 on a screen that has no way to click.

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

All lists are on the enumerated lists index.