Vibes

Zeta’s integration with Vibes allows marketers to create, distribute, and manage Mobile Wallet passes that users can install on Apple or Android devices. These passes can be used for loyalty cards, event tickets, promotional offers, and more. This article provides a step-by-step guide for setting up a wallet pass campaign using Vibes and integrating it with ZMP.

Creating and Configuring a Wallet Pass

1. Log in to your Vibes account at https://mpages.vibescm.com.

2. Navigate to Passbook Templates and create a new template or edit an existing one.

   • Example: https://mpages.vibescm.com/passbook_templates/edit

3. Set the Notification Title using a token (e.g., {{title}}). This allows personalization during future updates or messages.

4. After designing your pass, generate the Smartlink from Vibes.

   • Example format: https://mp.vibescm.com/c/

Note the merge tags used in the Smartlink as they will be important for ZMP integration.

5. Create your campaign in ZMP and use the Smartlink as your primary call to action.

6. Append the following tracking tokens immediately after the Smartlink: 

   • /{{bsin}}?data[account_number]={{bsin}}&data[version_id]={{version.id}} 

• {{bsin}}: Links install/removal events to user profiles. 

• account_number: Enables targeting for future pass messaging. 

• version_id: Tracks which version of the campaign was used. 

7. Other merge tags that are required for your pass can be added after the tracking tokens: 

   • Example: &data[first_name]={{first_name}} 

 8. Optional: To track wallet installs and removals, register callbacks for each campaign type: 

• Go to Vibes Callback Documentation.

• Use the following callback types:

  • wallet_item_install

  • wallet_item_remove

• You’ll need:

  • company_id (provided by Vibes)

  • campaign_token (from your Smartlink)

8. If you need to change the details of a pass already installed, use the Update Wallet Item API (API Docs).

Include the following:

• wallet_item_id (same as BSIN)

• wallet_id (same as campaign_token)

• Any token changes (e.g., update expiration date to mark it redeemed)