JCD
Ticketing and booking systems Cash register systems and POS
The figures from JCD are already pulled out of Business Central today, but they end up in a finance dashboard and marketing never sees them. The integration sends them into Heyloyalty instead, one way and without writing anything back: Purchases from the till and from the webshop land as orders on the contact with every line item, and the membership list syncs roughly every twenty minutes with the active cardholders. The newsletter list receives sign-ups with the details available at the moment they sign up.
What can you do with it?
-
Without the integration
The same family buys single tickets three times in a season, and nobody suggests the season pass. A season pass that expires is something you notice when the guest stops coming back, and by then a season has gone. Both sit in the till, and both need someone to go looking.
-
The purchase at the till, not just in the webshop
JCD is both till and webshop, so what sells across the counter lands on the same contact as what is bought online. It does require the customer to be identifiable at the till, and that is what the card is for. Without it, a purchase in the shop is just a receipt.
-
What was in the basket, not just what it cost
Every line item comes across: product, quantity and price. You can see that someone bought two bottles of the same wine, or an annual pass and food for four. That is the difference between "has spent 800 kroner" and "has bought something you can follow up on".
-
The ones who only buy on offer
Both the list price and the price paid come with each line. You can separate the person who always waits for a discount from the one who pays full price. Those two should not get the same email, and one of them may not need the discount at all.
-
The basket that was emptied again
Tracking reports both when something goes into the basket and when it comes back out. An item removed just before payment is a hesitation you would otherwise never hear about.
-
The card about to expire
The expiry date sits on the contact, so the reminder can go out while the card is still valid. It has to: When the card expires the fields are cleared, unless the setting to keep them is switched on. Wait until afterwards and the data is gone exactly where you needed it.
-
The ones who have not been here in a while
The date of the last visit comes across. For a park that is months ago, for a shop it is weeks. Either is an occasion, and it is more concrete than "we miss you".
The data you work with
About the purchase
- Order number and time
- Line items: which product and how many
- List price and price paid: whether a discount was given
- Purchases from the till and the webshop on the same contact
About the card and the customer
- Card expiry date: when the reminder should go out
- Last visit date: how long since they were here
- Number of periods: how long they have been cardholders
- Card type as tags: which kind of card they hold
- Name, mobile, postcode, town, country and date of birth
From the webshop
- Visits to individual pages
- Items added to the basket
- Items taken back out of the basket
- Completed purchases
- Product feed with id, title and price
Requirements
- Booking system with JCD
- Premium license or higher
- An active email list and Tracking integration in Heyloyalty
Consent and GDPR
Tracking only reports events once the visitor has given consent. That covers page visits, items added to the basket and completed purchases alike. Sales data from Business Central is only sent when an email address can be found for the customer, so an anonymous purchase at the till never arrives. The newsletter list and the membership list are kept apart, so you control who may receive marketing and who you simply hold as a cardholder.
It is your responsibility that the data in JCD was collected correctly and lawfully.
Setup
JCD activate and configure the integration, so you contact them to get started. Note that JCD charge a monthly fee for the integration; the price comes from them, not from us. In Heyloyalty you need two lists with identical field setups, one for the newsletter and one for the members, and the webshop needs your API key and tracking ID. Questions the guide does not answer go to our support.