> For the complete documentation index, see [llms.txt](https://help.fluorescent.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fluorescent.co/section-studio/smart-sections/audiences.md).

# Audiences

{% hint style="warning" %}
Available only on **Smart sections** and **Ultimate** plans. Learn about [upgrading your plan](/section-studio/get-started/choose-subscription-plan.md).
{% endhint %}

**Audiences** are a way to group your visitors based on their traits, allowing you to show personalized content to the right visitors, at the right time.&#x20;

You can create audiences based on different criteria, like location, time and date, how visitors arrive at your site, and other data about your customers.

<figure><img src="/files/SmMtodPNANqKumY6cq0G" alt="" width="563"><figcaption></figcaption></figure>

## Create audiences

***

{% columns %}
{% column width="66.66666666666666%" %}
Go to the **Audiences** page to create an audience.&#x20;

Select rules to group visitors into different audiences based on different criteria, like geolocation, time and date, UTM parameters, local weather forecast, and more.&#x20;

On the [Ultimate plan](/section-studio/get-started/choose-subscription-plan.md), you can use your Shopify and Klaviyo customer segments, as well as Shopify markets, as audience rules.

{% endcolumn %}

{% column width="33.33333333333334%" %}

<figure><img src="/files/uCNKzVhSwmUHqF9yW2KK" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}

#### Steps

1. Go to the **Audiences** page.
2. Click **Create new audience.**
3. Enter an **audience name**. (You can change the name later)
4. Select a **rule type** that will define who to include in the audience.
5. Click **Save**.
   {% endhint %}

### <mark style="color:$primary;">Audience rules</mark>

Find guides for each rule type. You can combine rules to create finely targeted audiences.

<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><mark style="color:blue;"><strong>Date range</strong></mark></td><td></td><td><a href="/pages/v95OR0TYlGRYx63lDbkj">/pages/v95OR0TYlGRYx63lDbkj</a></td></tr><tr><td><mark style="color:blue;"><strong>Domain referrer</strong></mark></td><td></td><td><a href="/pages/RCRaVNpaJQBC1CAERa3c">/pages/RCRaVNpaJQBC1CAERa3c</a></td></tr><tr><td><mark style="color:blue;"><strong>Geographic location</strong></mark></td><td></td><td><a href="/pages/NhFZrnrc4E4aJ4WR80Cr">/pages/NhFZrnrc4E4aJ4WR80Cr</a></td></tr><tr><td><mark style="color:blue;"><strong>Login status</strong></mark></td><td></td><td><a href="/pages/onCtLSiavOgJ2Wd4EgTE">/pages/onCtLSiavOgJ2Wd4EgTE</a></td></tr><tr><td><mark style="color:blue;"><strong>Time zone</strong></mark></td><td></td><td><a href="/pages/mbLgpqNUb9jmRbMZONsb">/pages/mbLgpqNUb9jmRbMZONsb</a></td></tr><tr><td><mark style="color:blue;"><strong>UTM parameters</strong></mark></td><td></td><td><a href="/pages/VZGng67sgRfDxOUAkmBl">/pages/VZGng67sgRfDxOUAkmBl</a></td></tr><tr><td><mark style="color:blue;"><strong>Weather</strong></mark></td><td></td><td><a href="/pages/h07zMwq7RLyfBcj6VtUm">/pages/h07zMwq7RLyfBcj6VtUm</a></td></tr><tr><td><mark style="color:blue;"><strong>Klaviyo segments</strong></mark></td><td><sup>Ultimate plan</sup></td><td><a href="/pages/Y4cfKvSMZesuLQWJiiDk">/pages/Y4cfKvSMZesuLQWJiiDk</a></td></tr></tbody></table>

### Next steps

***

After creating audiences, add [section variants](/section-studio/smart-sections/section-variants.md) with alternate content and styles that are tailored to each audience. Then [assign audiences to section variants](/section-studio/smart-sections/section-variants.md#assign-audiences-to-section-variants) to activate them on your storefront.


---

# 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://help.fluorescent.co/section-studio/smart-sections/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.
