Actions

What Klaviyo can trigger in The Wallet Crew (authenticated links and wallet-side actions).

Klaviyo can drive wallet behavior in two ways.

• By sending authenticated links that open a The Wallet Crew experience.
• By calling webhook endpoints that trigger wallet actions.

Real-world examples

• A campaign email contains a link that opens the pass page for the right customer.
• A flow updates a pass after a segment entry.

Authenticated link patterns

Authenticated links are built on neostore.authenticationToken.

Two common patterns exist.

Open an enrolment or registration layout

This is used when the pass is not installed or when a registration step is needed.

https://app.neostore.cloud/<tenantId>/mail?neo.authToken={{person | lookup:'neostore.authenticationToken' }}

Open the pass page

This is used when a pass exists and the goal is to show the pass details.

https://app.neostore.cloud/<tenantId>/mail/confirm?neo.authToken={{person | lookup:'neostore.authenticationToken' }}

Trigger pass update and wallet notifications

Klaviyo flows can trigger server-side actions via webhooks.

In addition to profile sync, webhook actions can call The Wallet Crew APIs to update passes and send wallet notifications.

This keeps Klaviyo as the orchestration layer.

• Pass update is typically done through the Pass API.
• Wallet notifications are covered in Push notifications.

API details and required permissions: API reference.

Start in staging.\nValidate on a test pass.\nRoll out in production once payloads and targeting are stable.

Common mistakes

• Link is missing neo.authToken.
• Token exists but is not attached to the expected Klaviyo profile.
• Flow webhook is not enabled in Klaviyo.

FAQ

Do authenticated links replace “Add to Wallet” buttons?

No. Authenticated links are often used inside email and SMS.

Web and app entry points usually use “Add to Wallet” buttons and dedicated layouts.