Connect Omnisend

Omnisend becomes the source of your wallet passes: PocketPass imports your contacts, gives each one their own install link, and keeps a set of custom properties up to date on their contact record so you can see who's added their pass.

Connect it

1. Open the Integrations hub and choose Omnisend.
2. Click Connect Omnisend. You'll be sent to Omnisend to sign in and approve the connection.
3. Approve the four permissions PocketPass asks for — reading and writing contacts, sending custom events, and reading segments — and you're back in PocketPass, connected.

That's it. Access tokens don't expire on their own, so you won't be asked to reconnect on a schedule.

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. Omnisend's contacts are account-wide rather than per-list, so PocketPass syncs all of them and sets everything up straight away.

If the connection stops working

Omnisend's tokens don't expire, so if the Omnisend page shows Needs attention it usually means someone removed the PocketPass app from your Omnisend account settings. Click Reconnect Omnisend on the manage page to issue fresh credentials.

What PocketPass writes back

PocketPass keeps five custom properties current on every synced contact:

The merge tag in the middle column is what you paste into an email or an automation. Omnisend uses Liquid-style handlebars, and the property name is exactly what PocketPass writes — no case conversion, no abbreviation.

These properties belong to your whole account, so any campaign, segment or automation can use them. That's the same account-wide model as ActiveCampaign and HubSpot, and unlike Mailchimp / Campaign Monitor / Constant Contact, whose equivalent fields only exist on a single list.

pocketpass_installed is the useful one for segmenting. Build an Omnisend segment on it to find everyone who hasn't added their pass yet, and send them a reminder.

The properties appear on a contact record only once PocketPass writes to that contact — which is the first time it issues them a personal install link. An empty schema before that is expected.

Add an install button to an email

1. In your Omnisend email, add a Text or Custom HTML block.
2. Paste the button HTML from the Add an install button to your emails section on the Omnisend manage page. It's ready to copy, with the official Apple and Google wallet badges already in it.
3. Send.

If you'd rather build the link yourself, {{ contact.customProperties.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_wallet and pocketpass_google_wallet 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 property, and the button will link nowhere.

Segments

PocketPass imports your Omnisend segments so you can target notifications and write template rules against them. See Lists, tags & segments from your CRM.

Tags exist in Omnisend but aren't surfaced as audiences in PocketPass — accounts tend to have far more tags than segments, and any contact can carry any number of them, so listing them all would drown the picker. If you want to target on a tag, build an Omnisend segment against that tag first, and use the segment here.

Keeping contacts in sync

Use Refresh customers on the Omnisend manage page to import your contacts into the Customers directory. Between clicks, PocketPass polls Omnisend on a schedule to pick up new and changed contacts.

A large first import runs steadily rather than all at once. Omnisend caps how many requests we can make per minute — 400 requests/minute, shared with every other tool connected to your account — so PocketPass paces itself and resumes automatically where it left off. Nothing is lost; it just isn't instant.

Triggering wallet pushes from an automation

Omnisend automations can send a wallet push — add a Send HTTP request step and point it at PocketPass.

The step accepts a full URL, custom headers and a JSON body, so this works the same way as Klaviyo, Mailchimp and HubSpot. The Trigger push notifications section on the Omnisend 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 request.

It looks like this:

POST https://your-pocketpass-domain/api/v1/passes/notify
Authorization: Bearer pkw_live_YOUR_KEY
Content-Type: application/json

{
  "id": "{{ contact.customProperties.pocketpass_id }}",
  "message": "Your points were updated"
}

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 Omnisend at all.

Starting an automation when someone adds their pass

PocketPass records a Pass installed or Pass removed custom event against the contact whenever they add or remove their pass. You can use either as the trigger for an Omnisend automation — a thank-you email when someone adds their pass, say, or a win-back when they remove it.

Nothing to configure on the PocketPass side; the events start flowing the moment the connection is live. In Omnisend, create a new automation with Custom event as the trigger and pick Pass installed or Pass removed.

Disconnecting

Disconnect on the manage page stops contact syncing immediately. Existing passes keep working and keep updating.

There's no token to revoke from PocketPass's side — if you want the OAuth grant itself gone, remove the PocketPass app from your Omnisend account settings. The five custom properties stay on your contacts; remove them in Omnisend if you want them gone.