Task · Questions

Keep metadata about an event and its attendees

Record what you fill in yourself, about the event or about the people at it.

3 steps · About 3 minutes

1. Open Settings and select Metadata

   Your eventSettings

2. Fill in this event's value

   Under About this event, each detail has its own box. Type what this event should say and select Save.

   go.tito.io/acme/summer-fete/admin/settings/metadata

3. To add one, select Add a detail

   Give it a Name, pick What you fill in, and answer What it’s about. This event gets one value for the whole event. Each attendee gets a different value per person, and asks Who can see it? as well.

   A Description and a Default value are optional. A Default value on a Pick from a list detail has to be one of that detail's own choices.

   A Description is for you and your team, and appears beside the box when an event fills the detail in. A detail about each attendee takes no default, because its value belongs to one person.

The two groups

About this event is one value for the whole event, like a Wi-Fi password or a hashtag. Every event gets a box for it and fills it in its own way.

About each attendee is a different value per person, like a seat number or a note on how you met them. Who can see it? decides which: The attendee too puts the value on their ticket, and Just your team keeps it internal. The row on the list says which one you picked.

Nobody is ever asked for metadata. What people answer themselves are questions, which have a section of their own. See Questions.

The types

Short text holds one line, like a link or a hashtag. Long text holds a paragraph or more. Most details are one of these two.

On or off and Pick from a list hold an answer a theme can switch on, so a section of a custom design appears on some events and not others. Use one of these rather than free text, where "Yes" on one event and "yep" on the next would show the section on one of them.

Number holds a whole number, like a capacity. Type it however you write one, and each language writes it out its own way, so 50,000 in English reads as 50.000 in German. A theme can compare it as well.

Details made before August 2026 can also be a date. They still work and still show what was typed. A date isn't offered for a new detail, and it comes out exactly as it was stored.

Defaults

A Default value is what a new event starts with. It suits a detail that rarely changes, like a support address. On a Pick from a list detail you choose it from that detail's own list.

An event inheriting a default shows an empty box with the default behind it in gray. To say something else on this event alone, type in the box. To say nothing at all on this event, untick Use the account default and leave the box empty.

Where details are set up

A detail's name, its type and its default belong to the whole account. Edit beside a detail opens that detail's own page, where you can change its name and its description, see everywhere it is used, and archive it. A change there reaches every event, and the form says so. Add a detail on an event goes to account Settings → Metadata and comes back when you save.

Under About each attendee, the detail's name is the link to the same page.

A detail's type and its short name are fixed once it exists, so the values already typed against it keep their meaning.

Archive takes a detail out of every event's list, and keeps the values already typed. Archived details have a list of their own on the same screen, each with Restore.

A detail no event has ever filled in says Delete instead, and deleting it removes it for good.

Filling in metadata about an attendee

An attendee's own Edit form has a box for each one, so you can set a value for one person at a time.

For a lot of people at once, use the attendee list's From a file import. A row with an identifier updates the attendee it matches, so an import is how you set the same detail across a whole list. The Metadata section links straight to it.

The account API can read and write these too. See the API reference.

Where a detail shows up

A detail about each attendee shows on that person's ticket when The attendee too is picked, and nowhere public otherwise. The rest of this section is about details about the event.

In a message: Insert details on the compose screen opens an Event details group. Picking one puts a chip in the message, and what goes out is whatever the detail 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 detail from the list. The order confirmation is one of the screens in the list, so a Wi-Fi password can go out with it.

A theme can read any detail as event.fields. followed by its short name. The short name is printed beside each detail. Themes are covered in the theme author's reference.

Where a detail is empty on an event, the whole line it's in is left out, so one wording can cover every event.

Details in more than one language

A Short text or Long text detail can be translated. It shows up in Translations under Event details, and attendees read it in the language they're booking in.

We already write a Number detail out to suit each language, so it needs no translation. On or off and Pick from a list hold a fixed answer a design reads, so those aren't translated either.

An event using the account default translates the words it's publishing, and stays on the default. Making a translated language the event's default moves those words into the event's own box.