> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/ads/creative-specification/programmatic-audio.md).

# Programmatic Audio

#### **General Information - Delivery of Audio Advertising**

Due to technical checks, the audio ad should be delivered to the ad management team at least 2 working days prior to the start of the campaign.

If there is an agreed upon campaign plan, the audio files can delivered up to 1 day prior to the campaign start. In these cases, the ad management team will prepare everything accordingly.

#### **Technical Requirements for Audio Advertising Formats**

<table data-header-hidden><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td>File Type</td><td>MP3 AND OGG </td><td>Mandatory</td></tr><tr><td>File Bit Rate</td><td>192 - 196 kbps</td><td>Mandatory</td></tr><tr><td rowspan="2">File Duration</td><td>5, 15 or 30 seconds</td><td rowspan="2">Optional</td></tr><tr><td>60 is limited, as it cannot be delivered with all SSPs/Inventory</td></tr><tr><td>Audio Trimming</td><td>Trimmed of slate/silence</td><td>Audio trimming is the process of removing unnecessary or unwanted parts from an audio file. This can be done for many reasons such as reducing the size of the file, removing unwanted sections, removing background noise, etc.</td></tr><tr><td>File Size</td><td>Max. 2 MB</td><td>Mandatory</td></tr><tr><td>Spotify Delivery </td><td>Companion Ad 600x600px (JPEG, PNG)<br>File Size 200KB Max.<br>Click through URL<br><br>Spotify specs - know the technical requirements: <a href="https://ads.spotify.com/en-GB/ad-specs/audio-ad-specs/">https://ads.spotify.com/en-GB/ad-specs/audio-ad-specs/</a><br></td><td>Mandatory</td></tr></tbody></table>

#### **File Delivery Options**

1. Physical audio file based on the Sportradar technical requirements.
2. 3rd party Adserving Audio VAST based on the Sportradar technical requirements. When using 3rd party VAST there may **be tracking deviations!** Deviations up until 10% will not be investigated due to industry standards.&#x20;

&#x20;

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportradar.com/ads/creative-specification/programmatic-audio.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.