Apple & Google Wallet membership
Add the Wallet channel to Constant Contact
Turn Constant Contact contacts into live wallet passes, with the install link on every record.
Get started
Why connect it
What the Constant Contact integration does.
Contacts become passes
Every Constant Contact contact turns into a live wallet pass, created the moment they add it - no bulk generation.
One button in your email
Drop a single button into any campaign. Constant Contact fills in each recipient's own install link, and the page offers both Apple and Google Wallet.
Install state on the contact
PocketPass keeps a set of custom fields current on every contact, so you can segment on who has - and hasn't - added their pass.
Personalized with their details
Put any contact field on the pass - a name, a tier, a balance - and it stays in sync automatically.
Live in three steps
Connect Constant Contact
Authorize the connection from the dashboard in one click - OAuth, no keys to paste.
Personalize the pass
Choose the contact details to show and how the pass should look.
Add the button
Paste one link into a campaign button. Every recipient gets their own pass.
Two-way
What lands on every Constant Contact contact.
PocketPass writes these back as each pass is issued and installed, so Wallet becomes something you can segment on without leaving Constant Contact.
| Field in Constant Contact | What it holds |
|---|---|
pocketpass_id | The pass id. Use it to trigger a push from an automation, or from the API. |
pocketpass_token | The bare enrollment token, for building your own install URL. |
pocketpass_link | This contact's own add-to-wallet page. Works on both wallets - it offers the right one. |
pocketpass_installed | Whether they've added it. Segment on this. |
Use it in a Constant Contact campaign
Drop the pass id into any message with Constant Contact's own merge syntax:
[[custom.pocketpass_id]]Field labels are lowercase_with_underscores on purpose: Constant Contact builds the merge tag from the field name, so this way it is predictable rather than guessed at.
How it stays in sync
Polled on a schedule
Constant Contact has no contact webhooks, so PocketPass polls on a schedule and runs a slower reconcile sweep behind it.
Push via Zapier or the API
Constant Contact's Automation Path Builder has no webhook or HTTP step at all, so a push cannot be triggered from Constant Contact itself. Use Zapier, or the REST API from your own stack.
Built for Dynamic Links
Constant Contact can only substitute a value into a query parameter, never into a path - so PocketPass also writes the bare token, and your button URL becomes /e?t=[[custom.pocketpass_token]].
Lists, not segments
Segment reads can return mid-computation, and PocketPass replaces local membership authoritatively - so a truncated read would silently delete real data. Lists only, deliberately.