ActiveCampaign becomes the source of your wallet passes: PocketPass imports your contacts, gives each one their own install link, and keeps a set of custom fields up to date on their contact record so you can see who's added their pass.
Connect it
ActiveCampaign is a little different from the other integrations here. It doesn't offer a "connect with ActiveCampaign" button to outside apps, so instead of sending you over there to approve access, you copy two values across yourself. It takes about a minute.
- In ActiveCampaign, go to Settings → Developer.
- Copy your API URL — it looks like
https://youraccount.api-us1.com. - Copy your API Key from the same screen.
- In PocketPass, open the Integrations hub, choose ActiveCampaign, and paste both in.
Paste the URL exactly as ActiveCampaign shows it — with or without the trailing /api/3, either works.
PocketPass checks the key against your account before saving, so if something's wrong you'll be told which of the two fields to look at rather than finding out later when a sync quietly fails.
You can connect one customer list at a time. If you already have another CRM connected, disconnect it first.
There's nothing to pick after connecting. Unlike Mailchimp or Campaign Monitor, ActiveCampaign keeps contacts at the account level rather than inside a list, so PocketPass syncs all of them and sets everything up straight away.
If your key stops working
An API key can't be renewed automatically the way an approved connection can. If you regenerate it in ActiveCampaign — or delete the user it belongs to — syncing stops and the ActiveCampaign page shows Needs attention with a box to paste the new key into. Nothing else is lost.
What PocketPass writes back
PocketPass creates five custom fields on your account and keeps them current on every synced contact:
| Field | Merge tag | What's in it |
|---|---|---|
PocketPass Link | %POCKETPASS_LINK% | Their install page URL. This is the one to put behind a button. |
PocketPass Apple Wallet | %POCKETPASS_APPLE_URL% | Adds straight to Apple Wallet, skipping the install page. |
PocketPass Google Wallet | %POCKETPASS_GOOGLE_URL% | Adds straight to Google Wallet. |
PocketPass Installed | %POCKETPASS_INSTALLED% | Yes once they've added the pass to a wallet, No before that. |
PocketPass ID | %POCKETPASS_ID% | Their PocketPass pass id, once one has been issued. |
The merge tag in the middle column is what you paste into an email or an automation.
These fields belong to your whole account, not to one list — so a campaign to any list can use them. That's different from Mailchimp and Campaign Monitor, where the equivalent fields only exist on a single list.
PocketPass Installed is the useful one for segmenting. Build an ActiveCampaign segment on it to find everyone who hasn't added their pass yet, and send them a reminder.
Add an install button to an email
- In your email, add a Text block and switch it to the source/HTML view.
- Paste the button HTML from the Add an install button to your emails section on the ActiveCampaign manage page. It's ready to copy, with the official Apple and Google wallet badges already in it.
- Send.
If you'd rather build the link yourself, %POCKETPASS_LINK% is the whole URL — put it straight in a button's destination. One link covers both wallets: the page it opens detects the device and offers Apple Wallet or Google Wallet accordingly. Use %POCKETPASS_APPLE_URL% and %POCKETPASS_GOOGLE_URL% if you'd rather show two separate buttons.
Send to a segment where PocketPass Link isn't blank. A contact PocketPass hasn't reached yet has nothing in that field, and the button will link nowhere.
Lists, segments and tags
PocketPass imports your lists, segments and contact tags so you can target notifications and write template rules against them. See Lists, tags & segments from your CRM.
Keeping contacts in sync
Use Refresh customers on the ActiveCampaign manage page to import your contacts into the Customers directory. Between clicks, PocketPass keeps up in two ways:
- A webhook, so a contact being added, updated, unsubscribed, or tagged reaches PocketPass within moments.
- A full check twice a day, which re-reads everything regardless. This is the safety net, and it earns its keep here: ActiveCampaign doesn't count a tag change as an edit to the contact, so tagging is invisible to the routine check and only the webhook sees it. It also doesn't retry a webhook it failed to deliver, so anything dropped is dropped for good until the sweep picks it up.
A large first import runs steadily rather than all at once. ActiveCampaign caps how many requests we can make per second — and that cap is shared with every other tool connected to your account, so PocketPass deliberately leaves room for them. It paces itself and resumes automatically where it left off. Nothing is lost; it just isn't instant.
If updates seem to have stopped arriving quickly, check your webhook list in ActiveCampaign under Settings → Developer → Webhooks. If PocketPass isn't there, use Re-register webhook on the manage page. Your data stays correct in the meantime; it just refreshes on the slower schedule.
Triggering wallet pushes from an automation
ActiveCampaign automations can send a wallet push — add a Webhook action and point it at PocketPass.
The Webhook action gives you a URL field and nothing else: you can't add headers, and the body it sends is ActiveCampaign's own contact data. So everything travels in the URL. The Trigger push notifications section on the ActiveCampaign manage page composes the whole thing for you — write your message, insert merge tags for the contact's name or email, and copy the finished URL.
It looks like this:
https://your-pocketpass-domain/api/v1/passes/notify?apiKey=YOUR_KEY&id=%POCKETPASS_ID%&message=Your%20points%20were%20updated
Treat that URL as a secret — it contains your notification key. Anyone with it can send a push to your passes.
The push only reaches contacts who've actually installed their pass. A contact with no PocketPass ID has nothing to push to, and the request is ignored.
You can always compose and send a push from the Notifications page in PocketPass without involving ActiveCampaign at all.
Starting an automation when someone adds their pass
This one's optional, and it needs a second set of credentials.
With event tracking switched on, PocketPass records a Pass installed or Pass removed event against the contact, which you can use to start an automation — a thank-you email when someone adds their pass, say, or a win-back when they remove it.
To set it up:
- In ActiveCampaign, go to Website → Site Tracking and make sure Event Tracking is switched on.
- Copy the account id and the event key from that screen. The event key is not your API key.
- Paste both into the Start automations when someone adds their pass section on the PocketPass manage page.
Without this, everything else still works — you simply won't get the two events, and you can add them any time.
Disconnecting
Disconnect on the manage page stops contact syncing immediately and removes PocketPass's webhook from your ActiveCampaign account. Existing passes keep working and keep updating.
Your API key is yours, so there's nothing for PocketPass to revoke — regenerate it in ActiveCampaign if you want the old one dead. The five custom fields stay on your contacts; delete them in ActiveCampaign if you want them gone.