The Batch Wallet Notifications feature allows notifications to be sent more efficiently by grouping recipients into batches. Instead of processing each recipient individually, this feature processes multiple recipients together, saving time and resources.

It also introduces new ways to define your target audience, enabling you to send notifications based on pass IDs, user segments, or by uploading a CSV file. These flexible targeting options make it easier to perform quick tests, even without API integration, especially with CSV uploads, which support very large data sets.

Let’s explore each option in more detail below.

Step by Step

Head to the Messaging section and click on the New Message button.

Complete the batch notifications form step-by-step:

  1. Batch Name. Optional. Enter a unique name for the notification batch. This helps you identify and manage batches easily in the future. If you choose not to include a name, the batch will automatically be named “Batch [DateTime]”.

  2. Tag. Optional. Add a custom label to group and track your notification batches.

  3. Message. Required. Write the message you want to send to your recipients. You can use variables to customize the message. Variables are placeholders like %{variable_name} that will be replaced with specific values for each recipient. Click Show Examples for help.

  4. Send At. Required. Choose a date, time, and timezone to schedule the notifications. You can schedule messages to be sent anytime between 1 hour and 365 days in advance, making it convenient to plan campaigns.

Recipients

There are three ways to define recipients for your message:

  • Pass IDs. Manually enter the pass UUID or external ID for each recipient, along with any variables needed for the message. You can add up to 10 recipients via the frontend, with 500 recipients limit when using the API.
  • Pass Filtering. Send messages to everyone within a specific segment, which can be entity-scoped, pass template-scoped, or group tag-scoped. The recipient counter will display how many users you’re targeting. Note that variables cannot be used in messages when using this option.
  • CSV Upload. Upload a CSV file containing recipient data (up to 10 MB). The required column is pass_id, which accepts either the pass UUID or external ID. If your message uses variables, add a column for each variable, with the column name matching the variable name in the message.

Example: For a message like “Hello, %{name%}. Your ticket number is %{ticket_number%}”, your CSV file should include columns named name and ticket_number: DOWNLOAD

Once you’re satisfied with your setup, double-check the message and recipient details, then click Send Message to confirm.

​
Message History: tracking and managing your batches

Once you submit your first message batch, you can track all your batches on the Message History page, which is divided into two tabs: Message Batches and Scheduled Message Batches.

  • Main Information: Each batch displays key details such as the batch name, message text and type, status, and completion time.
  • Error Handling: If any errors occurred, you can download an error CSV directly from this page.
  • Batch Details: Clicking the circular arrow icon will open full batch details, where you can also download a detailed delivery report, broken down by recipient and updated regularly while the messages are being sent.
  • In the Scheduled Message Batches tab, you can cancel any scheduled batches if needed.

That’s everything you need to know to get started with Batch Wallet Notifications. We’d love to hear your thoughts — if you have any feedback or run into issues, let us know so we can keep improving!

Was this page helpful?

Batch Pass CreationPassEntry Reader App