The attendee popup and its designer

The attendee popup is the form a shopper fills in after clicking Add to cart on an event. It gives every ticket a name and an email before checkout. You design how it looks in the app's Popup editor.

Switch it on in your theme

The popup runs from an app embed called Easy Tickets Popup. An app embed is a switch in your theme, so there is nothing to drag into a template.

1. In the app, open the setup guide on the home page (or Settings > Setup guide).
2. On the step "Add the ticket popup to your online store", click Open theme editor. The theme editor opens with the embed already switched on.
3. Check that Easy Tickets Popup is on under App embeds, then click Save.

You can also get there yourself: Online Store > Themes > Customize > App embeds.

If the embed is off while an event uses the popup, the event's Attendee information tab warns you. Its Enable in theme editor button opens the App embeds panel. Without the embed, the theme's own Add to cart sells the ticket without asking anything. Every ticket then gets the buyer's name and email from the order.

Which events use the popup

Each event has a When to collect attendee info setting on Event settings > Attendee information. It saves as soon as you pick.

• "On add to cart - show a popup on the storefront" is the default for new events.
• "From order - use name and email from the Shopify order" skips the popup. Every ticket gets the buyer's details from the order.

Free registration always uses the popup, even on an event set to "From order".

When the popup opens

1. On a recurring event, the shopper first picks a date and time on the product page. The popup has no date picker of its own.
2. The shopper picks a ticket type and a quantity, then clicks Add to cart.
3. The app checks the date, the ticket type, any required product-page add-ons and your per-order limit. Then the popup opens.

What the popup asks

From top to bottom, the built-in popup shows:

• The title "Attendee information" and your description, if you wrote one.
• A "Tickets" stepper, so the shopper can change the quantity inside the popup.
• One section per ticket with "First name", "Last name" and "Email", plus "Phone" if you switched it on and your custom questions.
• The "Ticket delivery" choice, when the event lets the customer choose and more than one ticket is booked.
• Add-on groups and refund protection that you set to show in the popup.
• The buttons "Cancel" and "Add to cart".

The number of sections is the quantity times the ticket type's group size. A table-of-6 ticket bought twice asks for 12 guests. A bundle ticket asks for one name per pack, and the other guests claim their tickets later by link.

Changing the stepper adds or removes sections and keeps what was already typed. The stepper stops at the lowest of 50, your per-order limit and the tickets left.

Required fields must be filled before the tickets go into the cart. The questions themselves are set up on the Attendee information tab, as explained in attendee details and custom questions.

One name for the whole booking

Let shoppers book all tickets under one name is a switch on the event's Attendee information tab. It is on by default.

When the booking covers more than one ticket, the popup then shows the tick box "Book all tickets under one name", unticked. If the shopper ticks it, only the first ticket's form stays. Every ticket gets that name, email, phone and answers, and every ticket is sent to that one email address.

Each ticket still gets its own QR code. Switch the setting off if you need every guest's name.

A second switch appears when the event sells per-attendee add-ons or refund protection: Ask for add-ons per ticket when booking under one name. It is off by default, so the first ticket's add-ons go on every ticket. Switched on, the popup still asks for the add-ons of each ticket under "Choose the options for each ticket".

Buy it now and express checkout

On events that use the popup, the app hides the theme's Buy it now and express checkout buttons on the product page. That includes Shop Pay, Apple Pay and Google Pay. That way nobody skips the questions. If the app's script never starts, the buttons come back after 10 seconds, so the page always has a way to buy.

To offer a quick path anyway, go to the Buy now button section on the Attendee information tab and switch on Show Buy now button. The app adds its own button next to Add to cart. It opens the popup, adds the tickets and goes straight to checkout. Buy now button text sets its label. Left blank, it reads "Buy it now" in your store's language; reword that phrase under Settings > Storefront text.

The Button text section on the same tab sets the product page's Add to cart and Join the Waitlist labels. Left blank, the buttons read the app's own "Add to cart" and "Join the Waitlist" in the store's language. A store language the app has no wording for keeps the theme's Add to cart text.

In "From order" mode nothing is hidden, and the Buy now switch has no effect.

After add to cart

Once the popup has added the tickets, your store does one of four things. You pick it under After add to cart on any event's Attendee information tab, and the choice applies to every event in the store.

• "Refresh the page"
• "Open the theme's cart drawer (recommended)", the default for new installs
• "Stay on the page and show a confirmation", which shows "Added to cart" for 4 seconds
• "Go to the cart page"

The cart drawer works on Dawn-family, Horizon and Motion or Archetype-family themes. On other themes, and on themes with no drawer, the page refreshes instead. The app's own Buy now button always goes straight to checkout.

Design the popup in the Popup editor

1. Open the event and go to Event settings > Attendee information.
2. In the Storefront popup section, click Customize on the Attendee popup card. The Popup template editor opens.
3. Pick Attendee popup or Waitlist popup at the top. In attendee mode, Attendees 1, 2 or 3 previews several ticket forms.
4. Click a block to edit it, drag blocks to reorder them, then click Save in the admin save bar.

The popup has four blocks. Add block adds Text, Image or Columns blocks to them.

• Header: Title, default "Attendee information".
• Description: empty by default, and hidden while empty.
• Attendee Form: Section heading (default "Attendee details") and the field layout. Drag fields to reorder them, and set each to 100%, 50% or 25% width to put fields side by side on desktop.
• Buttons: Submit button text (default "Add to cart") and Cancel button text (default "Cancel").

The editor has 16 style controls, 11 under Style and 5 under Calendar (date picker):

Section	Control	Default
Style	Accent / button color	#18181b
Style	Button text color	#ffffff
Style	Modal background	#ffffff
Style	Overlay color	#000000
Style	Overlay opacity	0.45 (0 is see-through, 1 is solid)
Style	Text color	#1a1a1a
Style	Secondary text	#71717a
Style	Input border	#d4d4d8
Style	Modal border radius	14 px (0 to 32)
Style	Input border radius	8 px (0 to 20)
Style	Font family	System Default, Arial, Georgia, Verdana or Courier
Calendar (date picker)	Event day background	#f4f4f5
Calendar (date picker)	Selected day background	The accent color
Calendar (date picker)	Selected day text	#ffffff
Calendar (date picker)	Slot border color	#e1e3e5
Calendar (date picker)	Calendar border radius	14 px (0 to 24)

The accent and calendar colors also style the date picker, the delivery choice, the add-ons and the Ticket selector on the product page. The theme editor has no popup styling, and design themes never change the popup. Reset to default, under Style, puts the standard popup back after you confirm.

The design belongs to one event, and duplicating the event copies it. On a recurring event, a save on the series reaches the dates that have not started and still follow it.

Your own HTML

Actions > Edit code on the Attendee popup card replaces the popup with your own HTML. A code popup reads the first ticket's answers only. It draws no stepper, no "Book all tickets under one name", and no add-ons or refund protection. On a multi-ticket order, the other tickets get the buyer's details from the order. Saving in the visual editor later throws the custom HTML away.

The waitlist popup

Switch the editor to Waitlist popup to design the form a sold-out event shows. It uses the same style controls and has these texts:

• Waitlist header, default "Join the Waitlist"
• Waitlist description, the sold-out explanation
• Waitlist submit text, default "Join waitlist"
• Success title, default "You're on the list!"
• Success message, default "We'll let you know when tickets become available."

The waitlist popup has no code editor. How signups and emails work is covered in waitlist for sold-out events and dates.

The popup in other languages

The popup's built-in wording ships in English, Spanish, French, German, Portuguese and Danish. Texts you left at their defaults show in your default customer language. Texts you changed show as you typed them until you translate them.

With customer languages switched on, each shopper sees the popup in the language they shop in. The Translate button in the Popup template editor holds your own texts per language; it shows once your store sells in more than one language. Built-in phrases can be reworded per language under Settings > Storefront text.

Limits

• The form is always a popup. There is no inline form on the product page.
• There is no date or time picker inside the popup. Dates are picked on the product page first.
• Required answers are checked in the shopper's browser only.
• If the shopper changes the quantity later in the cart, the saved answers stay as they were. Extra tickets get the buyer's details from the order.
• On an event page the popup takes over every add-to-cart button, quick-add buttons for related products included. Clicking one of those opens the ticket popup and adds the ticket instead of the related product.
• The attendee popup has no success screen. What follows is your After add to cart choice.

See also

• Storefront blocks: what each one does