> ## Documentation Index
> Fetch the complete documentation index at: https://docs.business.plvr.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Recurring and community events

> Build an audience over time, understand who returns, and bring people back to your next event.

## Who this is for

You run events regularly, such as a monthly night, a series or a community gathering, and your success depends on people coming back.

## What to set up

In priority order:

1. **Keep your organization profile current.** See [Organization settings](/organization/settings). Your profile is the constant between events.
2. **Understand your audience.** [Audience](/organization/audience) shows who attends and how many attendees come back, with an exportable list.
3. **Grow followers.** See [Followers](/events/followers) for the people following your event.
4. **Re-engage with email.** Send [email campaigns](/promotions/campaigns) to ticket holders, interested followers or your own list, and track opens, clicks and revenue.
5. **Run RSVP events if you need approval.** See [RSVP](/events/rsvp) to approve or reject requests and export the list.
6. **Reward loyalty.** Use [promo codes](/promotions/promo-codes) for returning guests or partners.
7. **Learn what works.** Use [tracking links](/promotions/tracking-links) for each channel.

Each new event is still created with the PLVR team. Email [partners@plvr.io](mailto:partners@plvr.io), and see [Ticketing concepts](/tickets/concepts) for what to ask for.

## What to skip

* Multi-day structures and bundles, unless a particular edition needs them.
* PLVR Tap, unless you want cashless at a given edition.

## Team shape

A small core team often plus a volunteer gate crew. See the [Core team](/roles/core-team), [Marketing team](/roles/marketing-team) and [Data team](/roles/data-team) pages.

## Common pitfalls

* Only looking at one event's sales instead of the Audience page across events.
* Emailing the same list too often.
* Starting a new event page from scratch rather than reusing what worked last time.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.