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

# Welcome

## Welcome to Publicit — the platform where brands and media owners meet directly, no intermediaries, no black boxes. d

## What is Publicit?

Publicit is a self-serve media infrastructure. You browse real inventory — outdoor billboards, digital placements, TV spots, radio, print, and more — choose exactly where your brand appears, and pay a transparent price. Each publisher reviews and confirms your campaign, so you always know your ads are running exactly where you planned.

No auctions. No hidden fees. No guesswork.

***

## How it works for advertisers

**1. Create a campaign** — Set your objective, budget, dates, and targeting.

**2. Search inventory** — Explore thousands of spaces filtered by format, location, impressions, and price. View each space on a map or in a browsable grid.

**3. Build your media plan** — Add spaces to your campaign. Mix digital with outdoor, TV, radio, or print — all in a single campaign.

**4. Pay securely** — Campaign payments are processed via Stripe with full invoice support and downloadable receipts.

**5. Publisher confirmation** — Each publisher decides on their own space, typically within 48 hours. Approval is per space, so your campaign runs with whichever spaces were accepted. You're notified of every status change.

**6. Your campaign goes live** — Track performance across all your spaces from one dashboard.

***

## What's in this guide

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>🚀 Quick Start</strong></td><td>Create your account and launch your first campaign.</td><td><a href="/advertiser/quick-start/creating-your-account.md">Creating your account</a></td></tr><tr><td><strong>📋 Campaigns</strong></td><td>Objectives, targeting, formats, budgets, and scheduling.</td><td><a href="/advertiser/campaigns/campaign-types.md">Campaign objectives</a></td></tr><tr><td><strong>📊 Reporting</strong></td><td>Track spend, impressions, and campaign performance.</td><td><a href="/advertiser/reporting-and-analytics/campaign-metrics.md">Campaign metrics</a></td></tr><tr><td><strong>💳 Billing</strong></td><td>Payment methods, invoices, and budget controls.</td><td><a href="/advertiser/billing-and-finance/payment-methods.md">Payment methods</a></td></tr><tr><td><strong>📜 Policies</strong></td><td>Content guidelines and the publisher review process.</td><td><a href="/advertiser/ad-policies/content-guidelines.md">Content guidelines</a></td></tr><tr><td><strong>❓ FAQ</strong></td><td>Quick answers to common questions.</td><td><a href="/advertiser/faq/faq.md">Frequently asked questions</a></td></tr></tbody></table>

***

## Need help?

{% hint style="info" %}
Contact our team at <info@publicit.es> — we typically reply within one business day.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.publicit.com/advertiser/overview/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.