> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/rules-and-customizations/rules-overview/targeting-with-audiences.md).

# Targeting with Audiences

An **Audience** is a named condition set — a reusable definition of *who*. Build a segment once, and every targeted experience across the platform can reuse it: to target an offer, scope a business rule, or drive a journey.

{% embed url="<https://youtu.be/TV4bw0z4KjU>" %}

**Where to find it**

Go to **Commerce → Audiences**. Each audience is a set of conditions a customer must match to be included; leave the conditions empty to match all customers.

**Build an audience**

1. Select **New Audience** and give it a clear name (for example, *Enterprise Accounts*).
2. Under **Conditions**, define who belongs. Each condition is an **object** (Customer, Order…), a **field** (segment, region, industry, company size…), an **operator**, and a **value** — for example, *Customer segment equals Enterprise*.
3. Add more conditions and combine them with **AND** (all must match) or **OR** (any can match). Nest groups for finer logic.
4. Save. Your segment is now available everywhere audiences are used.

**Reuse it everywhere**

Once saved, an audience can be selected wherever targeting applies:

* **Offers** — under *Audience & Eligibility*, target an offer so only members of the audience can receive it.
* **Business Rules** — scope a rule to specific audiences so it only applies to them.
* **Journeys** — route or gate steps by audience membership.

> **Tip:** When an offer targets more than one audience, a customer needs to match **at least one** (OR logic). Use **Audience Priority** to decide which offer wins when a customer qualifies for several.

**Learn more:** [Rules Overview](/product/rules-and-customizations/rules-overview.md) · [Creating and Managing Rule Sets](/product/rules-and-customizations/rules-overview/creating-and-managing-rule-sets.md).


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/rules-and-customizations/rules-overview/targeting-with-audiences.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.