NaviPartner
Cash register systems and POS Ticketing and booking systems
Members are pulled from Business Central, and the purchases come with them: The ticket at the gate, the item in the shop and the order from the webshop all land on the same contact. The connection runs both ways. When a customer unsubscribes in Heyloyalty, Business Central knows straight away, and the same goes for sign-ups, updates, spam complaints and hard bounces.
What can you do with it?
-
Without the integration
An unsubscribe has to be handled in two places. If a customer unsubscribes from the newsletter, the store system does not know, and she can still receive an offer she just said no to. Here the unsubscribe comes across immediately, and so does the sign-up.
-
The annual pass or membership about to expire
The end date comes across, so the reminder can go out while the card is still valid. A membership allowed to lapse in silence is a customer you let go of yourself.
-
The one who bought a ticket and did not come
With the PTE add-on, the contact shows whether the ticket was scanned. A purchase is not a visit, and the person who stayed away should not get the same email as the one who queued up.
-
Which shop they buy in
The shop sits on the purchase as "Retail center". With several of them, the person who shops in Aarhus can hear about Aarhus, and few chains can tell that apart without someone typing it in.
-
The purchase that calls for the next one
A running test is not an end in itself, it is an opening to talk about shoes. And shoes wear out. Product and purchase date sit on the contact, so the follow-up can arrive when it is relevant rather than a week later.
-
Service message or marketing
Permission holds two values, Notification and Newsletter, and they come across separately. Someone who only said yes to the practical should get the practical, not an offer.
-
The ones who were members and stopped
Membership status tells an active member from a newsletter subscriber from a former member. The three should not get the same approach: Someone who was a member and left already knows what she turned down.
The data you work with
About the purchase
- Tickets and admission
- Items bought in the shop
- Orders from the webshop
- Product, price and date
- Which shop the purchase happened in
About the membership
- Member number and card number
- Membership type
- Membership status: active, newsletter subscriber or former
- Activation date and end date
- Permission: Notification and Newsletter separately
About the visit, if you add the PTE app
- Arrival date and time
- Time slot and valid until
- Whether the ticket was scanned
- Name of the exhibition
Requirements
- POS system with NaviPartner
- Premium license or higher
- An active email list and Tracking integration in Heyloyalty
Consent and GDPR
Permission is a field with two values, Notification and Newsletter, and they decide what the customer may receive. Both come across from Business Central. All members land on the same list, though, so separating the two groups in practice is automation flows you build and maintain yourselves over time.
It is your responsibility that the data in NaviPartner was collected correctly and lawfully.
Setup
Setup has more steps than the others, and the order matters. You need an Entra ID app in Microsoft with an API key and secret, the field mapping agreed with NaviPartner, and lists and custom fields created in Heyloyalty. Only then can the webhook be set up, because it assumes member synchronisation and Entra ID are already working. If you want scan data and time slots, the PTE app is a paid add-on from NaviPartner. And one thing belongs in the calendar: The secret in the Entra app expires, and when it does, the webhook stops.