How to test Scenarios

Quality assurance (QA) for Bloomreach Engagement scenarios ensures they function correctly and deliver the intended outcomes. By performing QA, you can ensure your scenarios are reliable, effective, and aligned with your business goals.

There are three ways to test scenarios:

• Using the Preview tab,
• Using event triggers,
• Using "as live" email testing.

Preview tab

Use the Preview tab for:

• Building a scenario to check customer flow
• Debugging existing scenarios. For example, if something changes in the data, conditions can fail.
• Non-event triggered scenarios

Monitoring the customer flow

You can always see the number of customers flowing through. In more complex scenarios, this number may seem high.

When you start the scenario, a warning message will show the number of affected customers. The numbers may not match, but in simple scenarios, they often do (for example, 4 customers).

Understanding customer numbers

In the example below, we're testing two triggers. This results in twice as many customers appearing to flow through, even though both wouldn't happen simultaneously.

With two action nodes per customer, the warning message will show 16 affected customers.

Event triggers

When building a triggered scenario, include a separate testing flow for a dummy/test customer.

In the Add event node, include any required attributes (e.g., filters or email). Ensure the Allow scenario triggering checkbox is ticked.

Advanced tests

Your testing flow can be more complex, depending on the scenario's needs.

Specify custom timestamps to ensure events occur in the correct order.

“As Live” email testing

Use the custom recipient setting to send all emails to yourself, which is useful for complex scenarios difficult to test with dummy data.

Set the scenario live for real customers, but deliver emails to you. Review the data afterward. This test acts as a safety net to prevent accidental sends during scenario development.