Ticketmaster
Ticket data in Ticketmaster sits in reports, and it rarely becomes anything other than settlement and headcount: The road from a report to a segmented email is long enough that nobody walks it every week. The integration fetches the data itself instead, every five minutes and one way, from Ticketmaster to Heyloyalty. You can bring in guests both with and without marketing consent, so you can send newsletters, service messages or both. The ticket purchase data comes with them. Older data can be pulled in with a manual import.
What can you do with it?
-
Without the integration
The report goes to finance. It says how many tickets were sold and what has to be settled. It does not say who was also here last season, and it is not opened again when the next show has to be sold.
-
The guest who has never been to you
If she buys on ticketmaster.com, she has never seen your site, your newsletter or your name as a sender. The sales channel tells you who arrived that way, and the first email should not look like the one you send to someone who has bought from you for years. She needs to know who you are before she hears what else is on.
-
The reservation that was never paid for
A reserved ticket carries its own status, not a purchase. It is the clearest version of the thing that did not happen: Someone was almost there and stopped. A reminder before the reservation expires costs you one email and can save a seat that would otherwise stay empty.
-
The days before
The date and venue travel with every purchase. The message can therefore go out three days before the event rather than on the day the ticket was sold, which may be four months earlier. Three days before the event is when the guest needs to know where to park and when the doors open.
-
Where she sat, and what she paid for it
Section, row, level and price category come across. Someone who takes the most expensive seat every time and someone who always waits for the cheapest should not get the same offer. The ticket type says it again: Someone buying two student tickets is not the same as someone buying eight at full price.
-
The ones who bought for colleagues
Company and department travel with the purchase when the guest has given them. Someone ordering eight tickets for a department is not an audience member. She is a buyer, and she should be asked again next season, before the programme sells out.
-
The cancellation that need not be a goodbye
A cancellation stays on the record with its own status. You can see that someone held a ticket and is not coming, which is a different situation from never having bought one. An invitation to something else in the same season beats silence.
The data you work with
About the guest
- Name and email: from the consent report
- Preferred language: the guest's own choice in Ticketmaster
- Address, postcode, town and country: travel with the purchase
- Company and department: separates business buyers from private ones
- Newsletter consent, and service permission where it applies
About the ticket
- Event name, code and date: the timing of everything you send
- Venue
- Section, row, seat and level: where in the house she sat
- Price category and ticket type: full price, student or discount
- Order number and price
- Status: bought, reserved or cancelled
- Delivery method
About the sale
- Sales channel: whether the ticket was bought from you or on ticketmaster.com
- Promoter and administrator
- Time of the transaction
Requirements
- Booking system with Ticketmaster
- Premium license or higher
- An active email list and Tracking integration in Heyloyalty
Consent and GDPR
This is where Ticketmaster differs from the ticketing systems where you sell in your own name. When a guest buys, she chooses for herself whether to hear from Ticketmaster, from you, from both or from neither, and that tick decides who holds the permission. You only get the people who ticked you. In return, everyone on the list said yes actively at the moment of purchase. You decide whether buyers without marketing consent come across at all: Switch on the import of contacts for service messages and they are created with service permission only, so they can receive practical information about what they bought, but not newsletters. When a guest who is already on the list buys, their details are enriched with data from the purchase, and their newsletter permission is left alone.
It is your responsibility that the data in Ticketmaster was collected correctly and lawfully.
Setup
You need access to the Ticketmaster reports API, an API key, a market code and an API user who can read both the consent report and the sales report. Ticketmaster grants the access. In Heyloyalty you pick the list and the match field, email or mobile number, and the list needs tracking if the purchases are to come across too. One thing belongs in the calendar: The Ticketmaster API password expires every 90 days, and when it does the integration stops fetching data until the new one is saved. Heyloyalty reminds the account administrators on day 69 and again on day 83.