> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/data-capture/events.md).

# Events

Track and capture customer interactions and behavioural data within the platform.

The Events module in UbiQuity handles the full registration process for your events. You can create a registration form, set capacity limits, send automated confirmation and reminder emails, and track who has registered.

Events work well as a standalone registration tool, but become more powerful when connected to UbiQuity emails. Sending your event link via a UbiQuity mailout lets you personalise the experience for each contact, send reminders only to those who have not yet registered, and link registrations back to your database contacts.

You can allow a single registration per person or enable multiple registrations per form, either as named places with individual details for each registrant, or as anonymous tickets where one person orders multiple spots.

### In this section

* [Creating an Event](https://docs.ubiquity.co.nz/documentation/data-capture/events/creating-an-event.md)
* [Details and Settings](https://docs.ubiquity.co.nz/documentation/data-capture/events/details-and-settings.md)
* [Fields and Validation](https://docs.ubiquity.co.nz/documentation/data-capture/events/fields-and-validation.md)
* [Confirmation Message](https://docs.ubiquity.co.nz/documentation/data-capture/events/confirmation-message.md)
* [Triggered Emails](https://docs.ubiquity.co.nz/documentation/data-capture/events/triggered-emails.md)
* [Deploying Your Event](https://docs.ubiquity.co.nz/documentation/data-capture/events/deploying-your-event.md)
* [Registrations and Reporting](https://docs.ubiquity.co.nz/documentation/data-capture/events/registrations-and-reporting.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.ubiquity.co.nz/documentation/data-capture/events.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.
