Heyloyalty · mail

Heyloyalty integration: flows triggered by your system

A Heyloyalty integration means your system pushes events and fields to Heyloyalty, so newsletters and automation run on real data: purchased, cancelled, expires in 7 days, has not opened in 90 days. Heyloyalty is a Danish marketing-automation tool. It is not HubSpot. It should not try to be. If you already have lists and flows there, do not move them to an international tool in the middle of a development project. Send purchase, booking, cancelled subscription and inactive member. Do not send every mouse move. Consent lives in one place as master. Unsubscribe must work. A B2B contact on a CVR is still a person when you write to a named inbox.

Heyloyalty or HubSpot? If you already have Heyloyalty and only need mail and SMS flows: keep it. If the whole inbound machine lives in HubSpot: integrate HubSpot.

Events
payment.capturedok
invoice.bookedok
click.paidignore
Event in your app. Flow in Heyloyalty. Not a nightly CSV.

Events in a Heyloyalty integration

  • Purchase or booking completed
  • Subscription cancelled
  • Member inactive
  • Tracking sent — not “packed” if the customer is only happy at delivery

Send

  • Purchase, booking, cancelled, expiring, inactive
  • Fields you actually segment on
  • Consent status from the master

Do not send

  • Every mouse move
  • Every draft and internal note
  • Heyloyalty is not your audit log
Heyloyalty is the mail layer. HubSpot is the inbound machine. Pick what you already have.
HeyloyaltyHubSpot
Danish mail layer versus international inbound. Do not move mid-project.

GDPR: one consent master

Consent lives in your system or in Heyloyalty — one place. Unsubscribe must work. A B2B contact on a CVR is still a person when you write to a named inbox. Automation.

Events to Heyloyalty are 1 integration in a package from 18,000 DKK + 600 DKK/month. The Heyloyalty subscription is theirs. We build the trigger.

Heyloyalty is not your audit log

Write the 4–6 events you want to trigger, and where consent lives. Then we can give a fixed price within 24 hours instead of syncing “everything”. Describe the flows · Pricing.

FAQ: Heyloyalty integration

Heyloyalty or HubSpot?

If you already have Heyloyalty and only need mail and SMS flows: keep it. If the whole inbound machine lives in HubSpot: integrate HubSpot.

May we dump the list every night?

That is what you have now. An integration pushes events when something changes — otherwise the wrong flow starts.

Who is master for unsubscribe?

One place. Your system or Heyloyalty. Two masters means you write to people who said no.

Is a CVR email exempt from GDPR?

A named person at the other end is still a person. Unsubscribe and consent still apply.

Should we send “packed” or “shipped”?

The moment the customer is actually happy. Tracking sent beats “packed” if you promise delivery.