Skip to content

Design ticket templates

When a guest successfully registers, they receive an e-ticket with a QR code used to enter the event. The Ticket Templates page lets you decide what that ticket looks like: layout, colors, fonts, background image, and where the QR code sits. Each tier can use its own design, and you can set one default design for the whole event.

  • Create a new ticket design or edit an existing one.
  • Arrange content blocks (text, image, QR code, tier badge…) with a drag-and-drop editor.
  • Pick a font for the whole design.
  • Assign a design per tier, or set one design as the default.
  • Preview the ticket in each tier’s color before saving.

Open your event page and select the Ticket Design tab. There are three main areas:

  1. Tier list (left) — each tier with the design currently assigned to it.
  2. Tier detail (right) — edit the selected tier’s name, capacity, color, and design.
  3. Templates table (below) — every design in the event; create, edit, and delete from here.
  1. In the Ticket Design tab, scroll to the Templates table at the bottom and choose Create template.
  2. Enter a name in the top toolbar (for example, “VIP — Dark”). This name is for your own reference; guests never see it.
  3. Choose a default font for the whole design from the font picker next to the name.
  4. (Optional) Pick a tier from the dropdown to preview the design in that tier’s color. This choice only affects the on-screen preview — it does not assign the design.
  5. Build the layout by adding and arranging content blocks (see below).
  6. Click Save. The new design appears in the templates table.

The editor has three areas:

Area Purpose
Blocks (left) The block types you can add to the ticket
Preview (center) The ticket you are designing; click to select, drag to arrange
Properties (right) Edit the selected block: text, color, size…

When designing a ticket, you can add these blocks:

  • Text — free-form text (event name, thank-you note, entry instructions…).
  • Event info — automatically fills in the event name, start/end time, venue, or address. Instead of typing these by hand, you insert a placeholder and the system fills the real value per guest.
  • Image — logo, background photo, or illustration. Can be used as the ticket’s background.
  • QR code — the guest’s unique QR code for scanning at the door. You should always include this.
  • Tier badge — shows the tier name and color (for example, a “VIP” ribbon).
  • Columns layout — place blocks side by side in multiple columns.
  • Divider and Spacer — add separation and breathing room between sections.

The editor supports two ways to arrange blocks:

  • Vertical layout — blocks stack top to bottom; suited to long, strip-style tickets.
  • Free-form layout — you place each block anywhere on a background (typically a graphic background). In this mode, some blocks like the columns layout are hidden.

Switch between the two modes using the buttons in the editor toolbar.

The editor lets you preview the ticket at different sizes (desktop, laptop, phone). Guests mostly open their ticket on a phone, so check the phone view before saving.

Instead of hard-coding the event name or door time, you insert placeholders into your text. When the ticket is sent, the system replaces each placeholder with the guest’s real value. Available groups:

  • Event info — event name, start time, end time, venue, address.
  • Guest info — guest name, email, ticket tier, ticket number, and ticket/check-in links.

By default the editor works in RGB — what screens display. If your print vendor’s brand guide specifies CMYK values, you can switch the template’s color model:

  • The color-model toggle sits at the template level. Switching an RGB design to CMYK asks for a confirmation, because the colors are converted.
  • In CMYK mode, color inputs become C / M / Y / K channel fields (0–100), with an out-of-gamut warning when a color cannot be reproduced faithfully in the other model.
  • The canvas preview and the HTML export resolve the closest sRGB hex for display, while the server-side PNG rendering reads the original CMYK values — so the printed ticket matches what your vendor asked for.
  • CMYK values are validated on save, so a half-entered channel cannot slip through.

A design only takes effect once it is assigned to at least one tier. You have two options:

  • Set a default design for the whole event — any tier without its own design uses this one.
  • Assign a design to a specific tier — that tier uses its own design and ignores the default.
  1. In the tier list, click the tier you want to assign a design to.
  2. In the detail panel on the right, click Assign design (or Change design if one exists).
  3. Pick a design from the list and click Confirm.

The Default row at the top of the tier list represents the shared design. Click that row, then click Set as default (or Change default) to choose the design applied to every tier that has no design of its own.

In the templates table at the bottom:

  • Click a row (or the pencil button) to open the editor.
  • Click the trash button to delete the design.
  • Check the ticket on both a large screen and a phone.
  • Make sure the ticket always contains a QR code block — without it, door staff cannot scan guests in.
  • After you save a design, any newly issued ticket uses it. Tickets already sent are not changed automatically.

Control what guests see on the ticket page

Section titled “Control what guests see on the ticket page”

Besides the designed ticket, every guest receives a ticket link — the page they open on their phone to show the QR code at the door. The event’s Ticket Page tab controls exactly what that page shows:

  • Show ticket details — the master toggle. Turn it off and guests get a minimal QR-only view: guest name, email, phone, custom fields, companions, and guide images are redacted server-side from the public payload — they never even reach the guest’s browser.
  • Beneath the master toggle sit five per-section switches: event info, guide images, guest details, companions, and ticket actions. Each hides its section the same way — enforced at the server, not just hidden in the browser. Hiding every section equals turning the master toggle off, and the CMS warns you when you get there.

A few behaviors of the guest page worth knowing:

  • Once a ticket is scanned, the QR is covered by a “Used” state — but the guest can tap Show QR to reveal it again so door staff can re-check their information. Cancelled and expired tickets stay covered.
  • On walk-in companion events the guest’s name carries a +N party-size badge, and on count-only events the companions section collapses to the visible companion count.
  • Events spanning more than five days collapse the per-day list to the first two and last two days, with a control to expand the full list.