Apple & Google Wallet membership
Add the Wallet channel to Me&u Connect
Turn Me&u Connect contacts into live wallet passes that stay current between visits.
Get started
Why connect it
What the Me&u Connect integration does.
Contacts become passes
Every Me&u contact turns into a live wallet pass, created the moment they add it - no bulk generation.
Personalized with their profile
Drop any contact detail onto the pass - a name, a tier, a balance - and it stays in sync automatically.
Install state on the contact
PocketPass writes the install link and an installed flag back onto each contact, and logs installs and removals to their timeline.
Push to the lock screen
Trigger a wallet notification from a Me&u automation - it lands where email can't.
Live in three steps
Connect Me&u
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.
Watch it sync
Contacts turn into passes and stay current, and Me&u learns who's added their pass.
Two-way
What lands on every Me&u Connect contact.
PocketPass writes these back as each pass is issued and installed, so Wallet becomes something you can segment on without leaving Me&u Connect.
| Field in Me&u Connect | What it holds |
|---|---|
PocketPass ID | The pass id. Use it to trigger a push from an automation, or from the API. |
PocketPass install link | This contact's own add-to-wallet page. Works on both wallets - it offers the right one. |
PocketPass Apple Wallet link | Straight into Apple Wallet, skipping the install page. |
PocketPass Google Wallet link | Straight into Google Wallet, skipping the install page. |
PocketPass installed | Whether they've added it. Segment on this. |
Use it in a Me&u Connect campaign
Drop the pass id into any message with Me&u Connect's own merge syntax:
{contact.pocketpassId}Me&u uses SINGLE-brace merge tags, not the double braces most CRMs use. A doubled tag renders literally.
How it stays in sync
Polled on a schedule
Me&u Connect has no outbound webhooks, so PocketPass polls on a schedule. Changes land within minutes rather than instantly.
Push from a Me&u Connect automation
Add a Webhook step to a Me&u automation. Its webhook step takes body fields only - no custom headers - so the key travels in the body rather than an Authorization header.
Installs land on the contact timeline
Me&u has no custom-event API, so PocketPass writes a note on the contact when a pass is added or removed - visible in the same place your team already looks.
No lists or segments
Me&u Connect doesn't expose audiences, so passes are issued across all contacts rather than to a chosen group.