How to instantly test an entire journey

Modified on Tue, 26 Sep 2023 at 12:07 AM

Organizations need to confirm beforehand whether the campaigns incorporated within journeys will get processed properly and dispatched correctly to their clients. They need to verify in advance whether the communications set up within workflows will get forwarded exclusively upon fulfillment of certain conditions and whether the content of the campaigns will appear exactly as intended. Organizations usually perform such checks by means of executing the journeys for test users that can be set from within the marketing automation software.

However, within a journey, campaigns are precisely timed in order to engage clients in an appropriate manner. So, once a journey begins its execution, then all the campaigns within it will get dispatched only after their preconfigured time delays by default, even to a test user. Since brands prefer to bypass such time delays in order to instantly check the proper functioning of campaigns present within their workflows, we devised an essential feature that enables them to do the same.

Bypass time delays of campaigns included within journeys

In this particular section we delineate how you can utilize a feature of the NotifyVisitors software to expedite the process of testing an entire journey.


  1. To utilize the aforementioned feature, you will have to first create a journey
  2. To ultimately test the proper functioning of campaigns, you will have to mark a user for whom the journey has begun its execution as a test user, since this specific feature works exclusively for clients marked as test users within the software. 

Proceed as follows to utilize this feature:

  1. Navigate to the NotifyVisitors Dashboard > Segments > User List.

  1. Using the 'Search Bar' present within the 'User Details' section, search for the specific user that you had previously marked as a test user and copy the user’s NVUID.

  1. Next, navigate to NotifyVisitors Dashboard > Journey.

    You would notice that all of your previously designed workflows are listed within this specific section. Via the 'Search Bar', search for the journey that you intend to test.

Here onwards, we will explain the process of avoiding the preconfigured time delays to instantly receive the communications of the journey.

For instance, consider a cart abandonment journey that has 'Add To Cart' as its primary trigger event and 'Order Place' as its secondary condition (screenshot provided below). Let’s suppose you need to test all the campaigns present within this particular journey. 

There will be two cases in this journey:

  • Case I: Communications with time delays only

    Now, when the test user performs the 'Add to Cart' event, then he/she will enter this journey and all the communications will get scheduled to him/her according to the configured time delays.
  • Case II: Communications with additional conditions

    When the test user performs the 'Add to Cart' event and then performs the 'Order Place' event, then the WhatsApp communication will get scheduled according to the configured condition.

Now to process the aforementioned cases without waiting for the time delays to expire, you need to navigate to the transactional activity and search the test user via the copied NVUID.

It will show the logs of the scheduled communications along with a 'Process Now' button as shown in the screenshot provided below.

Upon clicking on this button, the communication will get processed and dispatched instantly to the inbox. A message confirming that the campaign has been processed would also appear on-screen.

This is how NotifyVisitors enables you to instantly test communications present within a journey before you run the same for all the live users.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article