Brevo

Send Apple Wallet and Google Wallet “Add to Wallet” links from Brevo by importing a `WALLET_LINK` contact attribute.

Brevo can be used to distribute Apple Wallet and Google Wallet passes by email. This setup enriches Brevo contacts with a secure Wallet link, then reuses it in Brevo templates.

Real-world examples

• A retail brand sends a loyalty “Add to Wallet” link after newsletter signup.

• A gift card program sends a “Save your gift card” link after purchase.

• A membership program sends a renewal email that includes the updated pass link.

Prerequisites

Brevo contacts must be exportable and importable. Brevo attributes must also be manageable.

The Wallet Crew must be configured to generate an authToken per email. This token is used to build a secure “Add to Wallet” URL.

If passes are normally generated from a CRM connector (Cegid, Openbravo, etc.), emails imported from Brevo must exist in that system. If that is not the case, use Via Email to generate and send secure “Add to Wallet” links.

Brevo contact update rules and CSV import constraints are documented by Brevo: https://help.brevo.com/hc/en-us/articles/10227982847762-Update-the-information-of-your-contacts

The authToken is a credential. It should be treated as sensitive data. It should not be published publicly or stored in uncontrolled systems.

Needs confirmation: the base “pass landing page” URL can vary by environment and project setup. The correct base URL should be taken from The Wallet Crew project configuration.

Setup

1

1) Export contacts from Brevo

Export a CSV from the Brevo contact list with the email field.

Open: https://app.brevo.com/contact/list

In the Brevo UI, select Contacts → More actions → Export.

Start a contact export from the Brevo contact list.

Use the following options:

• Attributes to export: EMAIL

• CSV field separator: , (comma)

Export only what is needed. Keep the file minimal.

The file becomes available in the Brevo notification center.

2

2) Create a WALLET_LINK attribute in Brevo

Create a text attribute to store the Wallet link per contact.

In Brevo, go to the attributes screen and select Add a new attribute.

Create a new custom attribute for Wallet links.

Create the attribute with:

• Attribute Name: WALLET_LINK

• Attribute Type: Text

`WALLET_LINK` stores the per-contact “Add to Wallet” URL.

3

3) Generate authToken values in The Wallet Crew

In The Wallet Crew admin console, open Token Generator. Generate an authToken based on email.

Generate one token per email.

This step typically outputs a list of {EMAIL, authToken} values. Store them in a working sheet for the next step.

4

4) Build the Wallet links (WALLET_LINK)

For each contact, concatenate:

• the project “pass landing page” base URL

• the query parameter neo.authToken

Example output:

• https://<host>/<tenant>/pass?neo.authToken=<authToken>

In Excel or Google Sheets, a typical formula looks like:

• =BASE_URL & "?neo.authToken=" & AUTH_TOKEN_CELL

The resulting CSV should contain at least:

• EMAIL

• WALLET_LINK

5

5) Import WALLET_LINK values into Brevo

Import the updated CSV so Brevo writes WALLET_LINK on each contact.

Start a contact import to update attributes.

Upload the CSV file:

Select the enriched file that contains `WALLET_LINK`.

Map fields and confirm the import:

Map `WALLET_LINK` to the custom attribute.

Once completed, validate the import report:

Brevo confirms the import job status.

Use the report to catch missing emails or rejected rows.

6

6) Add an “Add to Wallet” button in the Brevo email template

Add a link or button in the email template that points to the WALLET_LINK attribute.

Use the contact attribute as the button URL.

Add a display condition so the block only shows when WALLET_LINK is present.

Hide the Wallet block when the contact has no Wallet link.

FAQ

What happens if a contact email does not exist in the connected CRM?

The Wallet Crew may be unable to resolve an existing customer record for pass creation or updates. In that case, prefer Via Email, which distributes project-generated secure links through The Wallet Crew email flow.

How to validate that `WALLET_LINK` works before sending a campaign?

Run a test import with a small segment. Open a few links from the Brevo contact preview and confirm that the expected pass is displayed and addable to Apple Wallet or Google Wallet.

Should `authToken` be stored long-term in Brevo?

This depends on the security policy and token lifetime defined for the project. If tokens expire or must be rotated, regenerate and re-import WALLET_LINK values before each campaign.