HeyLoyalty integration

Connect HeyLoyalty, create member fields, enable optional webshop tracking and check purchases, subscriptions, consent and historical imports.

Use HeyLoyalty to build audiences and send marketing with customer, purchase, attendance, season ticket and ticket subscription information from eventii. Optional tracking adds webshop activity.

Choose one of Klaviyo or HeyLoyalty; eventii Automation can run next to either. EventManager prevents Klaviyo and HeyLoyalty from being configured together. See the Marketing integrations overview for setup responsibilities.

Prepare the list and access

Agree which HeyLoyalty list the club will use. Obtain the provider credential pair, API URL and list reference through your approved setup process. Do not put these values in support screenshots or public documents.

You need EventManager permission to manage marketing integrations to test, save, create member fields or remove configuration. Permission to view integrations does not grant management access. Ask eventii support to confirm service availability if the integration screen is unavailable.

Connect and create member fields

  1. Open Administration → Integrationer and find the HeyLoyalty card.
  2. Complete API-nøgle, API-hemmelighed, API-URL and Liste-ID using the agreed list details.
  3. Select Test forbindelse and review the result. This tests the connection; it does not save the form or prove that customer updates are arriving.
  4. Select Gem separately and confirm that saving succeeds.
  5. Open the card's Handlinger menu and select Opret medlemsfelter. This prepares the fields used by eventii on the list.

If existing fields have incompatible types, preserve the error and ask support to resolve the list setup before relying on those fields. Do not treat a successful connection test as validation of every field.

Medlemsfelter er delvist klar can mean purchased-match choices are deferred until a qualifying match-ticket purchase supplies the first value. It does not mean that every other field failed. Review the result and check the purchased-match field after a qualifying purchase.

Enable optional webshop tracking

Connecting the member list alone does not enable tracking. On Integrationer, open Avanceret konfiguration → HeyLoyalty sporing, select Rediger, enter the provider's tracking reference in Tracking Id, then select Gem. Confirm the reference with the person responsible for the club's HeyLoyalty setup. Tracking also needs the saved HeyLoyalty connection.

Tracking sends email, product or order references, quantities and available prices. It records product visits, basket additions and removals, and paid or cancelled orders. Missing tracking configuration skips sending. Activity needs a usable email; paid-order tracking omits kiosk orders and orders without eligible products. Cancellation tracking can contain an empty product list. Product visits do not carry a price.

eventii does not send phone or mobile numbers to these marketing platforms. Tracking does not grant marketing consent.

Verify the first updates

Use an agreed test customer and a controlled purchase with support. Check the intended HeyLoyalty member for updated customer details, purchase date and qualifying purchased-match selection. If tracking is enabled, verify that activity separately. Record the action, its time and any error for support without exposing credentials or customer data publicly.

Live updates follow supported customer actions and changes. They are not a documented nightly full copy, and saving configuration does not guarantee immediate updates. A connection test proves neither end-to-end synchronization nor a completed historical import. Production availability and provider-side setup must be checked for the club.

Use member data and purchased matches

Member fields include email and name, available gender, birth date, address, postcode and city; newsletter consent; consumer or business classification; purchase and cancellation dates; season ticket and subscription summaries; scans, partner details, releases and tickets sent from season tickets. Values depend on available source data. The country field is created but no country value is currently populated by the integration.

Purchases and cancellations update dates and purchased-match selections. A purchased-match option's final label contains the event name and local date, without the event identifier. Use these choices when selecting customers for a particular match.

For an audience requiring an active ticket subscription, use the boolean active_ticket_subscription together with the appropriate consent and list rules. One inactive subscription does not make the member inactive while another remains active. False requires a known subscription set with none active; missing or unknown information must not be treated as false.

A confirmed failed renewal updates the saved subscription information. It is not a named payment-failure metric like Klaviyo's. A successful renewal may be recorded before the subscription status becomes active again, so check current eligibility before sending a message that assumes recovery.

Member synchronization, list membership and permission to send are separate. eventii writes newsletter_consent when it knows the consent value. A customer or subscription update can synchronize data without granting permission to send. Check consent and HeyLoyalty's sending rules even when the member exists on the list. Do not assume an unsubscribe in HeyLoyalty automatically updates eventii; agree the handling with support.

Ask support to arrange a separate historical import and confirm its scope, list compatibility and outcome. Saving connection details does not start it. The import checks the list's required field types before starting. A report that source data has been submitted is not proof that HeyLoyalty has applied every update. Check representative members with support. Historical synchronization does not invent earlier payment failures, and no completion time is promised.

Troubleshoot by symptom

SymptomWhat to check
Integrationer er ikke slået til herAsk support about service availability. This is different from an invalid credential.
Test or save failsCheck all four connection inputs and your management permission. Test and save are separate; retain the actual error for support.
Connection works but old customers are missingConfirm that a historical import was requested and that provider updates were checked.
Member fields or match choices are missingUse Opret medlemsfelter, review type conflicts or deferred choices, and check qualifying purchase data.
Webshop activity is missingCheck separate tracking configuration, email and eligible product data. Support can distinguish rejected requests from temporary failures that can be retried. Most provider validation or permission rejections are not automatically retried.
Subscription eligibility looks wrongReview all of the member's subscriptions and missing history with support. Do not replace unknown state with false.

Reference: activities

ActivityHeyLoyalty effect
Customers and newsletter consentCreate, update or remove member details and update known consent.
OrdersUpdate purchase information for created, paid and cancelled orders and cancelled order lines.
Attendance and season tickets sent as ticketsUpdate entry scans and sent-ticket details.
PartnersUpdate partner registrations and contact changes.
Season ticketsUpdate activation, changes, cancellations, releases and available access history.
Ticket subscriptionsUpdate subscription history and current eligibility, including failed renewals.
Purchased matchesUpdate the member's qualifying match selections.
Optional trackingProduct visit: visit; basket addition: basket; basket removal: removefrombasket; paid order: bought; cancellation: cancelled.

Reference: member fields

Names are case-sensitive HeyLoyalty fields. Types below are the provider formats created by eventii. Values can be absent when source data is missing.

GroupField names and provider types
Standard identityemail (text), firstname (text), lastname (text), sex (choice, fixed), birthdate (date), address (text), postalcode (number), city (text), country (choice, fixed), reference (text)
Consent, B2C/B2B and record referencesnewsletter_consent (boolean), is_b2c (boolean), is_b2b (boolean); eventii_customer_id, eventii_customer_ids, eventii_partner_id, eventii_partner_ids, partner_groups, eventii_partner_group_ids, eventii_partner_groups (text)
Purchasesales_channel, eventii_last_purchase_at_utc (text); last_purchase_date, last_cancellation_date (date)
Season tickets, ticket subscriptions and accessseason_tickets (text; JSON history), ticket_subscriptions (text; JSON history), active_card_types, previous_card_types, ticket_subscription_types, active_entitlement_types (text), active_entitlement_count (number), active_ticket_subscription (boolean); last_card_type, last_card_section, last_card_price_category (text); last_card_expiration_date, last_card_activation_date, last_card_cancellation_date (date)
Scanlast_scan_date (date), last_scan_type, last_scan_event_name, last_scan_entrance (text), eventii_last_scan_at_utc (text)
Partnerpartner_name, partner_registration_product, last_partner_event_name (text), last_partner_event_date (date), eventii_last_partner_at_utc (text)
Releaselast_release_date (date), last_release_event_name, last_released_card_type (text)
Sent cardlast_card_sent_date, last_card_sent_event_time (date), last_card_sent_recipient, last_card_sent_barcode, last_card_sent_event_name (text)
Purchased matchespurchased_matches (multi; configured event options)

Custom dates use yyyy-MM-dd. The eventii_*_at_utc values are text timestamps, not provider date fields. sex and country are fixed choices; eventii sends numeric sex codes but does not populate a country value. purchased_matches contains selections from configured options.

Use booleans, dates, numbers, scalar text and purchased-match choices for practical segments. season_tickets, ticket_subscriptions and eventii_partner_groups contain JSON history stored as text. They are not directly queryable collections. active_card_types, previous_card_types, ticket_subscription_types, active_entitlement_types and partner_groups are comma-separated text, so substring matching can also match part of another value.

The plural customer, partner and partner-group reference fields contain JSON arrays. Their singular counterparts are scalar references. These fields help eventii keep records aligned; they are not recommended audience filters.