Volume normalization modes

Volume Normalization Modes says whether, and how, an audio platform adjusts the level of ads to match the content around them. Sellers send it in Audio.nvol, so buyers know whether their creative will play at the level it was mixed or be adjusted by the publisher.

List: Volume Normalization Modes5 valuesUsed by imp.audio.nvol

Values

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

Fields that use this list

How to use it

The field and its five values arrived with the Audio object in OpenRTB 2.4 and have not changed since. A jump in loudness between content and ad is one of the most common listener complaints in audio, and buyers that cannot control every mix may prefer normalized inventory. Value 3 is the only one that matches perceived loudness rather than a signal level.

Common mistakes

  • Sending 0 when the stream is normalized by a downstream player the seller does not control. If the seller does not know, leave the field out.
  • Sending 4 without telling buyers what the custom method is. The value is only useful with documentation behind it.

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.