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

# Audiences

Define the different target segments you tailor content for

Audiences allow you to define the different target segments you tailor content for. By specifying audience-specific details and writing rules, you can ensure your workflows generate content that resonates with each unique segment.

## Audience Attributes

For each Audience, you can define:

### Audience Name

The audience segment name (e.g., "Enterprise Customers," "Small Business Owners," "Content Marketers").

### Audience Description

Describe this audience and what matters to them. Include:

* Who they are (job titles, company size, industry)
* Their goals and motivations
* Their pain points and challenges
* What language and terminology resonates with them

### Writing Rules

These rules help with structure and content for all workflows creating or refreshing content for this audience. Use one rule per line. You can toggle "Show global rules" to see how your audience rules fit within your global guidelines.

## Example

A company might define audiences for:

**Enterprise Customers**

* Description: "Decision-makers at companies with 1000+ employees. They prioritize security, compliance, scalability, and ROI. They need to justify purchases to multiple stakeholders and have longer sales cycles."
* Writing Rules:
  * Emphasize enterprise-grade security and compliance
  * Include ROI calculations and business impact metrics
  * Reference case studies from similar-sized companies

**Small and Medium Businesses**

* Description: "Founders and marketing leads at companies with 10-500 employees. They're resource-constrained, value ease of use, and need quick time-to-value. Price sensitivity is higher."
* Writing Rules:
  * Focus on ease of implementation and quick wins
  * Highlight self-service capabilities
  * Avoid enterprise jargon

**Content Marketers**

* Description: "Content team members responsible for creating and managing content at scale. They care about quality, efficiency, and maintaining brand voice across high volumes of content."
* Writing Rules:
  * Use content marketing terminology
  * Focus on workflow efficiency and scale
  * Emphasize quality and brand consistency

## Adding Audiences

1. Navigate to the **Audiences** tab in your Brand Kit
2. Click **Add Audience**
3. Enter the **Audience Name**
4. Add an **Audience Description** explaining who this audience is and what matters to them
5. Add **Writing Rules** specific to this audience (these help with structure and content for all workflows creating content for this audience)
6. Save your changes

## Audience Variables

When an Audience is selected, use these variables:

| Attribute                  | Variable                               | Usage                                   |
| -------------------------- | -------------------------------------- | --------------------------------------- |
| **Audience**               | `{{brand_kit.audience}}`               | Access the selected audience's details. |
| **Audience Name**          | `{{brand_kit.audience.name}}`          | Name of the selected audience.          |
| **Audience Description**   | `{{brand_kit.audience.description}}`   | Understand who you're writing for.      |
| **Audience Writing Rules** | `{{brand_kit.audience.writing_rules}}` | Apply audience-specific writing rules.  |


---

# 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.airops.com/context/brand-kit/audiences.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.