An event's Customize opens the same full-screen studio described in Customize studio, for this one event only. Every change you make here applies to this event, and reaches people once you publish. Anything you leave alone shows the account's own defaults.

go.tito.io/acme/summer-fetes-summer-fete/admin/customize?tab=look&zoom=50

Changes waiting to be published

Changes you save in the studio stay out of sight of people until you publish. While any are waiting, the event's Overview shows a note with the number waiting, what people see meanwhile, and a way back into the studio.

Publishing clears it.

One audience's own wording

An audience can have its own wording for the people who book through its landing page. Pick the audience under Who, then on the Words tab open Change the wording for, just below the search, and choose the audience's name. Every audience is in the list, so you can move between them there.

A box in that audience's tab changes its wording only. Leave a box empty, or select the curved arrow beside it, and that audience gets everyone's wording for the line. Choose Everyone in the same list to go back to the wording everybody else gets.

Under Everyone, a box the audience has its own wording for says so, and the preview shows the audience's wording. Select Change it under the box to go to that audience's tab.

An audience can have its own wording on:

its landing page
the booking form and the claim form
the payment page
the order page and the ticket
the order confirmation and the ticket email, including the extra information on each

The email sign-off and any line that also appears on another screen read the same for everyone. Switching a line on or off applies to every audience, so those switches are under Everyone only.

Each language is separate. If you write an audience's line in English only, its buyers reading in another language get everyone's wording in their language.

Orders booked through the audience's landing page get its wording on the order page, the ticket and the emails. Every other order gets everyone's wording, including orders you add yourself, invitations, portals, quotes and sales at the door.

Point at a word on the preview and its label names the audience when the word is that audience's own.

Good to know

A control you haven't set on this event falls back to the account's value, then to the look the event is based on, then to Tito's own default. The undo arrow on a control names which of those it would go back to.
Before anything is on sale you can work on the event page and on any widget you've made. The buying screens appear once a ticket type goes on sale.
An event set to Asks for a ticket under How they book shows the screens somebody asking goes through. Its event page is still there to work on, under Booking.

Change the design through the API

The account API can read and edit this event's design tokens, including its look_base. Those edits wait in the same draft as changes made here. Publishing or discarding through the API acts on the whole event draft, including any wording, content or widgets waiting in the studio. Publishing with no draft leaves the public pages unchanged.

The event stylesheet has its own /events/{slug}/design/css route. Saving it changes the same draft as the other design controls.

/events/{slug}/design/wording takes audience, an audience's slug, to read and change that audience's own wording. The lines it accepts have per_audience set.

API changes are draft until published.