How-to · Your website
You have a site you like, on your own CMS or a site builder, and you want people to buy tickets there instead of being sent somewhere else. A plugin may not exist for your system, or may not suit the way you work. Below: the options for adding tickets to pages you already have, what to check before you commit, and a setup that leaves your site as it is.
The advice holds whichever ticketing service you pick. Here, the checkout and RSVPs for your own site are part of every plan, including Free.
The options
The quickest: a Buy button that sends people to a page on the ticketing service. It works anywhere, but buyers leave your site, and some never come back to it.
Good when one exists for your system and does what you need. Ask who keeps it updated, what happens to past orders if you drop it, and whether it survives your next CMS upgrade.
Add one script, and a button opens the service’s checkout on top of your page, or the form sits right in it. Nobody is sent away, and payments, ticket emails and the door are handled for you.
Full control, written by your developer on a payment processor. You also take on taxes, refunds, ticket emails, QR codes, scanning and fraud, a lot to maintain for a few events a year.
Before you choose
Anyone can change the HTML of a web page in their own browser. A price written in your page must never be what gets charged: it should come from the service’s records, or from a message your server signs.
The first price a buyer sees should already include every fee. Totals that jump during checkout lose sales, and in parts of North America the law now requires the full price for event tickets.
Most buyers arrive from social media on a phone. Try the checkout on yours, with Apple Pay or Google Pay, before you decide.
Someone who bought on a laptop will reach for their phone at the door. Make sure they can find their tickets again without creating an account or remembering a password.
Names and emails of the people who bought should be yours to download, and yours to invite to the next event.
A checkout any site can load could be copied onto a stranger’s page. The service should let only the addresses you list show your tickets.
On EventsMagic
In Website Embeds, pick the organizer page it sells for, list the sites that may show it (localhost too, while your developer works), and choose a look: each event’s own theme, or light or dark with your colours, a Google Font and the corners you like.
Copy one script tag into every page that sells. Many systems have a site-wide place for code like this, in the header or footer settings.
Copy an event’s Get tickets button, and My orders beside it, into its page, or RSVP and My RSVP when the event is free. They are plain HTML of yours, so style them like any other button you have, and word them in your language.
Buy one ticket yourself on your phone, scan it the way your door staff will, then refund it from your dashboard.
Design
The checkout drawer takes your colours, a Google Font and your corner style, so it reads as one more piece of your page.
Upcoming or past events arrive as HTML inside your page, where your stylesheet takes over. Start from our plain cards, or write a template of your own.
Every card offers what its event takes, Get tickets while it sells or RSVP while it takes replies, with My orders or My RSVP at all times, and carries a state for your CSS: open, closed, ended or cancelled.
Labels, the empty list, the message while the checkout opens and errors can all use your words, and dates follow your page’s language and the event’s time zone.
Rather than a drawer over the page, the checkout or any other form can sit in a box of yours, as wide as that box and as tall as the form, growing as people fill it in.
Some site builders remove scripts but accept an iframe. Then a plain frame shows the same form at a fixed height, scrolling inside, and the loader script isn’t needed.
For your developer
If your CMS already holds your events, your server can describe each one, with its tickets and prices, and the first Get tickets press creates it here. No setup in our dashboard.
Your server signs every event with your secret (HMAC-SHA256). A page edited in a browser can’t change a price, and an old signature can’t bring an old price back.
A newer signature updates the title and tickets for future sales. Paid orders stay as they were, and a ticket you leave out stops selling rather than disappearing.
Set the events up in our dashboard and point each button at one by its key. Prices then live in the dashboard, which suits most site builders.
Beyond tickets
RSVP and My RSVP open the same form as your event page here: your questions, the guest limit, approvals, the waitlist and the emails. On every plan, like the checkout.
A Volunteer button opens sign-up for your shifts, and My volunteering lets people see theirs. A list of open shifts can sit on the page as well. With Pro.
A sponsor button offers sponsorships and a vendor button stalls and booths; a third covers any other role, and each can be narrowed to the kinds you name. The packages can appear as a list, beside the sponsors and vendors already approved. With Business.
Give and Become a member open your organization’s causes and memberships rather than one event’s. A list can show them too, with each cause’s total so far only when you switch it on. With Business.
I lost something, I found something and What I reported open the same forms as your event page, following the settings you chose for that event. With Pro.
Every shift, package, cause and membership ends its edit screen with its own code to copy, which opens it straight away. Leave a button unnamed and people pick from what is open.
Questions
It works on any site that lets you put your own HTML and a script tag on the page itself, so no plugin is needed. Site builders often allow that on some of their plans only, so check yours first. If yours removes scripts but takes an iframe, the plain frame still works.
No. The checkout slides in over your page, and closing it puts them back where they were, on the button they pressed. Or place it inside the page, where it grows with the form.
No. They pay by card, Apple Pay or Google Pay and get their tickets by email. On a different device, My orders finds them with a code sent to that address.
Yes, when the event is set up here to take replies. RSVP opens your questions, limits, approvals and waitlist over your page, and My RSVP brings a guest’s reply back later, on another device through a code sent to their email or phone. An invitation-only event offers My RSVP alone, since replying needs each guest’s own link.
Exactly what selling from an event page here costs: no monthly price on Free, and a fee on each online order. Today’s figures are on our pricing page.
Yes. Choose upcoming or past, one channel if you group your events, and how many show at a time; Load more brings in the rest.
They can copy the code, but nothing opens there. Only the websites listed on your embed can show it, and the browser refuses the others.
Your site, our checkout
On EventsMagic, one script tag brings a Get tickets button, and My orders for returning buyers, to the pages you already have, in your colours, taking card, Apple Pay and Google Pay. Guests reply to free events there as well. Your door team uses their own phones to scan, and Free has all of it.