Apple & Google Wallet marketing
Add the Wallet channel to Omnisend
Turn Omnisend contacts into Apple and Google Wallet passes, with lock-screen push and geo-fenced notifications.
Get started
Why connect it
What the Omnisend integration does.
Contacts become passes
Every contact turns into a live wallet pass, created the moment they add it - no bulk generation, and nothing issued to people who never open the email.
Pushes from your automations
Omnisend has a Send HTTP request step, so a lock-screen message is one more step in the same journey that already runs your emails and SMS.
Install state on the contact
Five custom properties stay current on every contact, so you can segment on who has added their pass and follow up on the rest.
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 Omnisend
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 an email. Every recipient gets their own pass.
Two-way
What lands on every Omnisend contact.
PocketPass writes these back as each pass is issued and installed, so Wallet becomes something you can segment on without leaving Omnisend.
| Field in Omnisend | What it holds |
|---|---|
pocketpass_id | The pass id. Use it to trigger a push from an automation, or from the API. |
pocketpass_link | This contact's own add-to-wallet page. Works on both wallets - it offers the right one. |
pocketpass_apple_wallet | Straight into Apple Wallet, skipping the install page. |
pocketpass_google_wallet | Straight into Google Wallet, skipping the install page. |
pocketpass_installed | Whether they've added it. Segment on this. |
Use it in a Omnisend campaign
Drop the pass id into any message with Omnisend's own merge syntax:
{{ contact.customProperties.pocketpass_id }}Omnisend uses Liquid-style handlebars. Custom fields live under contact.customProperties.<name> - the field name is what you write, no case conversion, no abbreviation.
How it stays in sync
Polled on a schedule
PocketPass polls Omnisend on a schedule to pick up new and changed contacts. A daily reconcile sweep runs behind that to catch anything a polled window misses.
Push from a Omnisend automation
Add a Send HTTP request step to any Omnisend automation and a wallet push goes out in the same journey that already runs your emails and SMS.
Installs land as custom events
Pass installed and Pass removed are recorded against the contact via /api/events, so you can start an automation off wallet activity the same way you start one off any other Omnisend event.
Identity is stable across email changes
Omnisend contacts have a stable contactID that survives an email edit, so a change to someone's address reads as an update to the same person - not a delete plus insert.