Klaviyo integration
eventii sends customer profiles, purchases, cancellations, attendance, season tickets, ticket subscriptions and partner information to Klaviyo. Your club builds segments and sends campaigns or flows in Klaviyo. Start with the Marketing integrations overview for platform choice and shared responsibilities.
Before you use the integration
Have your Klaviyo administrator prepare the private API credential and confirm which list should receive consent updates. Choose Klaviyo or HeyLoyalty for the club; they cannot be configured together. eventii Automation can run alongside Klaviyo.
You need EventManager permission to manage marketing integrations to test, save or remove the connection. Permission to view integration settings is insufficient. Ask the club's administrator to check access if those operations are refused.
Connect in EventManager
- Open Administration → Integrationer and find the Klaviyo card.
- Enter the private API credential in Privat API-nøgle.
- Select Test forbindelse and check the result. Correct any error before continuing.
- Select Gem and check that saving succeeds. Testing and saving are separate operations; a successful test does not save the connection.
If Integrationer er ikke slået til her appears, contact eventii support about service availability. This is different from an invalid credential. Do not include credentials in support messages or screenshots.
Confirm consent-list mapping
The Klaviyo card has no list selector. Before relying on newsletter consent, ask eventii support to confirm that the relevant consent choices are mapped to the intended Klaviyo list. eventii sends consent grants and retractions only when the consent change includes that configured list reference.
Profile updates and subscription metrics do not grant consent. Klaviyo's suppression and sending rules still apply. Do not assume an unsubscribe in Klaviyo automatically updates eventii; agree how the club will handle it with support. eventii does not send phone or mobile numbers to Klaviyo.
Verify the first synchronization
After saving, check a known recent customer change and purchase with support. Find the corresponding profile and compare the expected fields and activity in Klaviyo. Order creation produces Started Checkout; payment produces Placed Order. Simply opening webshop checkout does not produce Started Checkout through this integration.
Customer synchronization can create or update a profile. Ticket subscription changes require an existing matching profile with the necessary customer or partner reference and email; they do not create a replacement when matching fails. A successful connection test alone does not prove that real activity is arriving.
Understand profiles and activity
Profile properties describe the person: available name, email and address; gender, birthday and consumer or business classification; season ticket and ticket subscription summaries; purchase, scan and partner recency; partner details and available history. Metric properties describe one activity. Use profile fields for an audience's current characteristics and metrics for actions that occurred.
Product-view metrics contain product and category information. Basket changes contain product, price category and price. Order metrics contain order, item and address information. Attendance contains event, entrance, pass, section and price category. Subscription metrics contain type, status, expiry and applicable redemption details. A field available on one metric is not necessarily present on another.
Eligible subscription changes produce activation, renewal, cancellation, use or payment-failure metrics. Type changes, historical snapshots and reassignment update saved state without lifecycle metrics. A declined renewal can leave the subscription expired; a later recorded renewal carries its current status.
Live updates and historical synchronization
Live updates follow new activity, with no guaranteed delivery time. Configuration changes are not necessarily effective immediately. There is no documented nightly full copy.
Ask eventii support to arrange and verify a historical import separately. Saving credentials does not start it. Klaviyo's historical operation updates existing profiles only, so missing old customers may need a separate customer setup step agreed with support. An accepted import is not proof that Klaviyo has applied every update. Historical synchronization does not invent old Ticket Subscription Payment Failed metrics.
EventManager also offers Send ordrer til Klaviyo in a match's action menu when Klaviyo is configured. With management permission, use it for that match's paid orders. It is not a general historical import.
Build a segment or flow
For a current subscription audience, filter the profile boolean active_ticket_subscription to true and apply Klaviyo's consent and sending eligibility conditions. One inactive subscription does not make a person inactive while another remains active. False is written only when the saved subscription set is known and none is active. Missing history is not evidence of false.
For a payment-failure follow-up, use a metric-triggered flow selecting Ticket Subscription Payment Failed. It can follow a declined first payment for a new subscription or a renewal. Use wording that fits both, such as "Your ticket subscription payment could not be completed." The metric has no first-payment indicator, and status alone does not distinguish the two cases. Refine it using the relevant subscription properties and review consent before sending. A later Ticket Subscription Activated records successful activation; Ticket Subscription Renewed records a renewal.
For list-valued fields, use Includes any of for complete-item membership. Contains the text matches text within list values. Profile dates can use date operators when recognized as dates; event properties cannot use date-based segment operators. See Klaviyo's segment condition reference.
Troubleshooting
| Symptom | What to check |
|---|---|
| Test or save fails | Check the credential and management permission. Record which operation failed and preserve its error for support. |
| Connection succeeds but old customers are missing | Confirm whether a historical import was requested and whether the profiles already existed. |
| Recent activity is missing | Check the customer match, email and expected activity type with eventii support. Opening checkout alone is not an order creation. |
| A subscription audience looks wrong | Ask support to compare all subscriptions and available history before relying on the profile summary. |
| Consent or sending differs | Confirm consent-list mapping, Klaviyo suppression and sending eligibility. A profile or metric is not permission to send. |
Reference
Metric catalogue
| Metric | Trigger |
|---|---|
Active on Site | A tracked active-site event. |
Viewed Product, Item Added to Basket, Item Removed from Basket | Webshop activity. |
Started Checkout | Order creation. Webshop checkout opening does not publish this metric. |
Placed Order | An order is paid. |
Cancelled Order | An order is cancelled. |
Event Attended | Attendance activity. |
Ticket Subscription Activated, Ticket Subscription Renewed, Ticket Subscription Cancelled, Ticket Subscription Used | Eligible ticket-subscription lifecycle changes. |
Ticket Subscription Payment Failed | A confirmed declined payment, including a first payment for a new subscription or a renewal. |
Profile property catalogue
Property names are case-sensitive. Types describe the values written to Klaviyo. Fields are present only when the activity or club's data supplies them.
| Group | Profile properties and data types |
|---|---|
| Standard profile fields | email (text), first_name (text), last_name (text), external_id (text); location (object with address fields when available) |
| Customer and classification | Gender, ConsumerType, BirthDay (text); IsB2c, IsB2b, active_ticket_subscription (boolean); eventii_customer_id, eventii_partner_id (text) |
| Season ticket, subscription and access summary | CardTypes, PriceCategories, PreviousCardTypes, TicketSubscriptionTypes, ActiveEntitlementTypes (array of text); ActiveEntitlementCount, OrdersPaidCount18Months (number) |
| Purchase and activity recency | LastOrderPaidUtc, LastScanUtc, LastPartnerAtUtc (date-time) |
| Partner summary and references | PartnerName, PartnerRegistrationProduct, LastPartnerEventName (text); eventii_partner_ids, partner_groups, eventii_partner_group_ids (array of text) |
| Saved history and synchronization details | SeasonTickets (array of objects), TicketSubscriptions (object keyed by subscription ID), eventii_partner_groups (object); HistoricalProfileAsOfUtc, HistoricalPartnerAsOfUtc, HistoricalSnapshotAsOfUtc (date-time); LastCustomerUpdatedAtUtc (date-time), LastCustomerUpdatedEventId (text) |
Use simple values and lists for profile segmentation. SeasonTickets, TicketSubscriptions and eventii_partner_groups contain nested history; do not assume their nested fields are direct profile filters. Reference arrays help support match records. active_ticket_subscription summarizes active status, while TicketSubscriptionTypes includes names from active and expired subscriptions. Subscription history records each subscription's identifier, type, price category, status, expiry and version.
Metric property catalogue
Metric property names below are case-sensitive. Types describe the event property values; they do not imply that every property is populated for every event.
| Metric | Top-level properties and types |
|---|---|
Active on Site | Channel (text; Webshop). The session identifier is not an event property. |
Viewed Product | Categories (text array); ProductID, ProductName, ImageURL, URL (text); ExperienceDate (date-time). |
Item Added to Basket, Item Removed from Basket | ProductId, PriceCategoryId (GUIDs serialized as text); ProductName, PriceCategory, Type (text); Price (number). |
Started Checkout, Placed Order | OrderId, SalesChannel, DiscountCode (text); DiscountValue (number); ItemNames, Categories, PriceCategories, Sections (text arrays); EventStartTimes (ISO-formatted text array, not native date-time); Items, BillingAddress, ShippingAddress (nested objects/arrays). |
Placed Order additional properties | TransactionId, TransactionTime (text; TransactionTime is a formatted timestamp); TransactionFee (number). |
Cancelled Order | OrderId, CancelledBy, CancellationTime, SalesChannel, DiscountCode (text); DiscountValue (number); ItemNames (text array); Items, BillingAddress, ShippingAddress (nested objects/arrays). This event has no top-level Categories or Sections. |
Event Attended | EventName, EntranceName, PassType, EntityId, Section, PriceCategory (text). |
| Ticket-subscription lifecycle metrics | Channel (text; Ticketing); ticket_subscription_id, card_type_name, status, used_event_id, used_event_name (text); expiration_utc, used_event_start_utc (date-time; the latter can be absent). |
Nested metric objects are not direct segment filters. Use EventStartTimes and subscription dates for value matching or activity history, not event-property date ranges. Fields may be absent depending on the activity and available club data. Only eligible lifecycle changes produce the subscription metrics listed above.