Sending test messages

Before sending a messaging campaign to your users, as a suggested best practice, we recommend testing to make sure it looks right and operates as intended. You can create and send test messages to select devices or team members using the tools in the Braze dashboard.

Step 1: Identify your test users

Before testing your messaging campaign, it’s important to identify your test users. These users can be either existing user IDs or email addresses, or new users that are used exclusively for testing messaging campaigns.

Optional: Create a Content Test Group

A convenient way to organize your test users is by creating a Content Test Group, which includes a group of users that will receive test messages from campaigns. You can add this test group to the Add Content Test Groups field under Test Recipients in your campaign, and launch your tests without creating or adding individual test users.

Step 2: Send channel-specific test messages

For steps to send test messages, refer to the following section for your respective channel.

• email
• push
• in-app message
• content card
• sms/mms
• webhook

Testing personalized campaigns

If you are testing campaigns that populate user data or use custom event properties, you’ll need to take additional or different steps.

Testing campaigns personalized with user attributes

If you are using personalization in your message, you’ll need to take additional steps to properly preview your campaign and check that user data is properly populating the content.

When sending a test message, make sure to choose either the option to Select Existing User or preview as a Custom User.

Selecting an existing user

If selecting an existing user, enter the specific user ID or email in the search field. Then, use the dashboard preview to see how your message would appear to that user, and send a test message to your device that reflects what that user would see.

Selecting a custom user

If previewing as a custom user, enter text for various fields available for personalization, such as the user’s first name and any custom attributes. Once again, you can enter your own email address to send a test to your device.

Testing campaigns personalized with custom event properties

Testing campaigns personalized with custom event properties differs slightly from testing other types of campaigns outlined.

Method 1: Triggering campaign manually

You can trigger the campaign yourself as a robust way to test campaigns personalized using custom event properties:

1. Write up the copy involving the event property.

2. Use action-based delivery to deliver the campaign when the event occurs.

3. Target the users as you would for testing by using a testing filter or targeting your own email address, and finish creating the campaign.

4. Go into your app and complete the custom event.

The campaign will trigger and show the message customized with the event property.

Method 2: Sending yourself a test message

Alternatively, if you are saving custom user IDs, you can also test the campaign by sending a customized test message to yourself.

1. Write the copy for your campaign.
2. Select the Test tab and choose Customized User.
3. Add the custom event property at the bottom of the page, and add your user ID or email address to the top box.
4. Select Send Test to receive a message personalized with the property.

Method 3: Using Liquid

You can test custom event properties by manually inputting values with Liquid.

1. In the message editor, input values for your custom event properties.
2. Select the Preview as a User tab to check that the correct message displays.

Troubleshooting

In-app messages

If your in-app message campaign is not triggered by a push campaign, check the in-app campaign segmentation to confirm the user meets the target audience before receiving the push message.

For test sends on Android and iOS, the in-app messages that use the Request push permission on-click behavior may not display on some devices. As a workaround:

• Android: Devices must be on Android 13 and our Android SDK version 21.0.0. Another reason may be that the device on which the in-app message is displayed already has a system-level prompt. You may have selected Do not ask again, so you may need to reinstall the app to reset the notification permissions before testing again.
• iOS: We recommend your developer team review the implementation of push notifications for your app and manually remove any code that would request push permissions. For more information, see Push primer in-app messages.

For an action-based in-app message campaign to deliver, custom events must be logged through the Braze SDK, not REST APIs, so the user can receive eligible in-app messages directly to their device. Users can receive the in-app message if they perform the event during the session.