> 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-attendee-details.md).

# Event Attendee Details

Learn how supporters enter a name, email, and phone for each ticket on an Event Page, how attendees get their tickets, and where to manage attendee details.

When supporters buy tickets on your Event Page, they can enter details for each person attending. Each ticket can carry its own attendee's name, email, and phone, so every guest gets their own ticket and shows up correctly on your attendee list. This article covers what supporters see at checkout, how attendees receive their tickets, and where you manage attendee details afterward. Attendee details apply to Event Pages only.

## What Supporters See at Checkout

Once a supporter selects tickets, the Event Page shows an **Attendee details (optional)** section with this note: "Your information will be used for each ticket unless you enter attendee details."

For each ticket, the section shows a heading with the attendee number and ticket type, such as "Attendee 2 · VIP," and these fields:

* **First name**
* **Last name**
* **Email**
* **Phone**

The fields start with the purchaser's information. Supporters can leave them as they are, or replace them with each guest's details.

There's no setting to turn this section on or off in the Page Builder. It appears on every Event Page once tickets are selected.

## How Attendees Get Their Tickets

After a paid purchase goes through, or right away for a free registration, the tickets become active:

* The purchaser receives the receipt.
* Each attendee with a different email address receives an email titled "Tickets for" followed by the event name, with that attendee's tickets attached.

Each ticket includes a QR code you can scan to check the attendee in at your event.

## Manage Attendee Details

To view or update attendee details after a purchase:

1. Go to **Action Pages > Events**.
2. On the event row, click the people icon, or open the **⋯** menu and select **View attendees**.
3. On the attendee row, click **View**.
4. Update the attendee's information, then save your changes.

From the attendee's details, you can also resend their tickets with **Email Ticket**. To learn more, see [Manage Events](/action-pages/action-page-basics/manage-events.md).

{% hint style="info" %}
Employer and occupation are collected from the purchaser only. You can add them for an attendee in the attendee's details.
{% endhint %}

## Related Articles

* [Page Builder Overview](/action-pages/page-builder.md)
* [Event Tickets and Promo Codes](/action-pages/page-builder/event-tickets-and-promo-codes.md)
* [Event Details and Location](/action-pages/page-builder/event-details-and-location.md)
* [Manage Events](/action-pages/action-page-basics/manage-events.md)
* [Receipts and Confirmation Page](/action-pages/page-builder/receipts-and-confirmation-page.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-attendee-details.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.