> For the complete documentation index, see [llms.txt](https://tads.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tads.gitbook.io/docs/resourses/ad-formats.md).

# Ad Formats

## **TGB (Text-Graphic Block)**

<div align="center"><figure><img src="/files/ukqcswFtJhOvPG0RM5Zh" alt="" width="296"><figcaption></figcaption></figure> <figure><img src="/files/eQT7p4eROZ16lgbhWRTA" alt="" width="369"><figcaption></figcaption></figure></div>

An ad in the form of a TGB has the following format requirements:

* **Image**: 128x128, format webp/jpeg/png, size up to 50kb
* **Title**: up to 30 characters
* **Description**: up to 60 characters
* **Link**: any length (we recommend using UTM tags and other methods to track the traffic received through it)

{% hint style="info" %}
Our ad widget inserts the content of the ads into the part of the code specified by the publisher. This can be a component on the screen, a popup window, or another design solution – in all cases, we insert the content, and the placement method is implemented on the publisher's side.
{% endhint %}

## Fullscreen Banner

<div align="center"><figure><img src="/files/ojRiKNDGL4iFEoG1Iegz" alt="" width="296"><figcaption></figcaption></figure> <figure><img src="/files/DcQ4YHayifbsH1SMGsrq" alt="" width="296"><figcaption></figcaption></figure></div>

An ad in the form of a Fullscreen banner has the following format requirements:

* **Image**: 300x300, format webp/animated webp/jpeg/png, size up to 200kb
* **Title**: up to 60 characters
* **Description**: up to 160 characters
* **Link**: any length (we recommend using UTM tags and other methods to track the traffic received through it)


---

# 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://tads.gitbook.io/docs/resourses/ad-formats.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.