> 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-joined-and-left-events.md). # Audience joined & left events When a user joins or leaves an audience, the Loyalty Engine can be configured to report an `AUDIENCE_JOINED` or `AUDIENCE_LEFT` event to your event stream. These events allow you to create reactors that trigger based on changes in audience membership. > #### Example > > Imagine you have an audience that includes all users who have made 5 purchases within a month. When a user meets this criteria and joins the audience, an `AUDIENCE_JOINED` event could trigger a reactor to award 100 points. For more ideas on how to use these event types, check out our [Create reactors for joining or leaving an audience](/product/loyalty-engine/audiences/audience-tutorials/create-reactors-for-joining-or-leaving-an-audience.md) tutorial. {% hint style="info" %} These event types will only appear in your event type list once you’ve created an audience in your loyalty tenant with the option to report join and leave events enabled. {% endhint %} *** ## Enabling audience joined & left events for an audience Audience joined and left events are enabled on a per-audience basis. To activate this feature, simply enable it in the configuration settings for the specific audience.

Audience joined & left events can be found in the create and edit audience screens of the Loyalty Console

--- # 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://kbase.whitelabel-loyalty.com/product/loyalty-engine/audiences/audience-joined-and-left-events.md?ask=&goal= ``` `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.