Task · Questions
Add a field about your event or its attendees
Keep details you fill in yourself, like a Wi-Fi password or a seat number, to use in your emails, pages and tickets.
5 steps · About 3 minutes
-
Open Settings and select Metadata
Select Add an event field for something that is the same for the whole event, or Add an attendee field for something different for each attendee.
Your eventSettings -
Name the field and pick What you fill in
A field holds short text, long text, a number, on or off, or a pick from a list.
A Description is optional. Your team reads it beside the box when somebody fills the field in on an event.
-
Answer What it’s about
- This event gives the field one value for the whole event, like a Wi-Fi password.
- Each attendee gives it a different value per person, like a seat number.
Each attendee also asks Who can see it?. The attendee too puts the value on their ticket, and just your team keeps it internal.
go.tito.io/acme/admin/settings/metadata?new=1 -
Select Add field
A field belongs to the whole account, so every event you run gets a place to fill it in.
-
Fill in this event's value
Back on Settings → Metadata, type what this event should say into the field's box and select Save.
go.tito.io/acme/summer-fetes-summer-fete/admin/settings/metadataYou fill a field in yourself.Anything people answer themselves is a question. See Ask attendees a question.
Where to put a field about the event
In a message, select Insert on the compose screen and pick the field from the Event details group. What goes out is whatever the field says at the moment you send.
In the wording on your pages and emails, open Customize, go to the Words tab and find the line you want to change. Type { in the box and pick the field. The order confirmation is one of the screens in the list, so a Wi-Fi password can go out with it.
In a theme, read the field as event.fields. followed by the short name printed beside it. See the theme author's reference.
Where a field is empty on an event, the whole line it's in is left out, so one wording covers every event.
Putting a field in calendar entries
A field can go in the calendar entry people add from their ticket, below the event’s description. This suits a joining link for an online event. In your account’s Metadata settings, turn on Include in calendar entries for the field and select Save. You can also turn it on when you add the field. It applies to every event, and an event where the field is empty leaves it out.
Filling in a field about an attendee
An attendee's own Edit form has a box for each field. For a lot of people at once, use the attendee list's From a file import, where a row with an identifier updates the attendee it matches. The account API can read and write these too. See the API reference.
Default values
A Default value is what a new event starts with, and it suits a field that rarely changes, like a support address. To say something else on one event, type in that event's box. To say nothing at all there, untick Use the account default and leave the box empty.
Changing a field later
Edit beside a field opens its own page, where you can change the name and the description, see everywhere it's used, and archive it. A change there reaches every event.
Archive takes a field out of every event's list and keeps the values already typed. Archived fields have a list of their own on the same screen, each with Restore. A field no event has ever filled in says Delete instead, and deleting it removes it for good.
Fields in more than one language
A short text or long text field can be translated. It appears in Translations under Event details, and attendees read it in the language they're booking in.