> 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/for-advertisers/advertiser-lifecycle.md).

# Advertiser Guide

This guide explains the advertiser journey in TomoAds.

## 1) Set Up Your Account

* complete profile and billing details
* confirm account access

## 2) Fund Your Balance

* add funds from the available payment options in dashboard
* wait for payment confirmation

## 3) Create a Campaign

Typical campaign setup includes:

* campaign objective
* target audience settings
* schedule
* budget and bid strategy
* creatives and landing page

## 4) Review and Launch

After submission, your campaign may pass through review before going live.

Possible statuses:

* draft
* in review
* active
* paused
* ended

## 5) Track Performance

Use dashboard analytics to monitor:

* impressions
* clicks
* spend
* trend changes by date/device/geo (as available in your account)

## 6) Optimize

Common optimization actions:

* adjust targeting
* tune bids and budget pacing
* refresh creatives
* pause low-performing variants

## Best Practices

* start with a controlled budget and scale gradually
* run multiple creative variants
* review results consistently, not only once
* align landing page quality with ad promise


---

# 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/for-advertisers/advertiser-lifecycle.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.