Contact fields from checkout questions
A checkout question built from a contact field saves its answer to the contact. Only a fixed list of fields can do this, and your own edits always win.
On this page
When you add a checkout question from Contact fields, each guest's answer is saved to their contact as well as to their order. Other questions stay with the order. Your contacts fill in as people register, and nothing you set by hand gets overwritten.
Which fields
In the event, open Sales → Questions, click Add field, and look under Contact fields:
Company, Job title, Industry, School, Date of birth, Website, Instagram, Twitter / X, LinkedIn and Address.
The list is fixed. A question about anything else, such as dietary needs or a shirt size, is a Custom question, and its answer stays on the order. Industry offers a set list of choices, the same for every organization. A question from the list shows "Saved to contact" in your Questions.
Adding questions needs Pro.
Whose contact
| Where you ask it | Whose contact it fills |
|---|---|
| Asked once per checkout | The buyer's |
| Asked for each ticket | Each ticket holder's own |
When an answer replaces a value
- Most fields take the newest answer. If Dana changes jobs and answers Company differently next year, the contact updates.
- Date of birth fills once. A later answer never replaces it.
- A field you edited by hand is locked, and answers never replace it.
Conflicts
When an answer can't be saved because the field is locked or already filled once, and it differs from what the contact holds, Review lists it under Conflicting answers. You choose Keep or Use. A different answer for Date of birth can mean two people share one email.
If you keep the current value, the same answer won't raise a conflict again.
Good to know
- An answer to a poll never reaches a contact.
- Integrations hear about these changes, because they come from a registration. See What Ovante sends and what stays.
The rule behind this page
- When
- You edit a contact's field by hand
- Then
- The field locks: later registrations and imports never write over it, and a field you clear stays clear. A member's own edits to their profile are the one exception.