> 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/getting-started/publishers/create-widget.md).

# Create Widget

## 1. Decide how to display the ad

### General conditions

You can integrate the ad wherever it fits best in your application’s flow. This could be a screen component, a popup, or any other design element. We provide the ad content (images, text, etc.), while you control placement and styling.

### 1.1 Choose Ad formats

Сhoose one of these ad formats, or install both to increase your income (each format requires its own widget):

* <mark style="color:green;">Text-Graphic Block (TGB)</mark>

  Native text-and-image unit that integrates into app’s content for a seamless user experience. Multiple ads can be shown within one widget.
* <mark style="color:green;">Fullscreen Banner</mark>\
  Telegram-style fullscreen ad that aligns with interface and maximizes user engagement. Only one ad can be shown at a time.

Detailed descriptions of ad formats with examples can be found in our [documentation](https://docs.tads.me/resourses/ad-formats).&#x20;

### 1.2 Choose Integration options

Each ad format can be integrated into your app in different ways. It should be natively integrated into the user experience to feel natural and non-intrusive.\
Choose one option for each widget described below that best meet your app’s needs and objectives:

* <mark style="color:green;">Rewarded Ad</mark>\
  The user should receives a reward for interact with the ad:

  * for TGB ads — a reward is given for clicking the ad (CPC)
  * for Fullscreen ads — a reward is given for watching the entire ad (CPM)

  *Examples of rewards: additional attempts, in-app currency, boosters, or any other bonus suitable for your app.*
* <mark style="color:green;">Non-Rewarded Ad</mark>\
  The user does not receive any reward for interacting with the ad:
  * for TGB ads — the ad should be organically placed within the interface.\
    \&#xNAN;*For example, as a standalone ad block embedded into a content page.*
  * or Fullscreen ads — The ad should appear as a result of user action or at natural breakpoints in the flow.\
    \&#xNAN;*For example, after clicking a “watch ad” button or between game levels.*

## 2. Add widget in the account

In your personal dashboard go to the Publisher section, then to the Widgets subsection. Click the “Create Widget” button and specify the required parameters:

<div align="left"><figure><img src="/files/JUF10RV6AWErSrfG2qGg" alt="" width="335"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Webhook URL** is the path for your webhook to receive a GET or POST request from TADS when user occurs a click or view event. [Learn more](/docs/getting-started/publishers/webhooks.md)
{% endhint %}

## 3. Get widget ID

Once the widget is created, a dashboard with a list of widgets will open, displaying the <mark style="color:green;">widget ID</mark>**.** You will need this widget ID in the next step — [embedding it into your code](https://docs.tads.me/getting-started/publishers/embed-widget)

<div align="left"><figure><img src="/files/uqW2aj9tdMCp9OXiHZb8" alt=""><figcaption></figcaption></figure></div>


---

# 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/getting-started/publishers/create-widget.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.