Native data asset types

Native data asset types name the text and number fields a native ad can fill, such as the sponsor name, description, rating, price or call-to-action text. AdCOM uses the list in its data asset objects, which makes it an OpenRTB 3.0 signal. OpenRTB 2.x uses the same values in the Native 1.2 request JSON inside imp.native.request, as assets[].data.type.

List: Native Data Asset Types13 values

Values

ValueNameWhat it means
1sponsoredThe sponsor's brand name, shown as the "sponsored by" label.
2descThe main descriptive text about the product or service.
3ratingA numeric rating of the product, such as an app store rating, usually from 0 to 5.
4likesA count of social likes or ratings for the product.
5downloadsA count of downloads or installs of the product.
6priceThe product or in-app purchase price, formatted for display with its currency symbol.
7salepriceA sale price shown next to the regular price to indicate a discount.
8phoneA formatted phone number.
9addressA formatted street address.
10desc2Additional descriptive text that accompanies the main description.
11displayurlA display URL, used when the sponsor does not own the content, as in "sponsored by Brand on Site".
12ctatextThe label on the call-to-action button, such as "Install" or "Shop now".
500+Vendor-specific codesVendor-specific data types agreed between the parties.

How to use it

Sellers list the data assets a layout can show and mark the ones it needs as required; buyers return values for the same asset IDs. Several types come with a recommended minimum length that sellers should support: at least 25 characters for sponsored, 140 for desc and 15 for ctatext. Send the length your template can actually show in len, and expect longer description text to be truncated. Prices should be formatted for display with a currency symbol, such as "$10". Values 500 and above are vendor-specific.

Common mistakes

  • Inventing values such as 13 for a new field. Use a 500+ code agreed with the buyer; rtblint reports unlisted values as openrtb.native.value.invalid.
  • Sending a raw number for price, such as 10, when the template expects display text like "$10".
  • Using desc2 (10) for the main description. It is for extra text alongside desc (2).

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.