> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/page-builder/event-tickets-and-promo-codes.md).

# Event Tickets and Promo Codes

Add ticket types and groups, set prices, quantities, and sale dates, and create promo codes for an Event Page in the Page Builder.

**Tickets** and **Discounts** set what supporters can buy on your Event Page. You'll find them in the Page Builder under **Event > Tickets** and **Event > Discounts**. This article covers ticket groups, ticket types, and promo codes.

## How Tickets Are Organized

* **Ticket groups** organize your tickets at checkout. At least one group is required. The group name is optional.
* **Ticket types** sit inside a group. Drag ticket types to reorder them or move them between groups.

New Event Pages start with a free General Admission ticket in a group named Tickets.

## Add a Ticket Type

To add a ticket type:

1. Go to **Action Pages > Pages**.
2. Hover over the Event Page you want to edit.
3. Click **⋮ > Edit**.
4. Select **Event > Tickets**.
5. Click **Add ticket type**.
6. Enter the ticket details.
7. Click **Save**.

The ticket appears on the Event Page when **Visible** is on.

| Field                             | What It Does                                                                                          |
| --------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Name                              | The ticket name. Required.                                                                            |
| Description                       | What the ticket includes.                                                                             |
| Price                             | The ticket price. Required. Enter 0 for a free ticket.                                                |
| Quantity                          | How many tickets are available. Turn on **Unlimited quantity** for no limit.                          |
| Max per order                     | The most tickets of this type a supporter can buy at once.                                            |
| Sales start and end date and time | Optional. Leave blank to sell the ticket whenever the page is live.                                   |
| Fair market value                 | The ticket's fair market value. Turn on **Show fair market value** to show it under the ticket price. |
| Show remaining quantity           | Shows how many tickets are left.                                                                      |
| Visible                           | Shows or hides the ticket on the Event Page.                                                          |

{% hint style="warning" %}
After a ticket type has sales, you can't change its price or remove it. Turn off Visible to stop selling it.
{% endhint %}

## Add a Ticket Group

To add a group, click **Add ticket group** and enter an optional group name. To delete a group, remove its ticket types first.

## Create a Promo Code

Promo codes give supporters a discount at event checkout.

To create a promo code:

1. In the Page Builder, select **Event > Discounts**.
2. Click **Add promo code**.
3. Enter the **Code**. Letters are changed to uppercase.
4. Choose a **Type**: **Fixed amount** (a discount in dollars) or **Percentage** (0 to 100 percent off).
5. Enter the **Value**.
6. Click **Save**.

Supporters enter the code at checkout. A promo code works only on the Event Page it was created on.

## Related Articles

* [Event Details and Location](/action-pages/page-builder/event-details-and-location.md)
* [Manage Events](/action-pages/action-page-basics/manage-events.md)
* [Page Builder Overview](/action-pages/page-builder.md)


---

# 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://docs.anedot.com/action-pages/page-builder/event-tickets-and-promo-codes.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.