> For the complete documentation index, see [llms.txt](https://dmtp.gitbook.io/dmtp-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dmtp.gitbook.io/dmtp-sdk/06-web3-traffic-exchange-banner-types-placements.md).

# 6. Banner Types and Placements

**Apps Network** supports special banner types and placements to accommodate different website layouts and advertising needs. This section outlines the current options and future plans for ad formats.

## Standard Banners

Currently, the primary ad format supported is the standard banner:

* Size: from 64x64 to 512x512 pixels
* Render: Banner + Campaign description + Play button

When creating your offer wall or designing your ad campaigns (tasks), keep in mind how the ad is rendered.

## Offer Walls

**Apps Network** mainly supports Offer Walls:

* Type: Full-page interstitial
* Features: Can display a single large banner or a list of multiple ad campaigns
* Usage: Ideal for transitional moments in user experience, such as between content pages or app levels


---

# 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://dmtp.gitbook.io/dmtp-sdk/06-web3-traffic-exchange-banner-types-placements.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.