Xbox mobile test message workflows in Braze begin by identifying and organizing test users, either as existing user IDs or emails or as dedicated test accounts, and optionally grouping them into a Content Test Group for repeated use, according to Braze documentation.
Before sending any campaign, Braze advises saving your draft after testing to avoid accidental deletion, while noting that test sends may be performed without saving the draft first.
Channel specific testing follows similar patterns but requires distinct steps. For Banner messages you must ensure the placement exists in the app or site, then preview the banner or send a test to one or more test recipients and view the message on the device for up to five minutes.
For Content Cards you draft the card, select a Content Test Group or individual users on the Test tab and send a test to the app, previewing in the composer and verifying media, Liquid rendering, and links before launch.
Email tests use the Test Send tab where you add an email address or user ID and select Send Test, while web push testing supports a Send Test to Myself workflow that requires browser permission to display the notification.
SMS, MMS, RCS, WhatsApp, LINE, and webhook test flows use the Test tab and require selecting content test groups or individual users, or in the case of webhooks, sending to the supplied URL to inspect the response.
The test checklist Braze recommends is consistent across channels: confirm images and media render correctly, validate Liquid personalization and default attribute values, check that links and buttons behave as intended, and ensure copy is clear and correct.
Debugging, Personalization, Accessibility, and Abort Behavior
For debugging Content Cards, Braze points to the Event User Log in the Developer Console where you can inspect SDK Requests, copy session ids, decode Base64 ids to find campaign_id values, and then locate the campaign on the Campaigns page for further review.
Testing personalized campaigns requires either selecting an existing user to preview or using a Custom User to populate personalization fields, and you can also edit a sampled user to create a custom preview to test dynamic content.
Campaigns that use custom event properties are tested by triggering the relevant event in-app using action based delivery, or by using the Test tab to send a Customized User test message with the event property values entered manually.
Braze distinguishes templated in-app messages from standard ones, noting templated messages fetch payloads at trigger time and therefore can log abort events when Liquid evaluation excludes the user after the trigger has occurred.
The in-app message accessibility scanner runs automatically on custom HTML messages and evaluates them against WCAG 2.1 AA rules, flagging elements, giving issue descriptions, and linking remediation guidance, while cautioning that automated checks need human review for focus order and clarity.
Troubleshooting notes include push token requirements for test devices, the need to tap iOS push notifications to view certain test Content Cards, Android and iOS push permission edge cases, and the requirement that action based in-app triggers must log custom events through the Braze SDK for delivery.
