> For the complete documentation index, see [llms.txt](https://docs.eventnook.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventnook.com/online-registration-report/attendee-summary.md).

# Attendee Summary

The **Attendee Summary** report allows you to group and analyze attendee data based on selected fields. This helps you quickly understand patterns, segments, and key insights from your registrations.

***

### 🧭 How to Access

1. Log in to your **EventNook account**
2. Select your event
3. Go to:\
   **Report → Attendee Summary**

***

### 📊 What is Attendee Summary?

Attendee Summary lets you:

* Group attendees by selected fields
* Filter by attendee status and ticket type
* Generate summarized data for analysis

Unlike **View Attendees**, which shows raw data, this report provides a **grouped overview**.

***

### ⚙️ Filters & Options

#### 1️⃣ Attendee Status

Select which attendees to include:

* **Approved** → Confirmed attendees
* **Pending** → Awaiting approval, payment, or waitlist
* **Cancelled** → Cancelled registrations
* **All Attendees** → Includes all statuses

***

#### 2️⃣ Ticket Type

* Filter by **All Tickets** or specific ticket types

💡 Useful for analyzing specific ticket categories.

***

#### 3️⃣ Group By Fields

You can group data by up to **3 fields**.

**Available fields include:**

* Standard fields (e.g., Email, First Name, Last Name, Full Name)
* Discount Code
* Invitation Code
* ✅ **Any custom registration form fields you have created**

💡 *This gives you flexibility to analyze data based on your event’s specific requirements (e.g., company, job title, preferences).*

***

### 🛠️ How to Generate Report

1. Select **Attendee Status**
2. Select **Ticket Type(s)**
3. Choose up to **3 fields** under “Group by”
4. Click **“Generate Report”**

The system will display a summarized breakdown based on your selection.

***

### 💡 Use Case Scenarios

#### 1️⃣ Marketing Performance

* Group by **Discount Code** or **Invitation Code**
* Track which campaigns are driving registrations

***

#### 2️⃣ Corporate / Group Analysis

* Group by **Company (custom field)**
* See how many attendees are coming from each organization

***

#### 3️⃣ Attendee Segmentation

* Group by **custom fields** (e.g., job title, industry)
* Understand attendee profile and demographics

***

#### 4️⃣ Data Validation

* Quickly spot missing or inconsistent data

***

### ⚠️ Important Notes

* You can group by a maximum of **3 fields** at a time
* Results depend on the data collected in your registration form
* Pending includes:
  * Manual approval
  * Manual payment
  * Waiting list

***

### ✅ Best Practices

* Start with **one grouping field** for clearer insights
* Use relevant **custom fields** for deeper analysis
* Combine with **View Attendees export** for advanced reporting
* Ensure your registration form captures the right data

***

The **Attendee Summary** report helps turn raw attendee data into meaningful insights, making it easier to analyze and manage your event effectively.


---

# 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.eventnook.com/online-registration-report/attendee-summary.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.