> For the complete documentation index, see [llms.txt](https://adagio-io.gitbook.io/adagio-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://adagio-io.gitbook.io/adagio-documentation/openrtb-s2s-endpoint/review-your-technical-integration/tagid-limits-and-guidelines.md).

# TagID Limits and Guidelines

This section explains the limits applied to tagIDs and why they exist. These rules are designed to ensure optimal performance, accurate learning, and effective monetization. Staying within these limit

### Summary of limits and best practices

| Rule                     | Limit / Threshold                                | What happens if exceeded?                  |
| ------------------------ | ------------------------------------------------ | ------------------------------------------ |
| Maximum number of tagIDs | 100 per site or app (total, across all requests) | Extra tagIDs are ignored and not monetized |
| Maximum tagID length     | 150 characters                                   | TagID may be rejected or ignored           |
| Low-traffic tagIDs       | Fewer than 150 adcalls per day                   | No meaningful value                        |

#### **Why it matters?**

Too many tagIDs slow down learning and optimization and low-volume tagIDs reduce overall performance.

#### **TagID Naming Suggestions:**

* Banner
  * `banner_top`
  * `banner_middle`
  * `banner_bottom`
  * `banner_left`
  * `banner_right`
  * `banner_sticky_top`
  * `banner_sticky_bottom`
* Interstitial
  * `interstitial_page_load`
  * `interstitial_exit`
  * `interstitial_pause`
* Video
  * `video_instream`
  * `video_outstream`
  * `video_rewarded`
  * `video_midroll`
* Native
  * `native_feed`
  * `native_article`
  * `native_recommendation`
* Special Formats
  * `sticky_footer`
  * `sticky_header`
  * `companion_banner`


---

# 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://adagio-io.gitbook.io/adagio-documentation/openrtb-s2s-endpoint/review-your-technical-integration/tagid-limits-and-guidelines.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.