Audio.nvol

The volume normalization applied to ads, from AdCOM List: Volume Normalization Modes: 0 none, 1 average volume normalized to content, 2 peak volume normalized to content, 3 loudness normalized to content, 4 custom.

CurrentintegerOptionalSince 2.4

Field facts

Path: imp.audio.nvol
Object: Audio
Type: integer
Requirement: Optional
Added: OpenRTB 2.4
Values: AdCOM list Volume Normalization Modes
Spec section: 3.2.8

How it is used

Ads much louder than the program are a frequent listener complaint. When the value is 0, the creative's own mastering decides how loud it plays, so buyers should supply loudness-normalized files.

Allowed values

Value	Meaning
`0`	None: No normalization: the ad plays at whatever level it was delivered.
`1`	Ad Volume Average Normalized to Content: The ad's average volume is adjusted to match the content's average volume.
`2`	Ad Volume Peak Normalized to Content: The ad's peak volume is adjusted to match the content's peak volume.
`3`	Ad Loudness Normalized to Content: The ad's loudness, a perceptual measure rather than a raw signal level, is matched to the content.
`4`	Custom Volume Normalization: The platform applies its own normalization method; ask the seller how it works.

Example

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

{
  "id": "req-1",
  "imp": [
    {
      "audio": {
        "nvol": 3
      }
    }
  ]
}

Common mistakes

Sending 0 by default when the platform does normalize, which tells buyers their files will play unadjusted when they will not.

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.

Versions	Type in the spec	Required	Deprecated
2.4	integer	No	No
2.5	integer	No	No
2.6-202210 to 2.6-202606	integer	No	No

Related fields

Other Audio fields

For a walkthrough of the whole object, read Audio object guide.