Constant Contact 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
Open the Integrations hub, find the Constant Contact card, and choose Connect. Authorise in Constant Contact and you're returned to PocketPass.
You can connect one customer list at a time. If you already have another CRM connected, disconnect it first.
What PocketPass writes back
PocketPass creates four custom fields on your Constant Contact account and keeps them current on every synced contact:
| Field | What's in it |
|---|---|
pocketpass_token | The contact's install token. This is what goes in your button link. |
pocketpass_link | Their full install page URL, if you'd rather paste it as plain text. |
pocketpass_installed | Yes once they've added the pass to a wallet, No before that. |
pocketpass_id | Their PocketPass pass id, once one has been issued. |
The field names have no spaces on purpose — that makes the merge tag predictable, so pocketpass_token is always written [[custom.pocketpass_token]].
pocketpass_installed is the useful one for segmenting. Build a Constant Contact segment on it to find everyone who hasn't added their pass yet, and send them a reminder.
Add an install button to a campaign
This is the part that differs from the other connectors, so it's worth reading rather than skimming.
Constant Contact can personalise a link, but only the query part of it — the domain and path have to be fixed text. So instead of storing a whole URL in a field and dropping that in, you paste one literal link and Constant Contact fills in each recipient's token:
https://getpocketpass.com/e?t=[[custom.pocketpass_token]]
- In your email, add a Button block (or select some text and click the link icon).
- Choose Web Page as the link type and paste the URL above as the destination.
- Send.
Each recipient lands on their own install page, which offers both Apple Wallet and Google Wallet — so one button covers both, and you don't need a separate Apple and Google link the way you do in other CRMs.
The Add an install button to your emails section on the Constant Contact manage page has this link ready to copy, along with button HTML if you'd rather use a custom-code email.
Two things that will otherwise catch you out
- Personalised links don't render in Preview, or in a test send. The link will look broken or dead. This is a Constant Contact limitation, not a PocketPass one. To check it properly, schedule a real send to yourself.
- Click reporting shows the base URL only. Constant Contact reports clicks against
getpocketpass.com/e, not per recipient. Your install numbers in PocketPass are the accurate ones.
Lists and segments
PocketPass imports your Constant Contact contact lists, so you can target notifications and write template rules against them.
Segments are deliberately not imported. Constant Contact's segment API can return results while a segment is still being calculated, and PocketPass replaces its local copy of membership on every sync — so a partial read could quietly drop members and change which template a customer's pass uses. Lists have no such caveat. If you need segment-shaped targeting, use PocketPass group tags alongside your lists.
Keeping contacts in sync
Use Refresh customers on the Constant Contact manage page to import your contacts into the Customers directory. Between clicks, PocketPass polls Constant Contact automatically — Constant Contact has no contact webhooks, so polling is how changes are picked up.
A large first import can take a day or two. Constant Contact caps API use at 10,000 requests per day, and updating a contact costs two of them (its API has no partial update, so PocketPass has to read the whole contact and write it back intact). PocketPass paces itself to stay within the limit and resumes automatically where it left off, including a daily sweep that catches anything a busy day deferred. Nothing is lost — it just isn't instant.
PocketPass only ever adds its own four custom fields. Your contacts' other fields, phone numbers, addresses, tags and list memberships are left exactly as they are.
Triggering wallet pushes
Constant Contact automations can't call a webhook. The Automation Path Builder can send email and SMS, wait, branch, update a contact field, and add or remove tags and lists — but there's no step that calls an external URL, so a push can't be triggered from Constant Contact itself.
Two ways to get the same result:
- Zapier — trigger a Zap on a Constant Contact event and add a "Webhooks by Zapier → POST" action.
- The API — POST to
/api/v1/passes/{id}/notificationfrom your own stack.
Either way you need the customer's pass id, which is on their contact record as pocketpass_id once their pass is installed. See Trigger notifications from your CRM for the exact request.
You can always compose and send a push from the Notifications page in PocketPass without involving Constant Contact at all.
Disconnecting
Disconnect on the manage page stops contact syncing immediately and revokes PocketPass's access on the Constant Contact side. Existing passes keep working and keep updating. The custom fields stay on your contacts — delete them in Constant Contact if you want them gone.