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

# Agency

The Agency section of Perkville Docs provides guidance for agencies using Perkville to places in the loyalty programs of businesses that have chosen to work with them. Here is a brief summary of the documents.

### [Overview](https://docs.perkville.com/features/agency/overview.md)

The overview section introduces the Perkville Ad Platform, explaining its purpose, initial placement in loyalty emails, and the requirement for businesses to opt in and manage their own relationships with advertising agencies.

### [Advertisers](https://docs.perkville.com/features/agency/advertisers.md)

Agencies can create "Advertisers" which are folders for content related to each advertiser such as their creative, suppression lists, and images.

### [Images](https://docs.perkville.com/features/agency/images.md)

The "IMAGES" section allows agencies to add, edit, and remove images associated with creative.

### [Creatives](https://docs.perkville.com/features/agency/creatives.md)

The "CREATIVES" section enables agencies to create and manage the individual ads that will be displayed. This includes setting up ad images, text, and links.

### [Campaigns](https://docs.perkville.com/features/agency/campaigns.md)

The "CAMPAIGNS" section allows agencies to group creatives into campaigns, define targeting, and set ad schedules.

### [Suppressions](https://docs.perkville.com/features/agency/suppressions.md)

The Advertiser Suppression List prevents ads from being shown to specific email addresses. Agencies can upload suppression lists in CSV format.

Please also refer to the [Ad Terms](https://info.perkville.com/terms).


---

# 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.perkville.com/features/agency.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.
