eventii Automation
eventii Automation provides profiles, segments, templates, campaigns and automated email inside EventManager's Marketing area. Choose one of Klaviyo or HeyLoyalty; eventii Automation can run next to either. See the Marketing integrations overview for responsibilities and shared rules. eventii Automation receives any phone numbers supplied with customer and order events, but does not retain those fields in its marketing data or use them in profiles, templates or email delivery. eventii does not send phone or mobile numbers to Klaviyo or HeyLoyalty.
Choose how to send
| Mode in EventManager | Use it for |
|---|---|
| Kampagner | A campaign to a selected audience, such as a match announcement. |
| Automatiseringer | An automatic email following a qualifying trigger, such as a purchase. These are also called one-shot automations. |
| Flows | A sequence of emails, waits and decisions, such as subscription follow-up. |
Saving a template, automation or flow alone does not start sending. Complete the applicable test and sending or activation steps below.
Enable Automation and prepare the sender
You need EventManager permission to manage marketing integrations to change enablement, plus permission to manage marketing to prepare and send messages. Viewing access alone is insufficient. Ask support to confirm availability for the club.
- Open Administration → Integrationer, then Avanceret konfiguration → eventiiAutomation. Select Rediger, turn on the enablement switch and select Gem.
- Open Marketing → Marketingindstillinger. Under Afsenderdomæne, complete Domæne, Afsender-e-mail and Afsendernavn, then select Opret domæne. The sender email must use exactly that domain.
- Have the club's domain administrator add the displayed DNS records. Select Bekræft DNS and check for Bekræftet before relying on the club's own sender.
Until verification succeeds, the configured eventii default sender is used. Check the actual sender in a test email. Domain verification does not establish consent, import customers or activate sending. Changes to the sender or content can invalidate a previous test.
Prepare profiles and historical information
Open Marketing → Profiler and inspect representative customers. Available data includes email, name, company, gender, birth date and location; newsletter consent and its source; consumer or business classification; recent purchases, cancellations and scans; season ticket and partner summaries. Subscription and activity records are also kept separately.
Updates follow customer and consent changes, paid or cancelled orders, season ticket changes, entry scans, partner changes, expired baskets and ticket subscriptions. Data received is not the same as a selectable sending trigger. Automation does not receive order-created activity or the product-view and basket-item-change stream used by Klaviyo.
Ask support to arrange a historical import for the required profiles, season tickets, activities and ticket subscriptions, then verify completion for each needed data category. Saving enablement does not start an import. Historical checks become available only after the expected records have arrived. Missing history is not evidence that a customer has no active subscription. Imports do not recreate old payment-failure triggers. No import completion time is guaranteed.
Prepare segments and templates
Use Marketing → Kampagnesegmenter to define the audience and review the matching profiles. If a history-dependent condition is unavailable, ask support to check the historical import before using it.
Under Marketing → E-mailskabeloner, prepare and save the subject and content. Use only personalization fields available for the chosen trigger; purchase, attendance and subscription triggers supply different information. Review the message and links before testing. Templates are reusable content, not an instruction to send.
Send a campaign
Open Marketing → Kampagner, prepare the campaign, select its saved segment and template, and complete any required match or link information. Select Gem, then Send test. Review the test email and check that the current test was accepted. Changes can require another test.
Review the recipient audience, then choose Send nu and enter the exact campaign name when asked to confirm. A campaign uses its selected audience rather than waiting for an activity trigger. Check its sending status and email history afterwards; provider acceptance does not prove inbox delivery.
Activate an automatic email
Open Marketing → Automatiseringer. Select a template and Trigger, then configure the applicable filters. For subscription triggers, Korttype can restrict the subscription type. Use Gem, then Test udløser. Review the test outcome and email. Only a successful test of the current setup allows Aktivér. A pending, unknown or rejected result is not a successful test.
Set Forsinkelse efter hændelsen (minutter) where offered. For Forladt kurv, the default is 60 minutes and the permitted range is 1 to 10,080 minutes. Other one-shot delays default to zero and must be nonnegative. A configured delay determines when sending becomes eligible, not a guaranteed arrival time. Abandoned-checkout triggers require separate service availability; contact support if the option is absent.
Publish and activate a flow
Open Marketing → Flows and choose a direct entry trigger. Build the sequence with E-mail, Vent, Segmentsplit, Split på triggerdata and Afslut. Choose a template for each email and a deliberate destination for each branch. Every path must end. A flow supports at most 100 steps.
Select Gem, then Udgiv. Use Send test for every email step in that published version and review the results. Then select Aktivér. Publication alone does not activate the flow. A new published version needs its own email-step tests. To edit an active flow, first use Deaktivér; this also cancels pending participants, so review its effect before changing a live flow.
Purchase thresholds, attendance thresholds, no-show and subscription-not-fetched are calculated triggers for automatic emails. They cannot start flows. The reference below distinguishes them from direct triggers.
Wait, then check subscription status
Vent waits for a fixed duration of 1 to 525,600 minutes. Segmentsplit evaluates current membership once and chooses a branch. It does not wait for a subscription to change or repeatedly check it.
For a renewal follow-up, add Vent, then Segmentsplit against a segment using Status for billetabonnement, Er lig med and Active. Route the matching branch to the intended email. Deliberately route the other branch to Afslut, or add another explicit wait and check before ending. A recorded renewal can temporarily still have Expired status.
An Active condition matches a customer with any active subscription. Expired can match the same customer if another subscription has expired. Er ikke lig med Active also includes customers with no subscriptions once complete history is available. Removed subscriptions are excluded. Do not infer that the entire customer relationship is inactive from one failed renewal.
Consent and delivery history
Triggers record activity and do not grant consent. Before delivery, eventii checks current customer consent and email. A saved audience or earlier consent value does not override that check. Native unsubscribe links retract consent. Provider unsubscribe, spam-report and bounce notifications also cause retraction when customer and email can be identified. A provider dropped result stops delivery without the same consent retraction.
Open Marketing → E-mailhistorik to inspect results and reasons, and check the flow's status when relevant. Temporary failures can be retried within a five-attempt limit. Actual delivery depends on eligibility, configured delays and provider results; live processing is not an instant-delivery guarantee or a nightly full copy.
Troubleshoot by symptom
| Symptom | What to check |
|---|---|
| Marketing er ikke slået til her or integrations unavailable | Ask support about service availability and enablement. |
| Subscription segment unavailable | Ask support to verify the required historical records have arrived. Do not treat unknown history as false. |
| No email | Check the intended sender, domain verification, current test, publication and activation where applicable, consent, email and audience eligibility. Inspect E-mailhistorik and flow status. |
| Afventer afstemning or unknown delivery | The provider outcome is uncertain, not proven failed. Ask support to reconcile it before any manual resend. |
| Test or save fails | Check management permission and required fields. Keep the actual error for support; saving and testing are separate actions. |
Reference: direct triggers
Direct triggers can start automatic emails and flows, subject to availability and eligibility.
| Family | Trigger labels in EventManager |
|---|---|
| Commerce and engagement | Ordre betalt, Forladt kurv, Gået ind, Partner tilmelding. |
| Consent and season tickets | Nyhedsbrev tilmelding, Sæsonkort køb, Sæsonkort frigivet. |
| Ticket subscriptions | Activation, renewal, cancellation, use and payment failure, as detailed below. |
| Subscription trigger | Use |
|---|---|
| Billetabonnement køb | Subscription activation. |
| Billetabonnement fornyelse | A recorded renewal; check status separately if active access is required. |
| Betaling af billetabonnement fejlet | A confirmed declined payment, including a first payment for a new subscription or a renewal. |
| Billetabonnement opsigelse | Subscription cancellation. |
| Billetabonnement brugt | A subscription redeemed for a ticket. |
The payment-failure trigger excludes pending or timed-out payments, but can follow a declined first payment before the subscription has been activated. Use wording that fits both first payments and renewals, such as "Your ticket subscription payment could not be completed." It supplies subscription-type context, not a status or first-payment personalization field.
Reference: calculated triggers
| Trigger label | Use in automatic emails only |
|---|---|
| Antal købte events | Purchase-event threshold. |
| Antal fremmøde med sæsonkort | Attendance threshold. |
| Udeblivelse | No-show audience. |
| Billetabonnement ikke hentet | Subscription ticket not fetched. |
Reference: support identifiers
These identifiers help support compare a configuration with the guide. Use the screen labels in normal setup.
| Identifier | Meaning |
|---|---|
TicketSubscriptionPaymentFailed | Confirmed failed first payment or renewal trigger. |
ticketSubscriptionStatus | Subscription-status segment condition. |
cardTypeId | Subscription-type filter where supported. |
delayMinutes | One-shot delay in minutes. |
cardType | Subscription-type rendering context. It does not report current status. |