> 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/platform-overview/system-overview.md).

# How TomoAds Works

TomoAds connects advertisers who want reach with publishers who have traffic.

## High-Level Flow

1. Advertiser creates and funds campaigns.
2. Publisher connects property and configures ad placements.
3. TomoAds matches campaigns to eligible publisher inventory.
4. Ads are delivered and user interactions are measured.
5. Spend and earnings are reflected in dashboards and payout flows.

## For Advertisers

You get:

* campaign setup controls
* budget controls
* performance visibility
* optimization over time

## For Publishers

You get:

* property verification flow
* placement control
* earnings tracking
* payout requests

## Platform Principles

TomoAds is built around:

* **Performance**: fast ad delivery
* **Trust**: measured interactions and fraud controls
* **Control**: transparent statuses and account-level management

## Current Product Lanes

* web-based inventory and placements
* Telegram Mini App web context requirements for supported flows

Dedicated Telegram bot-message ad product flows are evolving and should be treated as roadmap until explicitly announced as live.


---

# 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/platform-overview/system-overview.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.