Overview
Data capture lets you collect structured information from customers at key points in their journey — during event checkout, at registration, and through forms. You create reusable questions in a central library, then assign them to appear wherever you need them: across all events, on specific events, per ticket, or as part of customer registration. The system handles the full lifecycle: question creation, assignment to the right context, collection during checkout or post-purchase, and storage of responses for reporting and operations.How It Works
Data capture operates on three layers:- Questions — Reusable prompts defined in your question library. Each question has a type (text, date, selection, etc.), optional validation rules, and can include a description shown to customers.
- Assignment — Questions are assigned to contexts that control where they appear. A single question can be assigned to multiple contexts — for example, asked at every event, on specific ticket types, or only during customer registration.
- Responses — Customer answers are stored against their order or profile. Responses can be viewed per order, exported in reports, and included on invoices. Data capture responses can also be submitted programmatically via the Data Capture API endpoint.
Question Groups
Questions belong to one of four groups, which determines where they appear and who sees them:| Group | Visible to Customers | Purpose |
|---|---|---|
| Shop | Yes | Standard questions shown during checkout |
| Marketing | Yes | Marketing preference questions with consent tracking |
| Internal | No | Event codes and EPOS questions for staff use |
| Access Control | No | Questions prompted during zone scanning |
Built-in Customer Fields
In addition to custom questions, the platform includes built-in fields for collecting standard customer information. These are configured at the company level from Data Capture > Settings rather than through the question library. Each built-in field can be set to one of five states:| Setting | Behaviour |
|---|---|
| Disabled | Field is not shown anywhere |
| Optional | Field is shown during checkout but can be left blank |
| Required | Field is shown during checkout and must be completed |
| Optional (hidden) | Field is not shown during checkout — it appears on the post-purchase Complete data capture page instead |
| Required (hidden) | Field appears on the post-purchase Complete data capture page and must be completed |
| Field | Notes |
|---|---|
| Full name | Customer’s first and last name |
| Date of birth | |
| Address | Full address fields (lines, city, postcode, country) |
| Phone number | Includes country code selector |
| Title | e.g. Mr, Mrs, Dr |
| Nationality | Country selector |
| Billing address | Shown during payment |
| Delivery address | Shown during payment when fulfilment features are enabled |
Data Capture Settings
Navigate to Data Capture > Settings to configure:- Built-in customer fields — Set each field to disabled, optional, required, or hidden as described above
- Imported orders can skip data capture — When enabled, orders created through data imports are not required to have data capture responses
- Default country order — Control the ordering of countries in nationality and address selectors, useful if most customers are from a specific region