# Publishers

**Overview**

The "Publishers" section in our ad server is designed to manage and store vital information about advertisers who participate in the advertising ecosystem. This section includes various fields to comprehensively capture the details of each advertiser.

### General Settings

1. **Name**: The full name of the publishers. This is the primary identifier for the publisher within the system.
2. **API Endpoint**: An API endpoint that can be given to the publisher for API live reporting.\
   Example endpoint 

```
https://app.qntv.io/api/statsapi?startDate={YYYY-MM-DD}&endDate={YYYY-MM-DD}&token=auto_generated_token
```

1. **Revenue Model**: Specifies the type of revenue model the publisher is engaged with. It can be either a 'Fixed Price' model where the payment terms are set in advance or a 'Revenue Share' model where the payment depends on the performance of the ads.
2. **Revenue Split**: This field details the percentage or terms of revenue sharing between the publisher and the platform, applicable in the case of a Revenue Share model.
3. **TPP (Third Party Pixels)**: see [Third Party Pixels (TPP)](/general/third-party-pixels-tpp.md) section for more info

**Utilization**

This section is primarily used by the ad server administrators and sales teams to manage publisher accounts, track their activity, and customize their ad serving experience based on the provided information. The details captured in this section are crucial for effective ad campaign management and billing processes.


---

# Agent Instructions: 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.privateadserver.com/supply/publishers.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.