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

# TomoAds Documentation

Welcome to the official TomoAds public documentation.

This GitBook is focused on:

* **Advertisers** running campaigns
* **Publishers** monetizing traffic

It intentionally avoids internal engineering and infrastructure details.

## What You Can Find Here

* how to get started quickly
* how campaigns work for advertisers
* how property and placement setup works for publishers
* Telegram Mini App requirements and expectations
* public roadmap notes

## Start Reading

1. [Quick Start](/start-here/quick-start.md)
2. [Advertiser Guide](/for-advertisers/advertiser-lifecycle.md)
3. [Publisher Guide](/for-publishers/publisher-onboarding.md)
4. [Telegram Mini App Requirements](/for-publishers/telegram-mini-app-verification.md)
5. [How TomoAds Works](/platform-overview/system-overview.md)

## Scope Note

If you need private/internal docs (operations, infra, internal APIs), keep those in a separate private documentation workspace, not this public GitBook repository.


---

# 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:

```
GET https://docs.tomoads.com/tomoads-documentation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.