Ticketmaster integration

In this guide, you’ll get an overview of the Ticketmaster integration in Heyloyalty – including the overview, the value, and the opportunities the integration provides. In addition, it covers setup and technical details. The purpose of the integration is to make it possible to work data-driven with your Ticketmaster buyers and actively use ticket and purchase data in email marketing and marketing automation.

What value does the Ticketmaster integration provide?

Styrk loyalitet med dine køber
Med Heyloyaltys integration mellem Ticketmaster og Heyloyalty kan arrangører og venues opbygge stærkere relationer til deres publikum. Ved at kombinere billetdata med marketing automation og personlige beskeder kan du engagere dine modtager.

Improved communication
By sending timely and relevant messages based on purchase data from Ticketmaster, you can improve the overall experience for your recipients. This could be practical information before events, follow-up after concerts, or personal recommendations for upcoming events based on previous purchases.

Targeted and personal communication
The integration’s advanced segmentation capabilities make it possible to communicate in a targeted way to specific segments. You can customize your messages based on purchase history, location, engagement, and preferences – ensuring that communication feels relevant and personal.

Increased ticket sales and repeat purchases
By using automated flows and personalized campaigns, you can activate your recipients at the right times. This could be early access to ticket sales, exclusive offers, or reminders about events that match the recipient’s interests – all with the purpose of increasing conversion and repeat purchases.

Streamlined marketing processes
Automation of communication based on Ticketmaster data saves time and resources in marketing work. At the same time, it ensures a more consistent and data-driven effort, where relevant messages…

Setup options with the Ticketmaster integration

With the integration activated, you can easily set up automations targeting customers when they purchase or book events.

Examples of automations

These are just examples of automations that can be set up:

• Welcome flow
• Updated master data (profile details)
• Has purchased
• Has booked more than X times within Y period
• Has booked more than X tickets in the same order
• When a ticket is scanned (depends on when this becomes available to us; we retrieve data continuously)
• Has booked an event
• Has booked an event with dining
• Has booked an event without dining
• Has booked an event, then added dining in a new order

Examples of segmentation options

For campaigns and automations, you can segment on all the data retrieved from the integration. If you have added additional fields for mapping yourself, these are naturally also available:

• Booked a specific event
• Booked on a specific date
• Booked for an aggregated total amount over Y period
• Has booked online
• Has booked X tickets for one event
• Has booked X tickets over Y period
• Has booked a specific zone, seat, row

Whis are just examples of segmentation and automations that can be built with the Ticketmaster integration.

Integration specifications

In this section, you get a better understanding of how the various functions work in the integration.

After setting up the integration, it will run continuously:

• Data is retrieved from Ticketmaster automatically every 5 minutes
• Both member and order data are checked
• The integration retrieves members and order data.
• We don’t retrieve a product feed from Ticketmaster, so you need to provide this yourself

In the integration, we retrieve data from the endpoints below:

• Members/consent API endpoint
• Events endpoint

You can see which fields are mapped in the integrationen here.

It’s possible to add or remove mapping fields (fields from which data is retrieved) in the integration. As long as it’s from the above endpoints.

Members and permissions

In the integration, you can choose whether you want to retrieve everyone who has made a purchase or only those who have agreed to the newsletter.

Permission is divided as follows in the integration:

• The integration should only retrieve those who have agreed to the newsletter. Here, the Newsletter Permission permission field is set to yes on the member.
• The integration should also retrieve all contacts who have made a purchase, so that you can send service messages in connection with their purchase. Here, the permission field Service Permission is set to yes for those members.

Both permission fields will be created in the list regardless of which contacts you choose to import into Heyloyalty.

Purchase data

We retrieve all purchases made in Ticketmaster into Heyloyalty, and they can be found in our Activity feed.

Field mapping

On the integration page, there are fields marked with light gray under field mapping. These fields will not be mapped over to Heyloyalty.

You can see which fields are mapped in the integrationen here.

Setting up the Ticketmaster integration

To add the Ticketmaster integration, you need an account with either a Premium or Premium+ license. In addition, you must have both an active list and a connected tracking integration. Read here how to set up a list and how to set up a tracking integration. If you already had a Heyloyalty account before setting up Ticketmaster, we recommend creating a new list and tracking integration specifically for Ticketmaster. That way, you ensure that any history from an existing list is preserved.

When you are ready to create the Ticketmaster integration, go to List integrations, find Ticketmaster, and select Set up integration. If this is your very first Ticketmaster integration, the page will look like this:

Here you will enter the integration page, which contains many different settings. At a minimum, you must configure the settings to retrieve members and products:

Under Settings, you need to configure the following:

1. List:
   Select the list in Heyloyalty that you want your Ticketmaster members to be sent to.
2. Match members by field:
   Choose which field members should be identified by (email or mobile).
3. API key:
   Provides access to your Ticketmaster solution*.
4. Market code:
   The market code you use in Ticketmaster*.
5. Username:
   Username for your API key*.
6. Password:
   Password for your API key*.
7. Retrieve contacts for service messages: If you set this to yes, you retrieve contacts who have agreed to service messages.

Note: You must contact Tickemaster to get your API information and user info. If you have a permanent consultant, you can contact them; otherwise, you can contact Ticketmaster support.  
Once the integration is set up, every five minutes we will retrieve contacts who have agreed to < 0 >consent< 0 >by< 0 >Ticketmaster.

Finally, press save. The integration will then retrieve new contacts every five minutes and insert the permissions that you have set up in the integration.

Initial import

Once the integration is set up, you can retrieve retroactive data. You do this from the overview page, where you click on the three dots (•••) next to the selected integration. Then choose “Get data from Ticketmaster”:

When you open the import modal, you will see 6 options. These can override the general integration settings for an initial/manual import:

• Date range:
  From and to date you want to import data for (you can fetch up to one year back at a time).
• Get order data:
  Whether you want to import tracking data for orders in the selected period.
• Get members:
  Whether you want to import member data this time.
• How to handle previously unsubscribed members:
  If members in the import have previously unsubscribed, you can choose whether they should be created again.
• Trigger opt-ins:
  Whether members must confirm their subscription via a confirmation email before being created on the list.
• Send automations:
  If you want to send welcome emails and automations directly related to the member sign-up, field updates, etc., set this to Yes.

Note:  When you perform a manual import, you can only import one year at a time.  If you choose to perform a manual import for a longer period, you should expect the import to take 1-2 hours. However, you will continuously be able to see if data is coming into Heyloyalty.

To get confirmation that data from Ticketmaster is being retrieved into Heyloyalty, you can under the menu item Lists, see if contacts have been added to your list. Additionally, you can under the menu item statistics under activity feed, see if various events have been added to the list.

When an automatic and manual import is run, the following fields will be created. These fields are required, and if you remove one of the fields, they will automatically be created again during an automatic or manual import:

customer_id
preferred_language
company
department
Postal code
newsletter permission
service permission
First name
Last name
Address
City
Country

Advanced setup and customization

Advanced settings

On the integration page, you can configure advanced settings for your integration. For example, if you have additional requirements for the recurring member import that runs every five minutes, you can configure them under Import settings. Here you can control how member creation and updates should work:

You can find an explanation of the different settings here:

• Import type:
  Choose how contacts from Ticketmaster should be created in Heyloyalty.

• Date format:
  If you need a different date format, you can change it here. The format shown matches what Ticketmaster provides by default.

• Sign to distinguish choices:
  Defines how your data is structured. If you have indentation (arrays), you can retrieve nested data by using a dot or similar. Example: cards { Cardnumber: 1234, Cardname: Pension}. In this case, you can map the fields below using a dot: cards.Cardnumber. This will fetch the card number.

• Avoid subscribing currently unsubscribed members:
  By default, members are created if they do not already exist on the list. If you do not want members who previously unsubscribed from your list to be created again, change this option to No.

• Send active automations:
  If you want automations (welcome emails) to be sent when a member is created on the list, set this to Yes.

• Send webhooks:
  If you want creation and updates from Ticketmaster to trigger a webhook, enable this here (relevant if you have a CRM system or similar you want to notify). If you choose No, Heyloyalty will not send webhooks when we receive data from Ticketmaster.
• Send import error report to:
  Sends an error email to you including a list of members if the Ticketmaster import fails.

Field mapping

By default, we map several fields for customers and ticket purchases. You can see the field mapping at the bottom of the integration page. If there are fields you don’t use, or that are not active on your list or tracking setup, you can remove them in Heyloyalty’s field mapping.

• Mapping for Customer: We retrieve member data from “Customers” in Ticketmaster. These fields will be available on the list in Heyloyalty.

• Tracking mapping: We retrieve tracking data from Tickets in Ticketmaster, which includes all purchase events related to Ticketmaster and ticket information. Data can be found in the Activity feed under Statistics.

If you want to add more data fields than those already mapped on the integration page, you must first make sure the data exists in the Ticketmaster API endpoints before it can be mapped in Heyloyalty. These extra data fields can then be linked in the fields shown under field mapping on the integration page.

Note: If changes are made to the data available in the API, you must update the mapping once the changes are implemented in the API. If you want to see the changes immediately, remember to run a manual import after you have mapped in Heyloyalty.

Summary of the Ticketmaster integration

You now have the foundation of your Ticketmaster integration in place. A list has been created containing all Ticketmaster members you are allowed to send newsletters to. In addition, we track purchase data for members who buy through Ticketmaster. This means you are ready to send campaigns to your subscribers! Here you can read how to set up a campaign.

Remember that you can create segments, so your campaigns are targeted specifically at your Ticketmaster subscribers. As a bonus, you can also build an automation flow that automatically sends emails based on Ticketmaster purchases—completely without manual work.

Didn’t find what you were looking for? You are always welcome to contact our support at support@heyloyalty.com—we’re ready to help.

---