Content.genre

A free-text genre that best describes the content, such as drama or rock. Added in OpenRTB 2.4.

CurrentstringOptionalSince 2.4

Field facts

Path
app.content.genre, dooh.content.genre, site.content.genre
Object
Content
Type
string
Requirement
Optional
Added
OpenRTB 2.4
Spec section
3.2.16

How it is used

Because the value is free text, sellers spell genres differently and buyers struggle to target on it. The structured pair Content.genres and Content.gtax was added in 2.6-202501 for that reason. Content.genre is not deprecated, and sellers can send both while partners migrate.

Example

Where the field sits in a payload, with everything else left out:

{
  "id": "req-1",
  "app": {
    "content": {
      "genre": "documentary"
    }
  }
}

Common mistakes

  • Packing several genres into one comma-separated string. Send the main genre here and the full set as IDs in Content.genres.

Version history

Added in OpenRTB 2.4, and present in the latest snapshot. The table shows how each version's spec text types the field.

VersionsType in the specRequiredDeprecated
2.4stringNoNo
2.5 to 2.6-202606stringNoNo

Related fields

Other Content fields

For a walkthrough of the whole object, read CTV and ad pods.