> 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/onsite-registration/dashboard.md). # Dashboard The Dashboard helps you monitor and analyze event attendance from different perspectives. Each tab gives you a unique way to view your data depending on what you need. *** #### 🧭 1. Overview The **Overview** tab gives you a quick, high-level snapshot of your event attendance. **What you’ll see:** * Total registrations * Number of attendees checked in * Number of absentees * Percentage of attendance **When to use it:** * During event check-in for a quick status update * To get an instant understanding of overall turnout * For a simple summary without diving into details *** #### 🎟️ 2. By Ticket The **By Ticket** tab breaks down attendance based on ticket types. **What you’ll see:** * Attendance grouped by ticket category (e.g., VIP, General, Early Bird) * Check-in status for each ticket type * Comparison between different ticket groups **When to use it:** * To analyze which ticket types are most popular * To monitor VIP or special access attendees * To evaluate ticket performance after the event *** #### 🧩 3. By Field The **By Field** tab lets you group attendees using custom registration fields. **What you can do:** * Filter attendees (e.g., Approved, Pending) * Group by selected fields (e.g., Company, Role, Country) * Generate a report based on your selection **What you’ll see:** * A customized breakdown of attendees based on your chosen field * Sortable totals for easier analysis **When to use it:** * To segment your audience (e.g., by job title or organization) * To analyze attendee demographics * To create tailored reports for stakeholders 💡 *Example:*\ Group attendees by “Company” to see which organizations have the highest attendance. *** #### 📅 4. By Date The **By Date** tab shows attendance trends over time. **What you’ll see:** * Check-in activity by date (and sometimes time) * Daily attendance patterns **When to use it:** * For multi-day events * To track peak check-in times * To understand attendance flow throughout the event *** #### ⚡ Pro Tips * Use **Overview** for quick monitoring * Use **By Ticket** for sales and ticket performance insights * Use **By Field** for deeper audience analysis * Use **By Date** for time-based trends and planning *** This set of tabs gives you both a **big-picture view and detailed insights**, helping you make better decisions during and after your event. --- # 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/onsite-registration/dashboard.md?ask=&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.