Skip to content
Heyloyalty
← All integrations
Billetten logo

Billetten

Ticketing and booking systems

When a guest buys a ticket through Billetten, they are created as a contact in Heyloyalty straight away. The integration runs in real time and one way, from Billetten to Heyloyalty. Guests who did not opt in to the newsletter come across too, so you decide for yourself who you want to talk to. If you set up tracking and a product feed, on-site behaviour follows: sessions, visits, add-to-basket and purchases. The behaviour is tied to the guest the first time they log in or click through to payment, and that requires them to have accepted cookies.

What can you do with it?

  • Without the integration

    Ticket sales are slow, and the email has to go out this week. Finding the people who have seen something similar takes longer than there is, so it goes to the whole list. Most of them get something that is not for them, and every time that happens, more of them unsubscribe. With the ticket purchases on the contact, that selection is a filter instead of an afternoon.

  • The basket that never became a ticket

    Tracking shows when someone put tickets in the basket and did not buy. At a venue that is rarely a no. It is a decision that was postponed because the date had to be checked with a friend. A reminder the next day lands while the show is still coming up, and it can go out automatically.

  • The ones who only said yes to their own purchase

    The Billetten checkout has two consents, and they come across separately. Some guests only agreed to information about what they bought. You can still write to them about that particular show without sending them the newsletter. They are two different conversations, and they can be kept apart from the first email.

  • What they came to see

    The ticket says which performance the guest bought for, and that is the sharpest dividing line you have. A stand-up audience and a classical audience rarely share a taste. Build the segments on the performance and you are writing to people about something they have already chosen once.

  • One ticket or seven

    Purchases arrive one line per ticket, so you can see how many tickets are on the order. Someone buying a single ticket for themselves and someone gathering seven colleagues should not get the same message. Do note that a segment on "has purchased" counts the guest once, however many lines sit behind it.

  • The show in the email, not just a link

    The product feed pulls the image, price and link for the current performances, so they can be dropped straight into a campaign or a flow. The programme does not have to be rebuilt every time, and what the email shows is what is actually on sale.

  • The ones who bought and stayed home

    If you scan tickets at the door, you can tell the guests who turned up from the ones who bought and did not come. They are two different people to write to afterwards, and the second group is the one you otherwise never hear from.

The data you work with

About the guest

  • Name and email
  • Newsletter consent: the whole programme, not just what they bought
  • Purchase information consent: the show they hold a ticket for
  • Guests with no consent at all: created, but can be segmented out

About the purchase

  • The performance on the ticket: what the guest chose, and so what they want to hear about
  • Ticket lines: one per ticket, combined into a single order behind the scenes
  • Tickets on the order: the individual guest or the whole group
  • Price: including VAT, excluding the booking fee
  • Cancellation: the line disappears again
  • Scan at the door: who actually turned up

From tracking and the product feed

  • Sessions and visits on the site
  • Add-to-basket without a purchase
  • Completed purchases
  • Performances with image, price and link

Requirements

  • Booking system with Billetten
  • Premium license or higher
  • An active email list and Tracking integration in Heyloyalty

Consent and GDPR

The Billetten checkout has two consents, and both come across as fields on the list. One is consent to emails and SMS about what the guest bought. The other is consent to newsletters in general. Guests who only accepted the terms and conditions are created as well, simply without consent fields, so you can segment them out. If a guest changes their consent inside Billetten, Heyloyalty is told through the integration.

It is your responsibility that the data in Billetten was collected correctly and lawfully.

Setup

Billetten set up the integration, so questions about the integration itself should go to Billetten. In Heyloyalty you need three things in place: a list whose name Billetten has to know, the consent fields created as text fields, and a tracking integration with a product feed, with the tracking ID passed on to Billetten. The field names can be changed afterwards, but the merge field has to stay as it is, because the integration uses it.

See our other integrations for ticketing and booking systems

See all integrations →