ActiveCampaign Loyalty Integration: Put Email Automations and a Wallet Card Together
An ActiveCampaign loyalty integration connects your email automations to a wallet card, so a customer’s tier, tag or last visit in one place matches the other. MSTRMND connects through webhooks and the API on the Business plan. This page covers what it does and where it stops.
Via API and webhooks, Business plan
Connect ActiveCampaign to a wallet card
- Choose the first direction
- Pick one matching key
- Build one automation
- Check email consent
Never email a card holder who has not agreed to email.
What does an ActiveCampaign loyalty integration do?
ActiveCampaign holds who your contacts are and what they have done. MSTRMND holds the card in their phone and what it has earned. An integration lets one tell the other, so an email can mention a reward the customer has actually earned, and a card can react to something the customer did in an email.
MSTRMND does not publish an ActiveCampaign app. The two connect through ActiveCampaign’s webhook and contact steps and the MSTRMND API and webhooks, which the Business plan includes. New to wallet cards? Start with our guide to digital loyalty cards.
Two directions, two jobs
The link can run both ways, and most businesses start with one.
- From the card to ActiveCampaign: a webhook tells ActiveCampaign when a customer joins, reaches a reward or goes quiet. It adds a tag or updates a field, which starts an automation.
- From ActiveCampaign to the card: an automation calls the MSTRMND API when a contact does something, such as completing a form, and adds a stamp or sends a push notification.
Start with the direction that solves your biggest gap. For most venues, that is telling email about card events.
Four ActiveCampaign automations and what drives them
Each row pairs an email automation with a card event or action.
| Automation | Starts from | Card side | Best for |
|---|---|---|---|
| Welcome sequence | Card issued | Webhook to tag the contact | New card holders |
| Reward reminder | One visit from a reward | Push notification to the card | Closing the gap |
| Win-back | Customer gone quiet | Segment written as a tag | Lapsed regulars |
| Form to stamp | Form submitted | API call to add a stamp | Events and referrals |
Keeping the two records in step
The risk with two systems is that they disagree. A customer who changes their email in one place and not the other becomes two people. Choose one key, the phone number or the email, and use it in every step.
Decide which system is the source of truth for each fact. The card is the source for stamps and points. ActiveCampaign is the source for email consent. A tag that says a customer is a regular is derived from the card and written to ActiveCampaign, never typed in by hand.
Automations that suit the link
A welcome sequence for new card holders
When the card is issued, a webhook creates or tags the contact. A short sequence explains the reward and how to find the card in the phone wallet.
A reward reminder
When a customer reaches the point where one more visit earns a reward, tag them and send one email. A push notification to the card can say the same thing, so the customer sees it in both places.
A win-back for lapsed regulars
When a customer goes quiet for a set period, the card’s segment tells ActiveCampaign, which starts a short win-back sequence.
A tier-based newsletter
Send different content to customers by tier, using a tag written from the card. Regulars hear about new products first.
API access by plan
The link needs webhooks and the API, so it needs the Business plan.
Source: MSTRMND plan limits, checked 11 October 2026.
What you need before you start
- The Business plan, which includes API and webhooks.
- An ActiveCampaign account on a plan with the automation steps you need. Check its current plans.
- The API credentials from your MSTRMND account.
- A matching key, phone or email, used everywhere.
- A consent rule: email only goes to contacts who agreed to email.
Where it stops
A wallet card is not an email list. A customer can hold a card without agreeing to marketing email, and the link must not change that. Webhooks pass data, not permission. The build also takes someone who is comfortable with both tools, and a failed call needs an alert or it fails silently.
A first-week plan for an ActiveCampaign loyalty integration
Prove the card-to-email direction first.
- Day one: write down the three card events you want email to know about.
- Day two: choose the matching key and check how your contacts are stored.
- Day three: build one webhook that adds a tag when a card is issued.
- Day four: build the welcome automation that the tag starts.
- Day five: test with your own contact and a real card, then check consent before you switch it on.
Name every tag in plain words and keep a list. Two tags that mean almost the same thing are the most common way an automation sends the wrong email.
Questions to ask before you connect the two
The questions are mostly about permission and clean data.
- Which contacts have agreed to email, and where is that recorded?
- Is every contact keyed the same way in both systems?
- What should happen when a customer unsubscribes but still holds a card?
- Who owns the tags, and who may change them?
Settle these before the build. They are far easier to fix on paper than after a thousand contacts have been tagged.
Frequently asked questions
Is there an ActiveCampaign app for MSTRMND?
No app is published. The two connect through ActiveCampaign’s webhook and contact steps and the MSTRMND API and webhooks, which the Business plan includes. A no-code tool in between can make the build easier if you prefer not to write code.
Does having a card mean a customer agreed to emails?
No. Holding a card and agreeing to marketing email are separate choices. Only send email to contacts who agreed, and record that agreement in ActiveCampaign. The integration passes tags and fields. It should never add someone to an email list on its own.
Which direction should we build first?
Start with the card telling ActiveCampaign, because it is the safer direction for a first build. A tag for a new member or a lapsed regular starts useful automations without changing any card. Add the reverse later, once the matching key is proven.
What does it cost?
MSTRMND’s side is the Business plan, £115 a month billed annually, which includes API and webhooks. ActiveCampaign is a separate subscription priced by contacts and features, so check its current plans against the size of your list before you commit to the build.
Key takeaways
- An ActiveCampaign loyalty integration links email automations to a card through webhooks and the API.
- No app is published, so someone builds the link on the Business plan.
- Start with the card telling ActiveCampaign about joins and lapses.
- Use one matching key, and keep consent separate from the card.
- Add an alert for failed calls.