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

# Responsive Display Ads

How Native campaign assets render in Banner, Interstitial and Instant Message zones, and how to enable it.

Responsive Display Ads (RDA) are a combination of visual and textual elements that can be used as an alternative to standard banner ads. They automatically adjust their size, appearance, and format to fit the allocated space.

Responsive Display Ad templates are created and maintained by EXADS. Networks cannot create or modify them, and Advertisers use the templates made available to their network.

By default, this feature is turned off. Network Admin Users can contact their EXADS representative to enable Responsive Display Ads for the network.

<figure><img src="https://4095468742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQpBCwTiJQ0YOSGpcC0AH%2Fuploads%2FtcgoZvelAZKWLwSZBCqS%2FRDA-ad.png?alt=media&amp;token=53172ab5-b2a8-4e1c-ba7c-58aa3ef9c3da" alt="The same Native assets rendered as 160x600, 300x250, 300x100 and 728x90 ads"><figcaption></figcaption></figure>

## How Responsive Display Ads Work <a href="#how-responsive-display-a-ds-work" id="how-responsive-display-a-ds-work"></a>

Responsive Display Ads allow Native campaign assets to dynamically render within compatible Banner, Interstitial and Instant Message zones.

A layout is a template that arranges the Native assets within a zone. The same campaign can render as a single image in one layout and as a grid of items in another. Each zone type and size has one or more layouts available, and the Ad Server chooses which to use.

## Advertisers <a href="#a-dvertisers" id="a-dvertisers"></a>

When you create a **Native Ad** campaign, Step 1 has a **Responsive Display Ad Zones** checkbox. It is enabled by default.

<figure><img src="https://4095468742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQpBCwTiJQ0YOSGpcC0AH%2Fuploads%2FG8irEpyYPEpJH5t7hP2B%2FRDA_enable_Advertiser.png?alt=media&amp;token=a9de6912-0c5a-470d-8acb-d672473a3bf6" alt="The Responsive Display Ad Zones checkbox in Step 1 of campaign setup"><figcaption></figcaption></figure>

Responsive Display Ads are available on the following zone types and sizes:

<table data-search="false"><thead><tr><th>Zone Type</th><th>Sizes</th></tr></thead><tbody><tr><td>Banner</td><td>160x600, 300x250, 300x500, 728x90, 900x250</td></tr><tr><td>Sticky Banner</td><td>160x600, 300x250, 728x90, 900x250</td></tr><tr><td>Mobile Banner</td><td>300x50, 300x100, 300x250</td></tr><tr><td>Instant Message</td><td>300x250</td></tr><tr><td>Mobile Instant Message</td><td>300x100</td></tr><tr><td>Desktop Fullpage Interstitial</td><td>1600x900</td></tr><tr><td>Mobile Fullpage Interstitial</td><td>900x1600</td></tr></tbody></table>

The Ad Server uses your Native campaign assets and adapts them to fit these formats. Not all assets appear in every impression.

## Publishers <a href="#publishers" id="publishers"></a>

The Responsive Display Ads setting appears in the Admin Panel when you create or edit:

* Banner and Mobile Banner zones
* Sticky Banner zones
* Desktop Fullpage Interstitial and Mobile Fullpage Interstitial zones
* Instant Message and Mobile Instant Message zones

Enabling this setting:

* Adds Native campaigns to the bidding auction for that zone
* Enables dynamic rendering within the allocated space

This setting makes the zone eligible for Responsive Display Ads. It does not control which layout or which assets are displayed.

### How to Enable

1. In the Admin Panel, click **New Zone**, or edit an existing zone.
2. Select **Banner**, **Mobile Banner**, **Sticky Banner**, **Desktop Fullpage Interstitial**, **Mobile Fullpage Interstitial**, **Instant Message** or **Mobile Instant Message**.
3. Turn on the **Responsive Display Ads** switch.

<figure><img src="https://4095468742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQpBCwTiJQ0YOSGpcC0AH%2Fuploads%2FEiemqX2aoMrd2rL3OVMT%2FBannerRDA.png?alt=media&amp;token=d6b13a20-b325-48cc-907f-d100f83a0ed2" alt="The Responsive Display Ads switch in the zone settings"><figcaption></figcaption></figure>

This setting is enabled by default for every zone that supports Responsive Display Ads. You can disable it at any time.

## Optimization and Delivery <a href="#optimization--delivery" id="optimization--delivery"></a>

Responsive Display Ads use optimization to determine which eligible campaign and layout to display. The Ad Server considers:

* Campaign competitiveness
* Historical performance
* User engagement signals

A small portion of traffic is used to evaluate alternative variations, so that new or lower-volume campaigns can gather performance data and remain competitive.

The rendering logic is built and maintained by EXADS to ensure technical compatibility and consistent quality.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.exads.com/general/general-responsive-display-ads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.