# Limit a reactor an audience

## Introduction

Creating a reactor which can only be triggered when a user is in a particular audience is a popular way to offer bonus rewards to your end-users.

It can also be used to ensure that the end-user has met certain requirements, such as age verification, before they can earn points.

{% hint style="info" %}
To see an example of a configuration that uses an audience constrained reactor see the [Create advanced or multi-event reactors using Audiences](/product/loyalty-engine/reactors/reactor-tutorials/create-advanced-or-multi-event-reactors-using-audiences.md) article.
{% endhint %}

***

## Configuration

{% hint style="warning" %}
Ensure that the event you want to reactor to be listening for has the 'Audience' enhancer enabled. See the [Event enhancers](/product/loyalty-engine/events/event-types/event-enhancers.md) page for more information.
{% endhint %}

1. Navigate to Events > Reactors. Click 'Create in the top right corner.
2. Give the reactor a name and choose the event you want to reactor the listen for from the 'Event type' list.
3. Move to the 'Payload Constraints' tab. Click the 'In Audience' button in the Audiences section and select the audience the user must be part of for the reaction to trigger.
4. Configure the reaction and effectivity. Click save.

<figure><img src="/files/IQcM0ZDWCidruqNpDodu" alt=""><figcaption><p>Reactor being constrained to an audience</p></figcaption></figure>

***

## Tips

#### Limiting a reactor to only trigger for users NOT in a particular audience

It's possible to create a reaction which only triggers if a user is *not* in a particular audience by editing the JSON schema produced in step 3 of the configuration guide. **After completing step 3,** click 'JSON' in the <kbd>BLOCK/JSON</kbd> switcher to begin editing the JSON schema. Make the following adjustments to the schema.

1. Add the line **`"not": {`** below the `"audiences": {` line (line 6 in the sample schema).
2. Add an additional closing bracket `}` below the closing square bracket (line 13 in the sample schema).

<pre class="language-json" data-title="Sample JSON schema to exclude users in a particular audience" data-line-numbers><code class="lang-json">{
    "type": "object",
    "$schema": "http://json-schema.org/draft-06/schema#",
    "properties": {
        "audiences": {
<strong>            "not": {
</strong>                "type": "array",
                "contains": {
                    "enum": [
                        "8807dc2d-8aa5-4d00-842b-1da4ae95f902"
                    ]
                }
<strong>            }
</strong>        }
    },
    "required": []
}
</code></pre>


---

# 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://kbase.whitelabel-loyalty.com/product/loyalty-engine/reactors/reactor-tutorials/limit-a-reactor-an-audience.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.