> 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-native.md).

# Programmatic Native

All creative must meet the standards mentioned below, for campaigns to run. It is essential that creative are compliant not only to be allowed to serve on our systems but also to ensure that creative can serve on the widest pool of inventory.

Our Audit Team evaluates creative against the standards below. As initial requirements, a single creative must render properly multiple times during the audit process. Therefore, frequency capping or geo-targeting set outside the system will interfere with the audit process. We must receive the creative 72 hours prior to campaign start to ensure that creative can be audited in time to serve for any campaign.

Please send the creatives at least three days before the campaign starts to your account manager.

Sportradar recommends on the next pages creative guidelines for native display advertising.

#### Technical Specifications <a href="#technical-specifications" id="technical-specifications"></a>

| General       | <ul><li>If a creative’s background image utilizes a photo, pattern etc. it should be simple, non-distracting, and understated.</li></ul><p><br></p><ul><li>Creative should have a clearly visible non-white 1-pixel border or a dark or high contrast background color that distinguishes it from a site’s content.</li></ul><p><br></p><ul><li>Animation (e.g. animated GIF files) are not allowed and not recommended.</li></ul> |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Actions       | <ul><li>Strobing, flashing backgrounds, or otherwise distracting ads are not allowed.</li></ul>                                                                                                                                                                                                                                                                                                                                    |
| Landing pages | <ul><li>Landing pages may not navigate away from the advertiser’s page.<br><br></li><li>The landing page must match the language, brand, or offer of the creative description.</li></ul>                                                                                                                                                                                                                                           |

### Creative Specifications - STANDARD ASSETS REQUIRED <a href="#creative-specifications-standard-assets-required" id="creative-specifications-standard-assets-required"></a>

| Max File Size             | Up to 250 KB                                                                                                                                                                                                                                          |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Image Asset/Main Image    | <ul><li>Supported formats: JPG, PNG</li><li>Recommended sizes: 1200x628px,600x600px, 344x180px, 600x315px, 300x300px, 1200x1200px, 310x310px, 400x400px, 1080x1080px</li><li>Image should be free of text</li><li>Aspect ratio: 1:1 or 4:3 </li></ul> |
| Logo/Icon (not mandatory) | <ul><li>Format: JPG, PNG</li><li>Recommended sizes: 300x300px, 80x80px, 50x50px, 48x48px, 32x32px</li><li>Max height: 300px</li><li>Min height: 48px</li><li>Ratio: 1:1</li></ul>                                                                     |
| Text                      | <ul><li>Headline/Sponsored by: 90 Characters and should contain the name of the sponsor / to stand on its own</li></ul><p><br></p><ul><li>Native Description: 200 Character Limit</li></ul><p><br></p>                                                |
| Click URL / Landing page  | <p>Clickthrough URL</p><p><br></p>                                                                                                                                                                                                                    |

<br>


---

# 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-native.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.