Klaviyo becomes the source of your wallet passes: PocketPass reads your contacts, creates a pass for each one, and writes the install state back onto their Klaviyo profile so your Flows and segments can act on it.
Connect
Open the Integrations hub, find the Klaviyo card, and choose Connect. You'll be sent to Klaviyo to authorise the connection, then returned to PocketPass.
An account connects one CRM at a time. If another CRM is already connected, disconnect it first.
What connecting does
Once connected, PocketPass:
- Reads your lists and segments. These become the audiences you target notifications at and the conditions you write template rules against - see Lists, tags and segments.
- Samples contact properties. So you can bind template fields to real Klaviyo data - a member's name, tier, or points - when you build a pass. See Passes from your CRM.
- Writes back to each profile. As passes are issued and installed, PocketPass keeps your Klaviyo contacts up to date.
Pull your contacts in
Use Refresh customers on the Klaviyo manage page to import your contacts into the Customers directory. Run it after connecting, and any time you want to pick up new contacts.
The profile properties PocketPass writes
PocketPass writes these properties onto each Klaviyo profile:
| Property | What it holds |
|---|---|
PocketPassID | The pass's ID in PocketPass |
PocketPassInstallPageURL | The customer's personal install link |
PocketPassAppleWalletURL | Direct Apple Wallet link |
PocketPassGoogleWalletURL | Direct Google Wallet link |
PocketPassIsInstalled | Whether the pass has been added to a wallet |
Because these live on the profile, you can drop them straight into a Klaviyo email or SMS - see the Add install buttons to your emails section on the manage page.
Use PocketPassInstallPageURL as the button link in your welcome email. It's the personal install link, so the pass is created the moment that contact clicks - no pass is issued for people who never do.
Metrics you can trigger Flows on
PocketPass fires two Klaviyo metrics, named exactly:
Pass installedPass removed
Build a Flow off either one. Pass installed is the moment a link you sent becomes a real pass holder - a good trigger for a welcome or "here's what your pass does" message.
Metric names are exact and case-sensitive. Match Pass installed and Pass removed precisely when you set up a Flow trigger, or it won't fire.