> For the complete documentation index, see [llms.txt](https://kbase.whitelabel-loyalty.com/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kbase.whitelabel-loyalty.com/product/loyalty-engine/audiences/audience-tutorials/create-audiences-based-on-user-activity/create-an-audience-of-users-who-have-or-havent-reported-one-or-more-events.md).

# Create an audience of users who have or haven't reported one or more events

## Introduction

Creating audiences which track end-user events can be used in a number of ways. They can play a part in the gamification elements of your loyalty program, to incentivise users to complete specific tasks to unlock rewards. They can also be used to track users who aren't active in your program and offer extra rewards to try and re-engage them.

***

## Configuration

1. Navigate to Users > Audiences and then click 'Create' in the top right corner.
2. Give the audience a name and description. Turn on AUDIENCE\_JOINED and AUDIENCE\_LEFT events if needed. Set the refresh rate to 'Reactive'.
3. Move to the criteria tab. The criteria should be;
   * Event type is *the event you want to track*
   * Event occurrence count is (to track users who haven't recorded an event) or greater than (to track users who have recorded an event) 0.
4. Optional - click 'Add Group' in the top right corner to add additional criteria to the audience.

***

## Tips

* Adding an extra requirement that the event payload matches a particular schema allows you to be selective about the behaviour you want to track.
* Adding date logic to the audience criteria allows you to limit the events to a certain time period. For example you may want to find users who do not have a particular event recorded in the last 12 months to track unengaged users.
* Using extra groups allows you to find users who may have performed one action but not another. You could then incentive them to be more engaged with the program.
* Using `AUDIENCE_JOINED` and `AUDIENCE_LEFT` events related to these audiences can automate the process of gamification or reengagement. See the [Create campaigns for joining or leaving an audience](/product/loyalty-engine/audiences/audience-tutorials/create-campaigns-for-joining-or-leaving-an-audience.md) article for more information.


---

# 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://kbase.whitelabel-loyalty.com/product/loyalty-engine/audiences/audience-tutorials/create-audiences-based-on-user-activity/create-an-audience-of-users-who-have-or-havent-reported-one-or-more-events.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.