# Fields and Validation

To start building your registration form, go to the Event Dashboard and click **Edit Fields and Validation**.

Any changes you make are not saved until you click Save. We recommend finalising your event form before it goes live. Editing a live event may produce inconsistent results for anyone currently completing the form. Deleting a field will permanently remove the data stored against that field for existing registrations.

Once your event is ready, activate it from the Event Dashboard and your event is ready to go.

***

### Registration Form Fields

Add fields to your registration form and edit them by clicking the properties icon. If your event uses named places, you can control which fields appear for additional registrants using the option to show the field in the additional registrants section.

<figure><img src="/files/visjwPH5wZ7SzUE37ggg" alt="A screenshot showing the Edit Fields and Validation screen where you build your form fields and introduction text."><figcaption><p>The Edit Fields and Validation screen where you build your registration form fields and introduction text.</p></figcaption></figure>

If you have enabled tickets under Event Settings, a Number of Tickets field is added to the form automatically.

Paid item fields are added up to a total alongside any event-level pricing. If any costs are present on the event, a payments page will be displayed to the registrant.

When event forms are submitted, data is stored against the event registration, not directly in the UbiQuity database. However, the registration is linked to the database contact. You can import event registrants into your database if needed.

***

### Merging Fields

If you send your event via a UbiQuity email, you can merge database fields into the registration form introduction, confirmation page, and triggered emails.

You can also merge fields from other UbiQuity interactions such as survey responses, provided they are linked to the relevant database contacts.

If you are not using a UbiQuity email and are placing the event link on a website, you can still merge fields, but only event fields, and only onto the Thank You page and triggered emails.

<figure><img src="/files/76S8jmbjiN58RikkCPCH" alt="A screenshot showing the insert merge fields button in the standard content editor."><figcaption><p>Use the highlighted button to insert merge fields.</p></figcaption></figure>

***

### Event Validation

You can make individual fields mandatory and set custom validation messages. For more complex rules, use the Event Validation section at the bottom of the Edit Fields and Validation screen to build conditional validation rules. For example: if a registrant selects email as their preferred contact method, then the email address field becomes mandatory.

***

### Inserting Links

Use the Insert UbiQuity Link function to add links to other events, surveys, or forms within your event content. You can add these links to the introduction, Thank You page, and triggered emails. For example, add a survey to a triggered email sent after the event, or add a Subscribe Form to the Thank You page for anonymous registrants to join your database.

<figure><img src="/files/AwGlnEaFnY51dTMIS52T" alt="A screenshot of the insert UbiQuity links button in the standard content editor."><figcaption><p>Use the highlighted button to insert UbiQuity links.</p></figcaption></figure>

If the event was sent via a UbiQuity email, you can also include Update Forms so contacts can update their database details directly from the event or a triggered email.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ubiquity.co.nz/documentation/data-capture/events/fields-and-validation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
