See the field mapping for United Tickets

Here you can see which fields the United Tickets integration fills in Heyloyalty, and where the data comes from in United Tickets. Use the overview when you need to find the field a segment or a flow should be based on, for example the event’s start time or whether the buyer showed up.

The fields are prefilled on the setup page, and a field mapping you leave empty is not transferred to Heyloyalty. You can read how to set up the integration in Set up the United Tickets integration.

Contact field mapping

Under Contact field mapping, the buyer in United Tickets is connected with the standard fields on your list. The mapping is prefilled for the fields that exist on the list. Contacts are matched on email or mobile number, and a buyer without a value in the field you match on is skipped. The field you match on cannot be changed in the mapping.

Field on the list	United Tickets customer field	Content
email	email	The buyer’s email address. Can be used to match contacts.
mobile	mobile	The buyer’s phone number with digits only. Can be used to match contacts.
firstname	firstName	First name.
lastname	lastName	Last name.
address	address.line1	First address line.
postalcode	address.postCode	Postal code.
city	address.town	City.
country	address.countryIso	The country’s ISO code. Stored as text.

Permission fields

The integration creates two Yes/No fields on the list when you save it. They are shown under Buyers on the setup page and are marked Created on save until they exist on the list.

Field on the list	Content
Newsletter Permission (newsletter_permission)	Yes for buyers who gave consent under the chosen consent questions. The integration never sets the field back to No.
Service Permission (service_permission)	Yes for buyers created without consent. Only used when Create buyers without consent is set to Yes.

Ticket fields

Under Ticket fields are the fields every order line sends to the list’s tracking. The fields are fixed. Every order line is its own purchase with the event as the product, and the contact is found through the field you match on. The fields from order_id and down are marked Custom field and are created in the tracking when you save the integration.

Tracking field	Content
order_number	The order id and the line id separated by a hyphen. Every order line is its own purchase.
product_id	The event id, for example DF-1234567.
product_name	The event name.
amount	Number of tickets on the line.
product_price	Price per ticket including the booking fee.
currency	Currency, for example DKK.
created_at	When the tickets were booked.
category_name	The event’s categories separated by commas.
email	The buyer’s email, when contacts are matched on email.
phone	The buyer’s phone number, when contacts are matched on mobile number.
event_type	bought for purchases and cancelled for cancelled order lines.
order_id	The order id in United Tickets. Locked field in the tracking.
event_start	When the event starts. Date field.
event_end	When the event ends, if United Tickets has it. Date field.
doors_open	When the doors open. Date field.
venue_name	Venue.
venue_town	Town of the venue.
promoter_id	The promoter’s id.
promoter_name	Promoter.
artist_names	Artists separated by commas, or the tour name when there are no artists.
tour_name	Tour name.
ticket_type	Ticket type.
face_value	The ticket’s face value rounded to a whole number. Number field.
block	Block, for seated events.
row	Row, for seated events.
seat	Seat, for seated events. If the line has several tickets, the seats are separated by commas.
offer_code	The offer code the buyer used.
selected_postage	Delivery, for example E-Ticket.
lead_time_days	Number of days from booking to the event. Number field.
tickets_cancelled	Number of cancelled tickets on the line. Number field.
cancelled_at	When the line was cancelled. Date field.
attended	Yes when a ticket on the line has been scanned. No when the attendance is finalised and no ticket was scanned. Empty if the token cannot read scans.
tickets_scanned	Number of scanned tickets on the line. Number field.
first_scanned_at	The time of the first scan. Date field.

Very long texts are shortened so the purchase can be stored. If an order line is still too long, the artists, tour name and seats are left out.

Note: attended, tickets_scanned and first_scanned_at are filled in after the event from the scans. attended only gets the value No when the attendance is finalised during the nightly reconciliation, a day after the event has ended. Read more under Attendance.

The United Tickets events product feed

The product feed United Tickets events is created when you save the integration. It holds your events that start today or later, except events from promoters you have set to Left out.

Field in the feed	Content
productId	The event id.
name	The event name.
description	Tour name and venue.
imageUrl	Link to the event image.
url	Link to the event, built from Event link. Empty if that field is empty.
salePrice	The lowest ticket price for sales on the web. If there is none, the lowest face value.
currency	Currency.
inStock	Whether there are tickets left.
categoryName	The event’s categories separated by commas.
EventStart	When the event starts.
DoorsOpen	When the doors open.
VenueName	Venue.
VenueTown	Town of the venue.
PromoterName	Promoter.
TourName	Tour name.
TicketsRemaining	Number of tickets left.

Use the fields in Heyloyalty

Now you know where data from United Tickets lands in Heyloyalty. The ticket fields show who bought a ticket for which event, when the event is, and whether the buyer showed up. Newsletter Permission shows who said yes to your newsletter in the checkout. Build your segments and flows on these fields, for example an email about doors opening to those who bought a ticket for Friday’s concert, or a follow-up to those where attended is No. See examples and the full setup in Set up the United Tickets integration.