Before launching a campaign or sending notifications to your entire audience, you should test them to ensure everything works correctly.

Before you start

• To test a campaign, the campaign must already be running in the Campaigns tab
• You need at least one test card in your Audience tab
• Test notifications are sent immediately and cannot be canceled once triggered

💡 Best practices for testing

• Test before scheduling: Always test campaigns and notifications before creating automation rules for your full audience
• Use dedicated test cards: Create specific test cards for your team to avoid impacting real users
• Test both platforms: If your campaign includes both Apple Wallet and Google Wallet templates, test on both platforms
• Test the full user experience: After receiving the test notification, click on it to ensure it opens the correct card content

👤 Test a single card

To test a single card, access the Contacts tab and click on the card you want to test to open it. From there, you will be able to test either:

• A notification, without moving the card to a new campaign.
• A "move" or "move and notify" notification by moving the card to a new campaign and sending a notification (optional).

Test a notification

If you want to test only a notification without moving the card to a new campaign:

1. Hover over the card.
2. Click the three-dot menu (•••).
3. Select Notify
   
4. Enter the notification text you want to test.
5. Click Send.

The notification will be sent immediately to the device associated with that card.

Test a "move" or "move and notify" notification

If you want to test moving the card to a new campaign and sending the associated notification:

1. Hover over the card.
2. Click the three-dot menu (•••).
3. Select Move.
   
4. Select the campaign you want to test.
5. (Optional) Enter the notification text associated with the move.
6. Click Move.

The card will move to the selected campaign, and the notification will be sent.

👥 Test multiple cards

If you have several test cards, you can test them all at once using a target file.

Step 1: Create a CSV target file

1. Create a CSV file with UTF-8 encoding.
2. Include the list of user identifiers you want to target (no headers required, just 1 column with the identifiers).
3. Save the file.

Step 2: Create a test automation rule

1. Go to Automation.
2. Click Create a rule.
3. Select Move, Move and Notify, or Notify depending on your test needs.
4. If applicable, configure your notification text and destination campaign.
5. In the Target section, select Target file.
   
6. Upload your CSV file.
7. Configure the trigger (typically set it to run immediately or at a specific date/time).
8. Give your rule a name.
9. Click Validate.

The rule will execute based on your trigger settings and apply to all cards in your target file.

📍 Test geofence notifications

Testing geofence notifications has limitations:

• Geofence notifications trigger automatically when a user is within 200-300 meters of a defined location.
• You cannot manually trigger a geofence notification from the platform.
• To test, you must physically be near the location coordinates you configured.

To test a geofence notification:

1. Ensure your test device is an iPhone with location services enabled.
2. Configure the geofence notification in your campaign's Apple Wallet template under Advanced Settings > Locations or Advanced Settings > Store.
3. Move the test card to the campaign with geofence notification enabled.
4. Physically visit the location to trigger the notification.

⏭️ What's next?

• Create a geofenced notification in Wallet