I have created a Journey with an Email Studio Audience Entry Source. It has data from my UAT environment. I would like to know how this sample data flows through the journey. I have used the Test button to put the Journey into Test. It changes the Status to Testing but nothing happens. Should this test work?

I have read the following help article but I have not found it helpful. http://help.marketingcloud.com/en/documentation/journey_builder/testing_an_interaction/

I have gone through the steps of recreating the Email Audience but I can't find a Test Mode. When I try creating a new Entry Source Event, Email Audience is not an option. I have tried creating an Entry Event with the other options available but I can't find a Test Mode.

My understand is that the new entry Sources are moving us away from Fire Events in Automations.

Please can someone explain how I can use the Journey Builder Test Mode with a Journey with an Email Studio Audience?

  • When you created email studio audience, did you choose the option "Run Once When Journey is Activated"? my understanding is if you choose this option and activate journey in test mode, it should work. – Unais Komath Nov 20 '17 at 13:05
  • Hi Unais, I went back to the journey, set it back to Draft, updated the audience to Run once, saved it, put it back in test and nothing appears to happen. There are definitely people in the Data Extension, the Data Extension is linked into Contact Builder as an Attribute group. I have checked the Entry Event History, it says that the Journey ran today but 0 entries were evaluated and 0 were entered. The Entry Event is schedule to run every hour, previously it was paused. I feel like I am running out of options to toggle. Any other suggestions? Thanks – KerryT Nov 23 '17 at 13:09
  • You have to first put the journey in test mode and then inject the audience into data extension. That's how At least it works with automation audience and we never had issues. Not sure how different it is for email audience – Unais Komath Nov 23 '17 at 13:14

Test Mode really only simulates the decision logic of the journey. From my own personal experience it's rather useless - if you are wanting to properly test your journey then build a test audience to match any criteria or decision logic and inject them into the journey. You may want to decrease the wait duration to minutes along your journey.

The least troublesome success I've had making journeys work is to use the Audience entry, and select the Automation Audience (create your automation first with your SQL selection for the journey entry).

When you activate your journey it automatically adds an Audience refresh widget to the automation.

If you do decide to use the Email Studio audience then you will need a Fire Event in your automation to trigger off the journey.

I have also experienced a bug after I put a journey into test mode and then took it out of test mode and then activated it. The activated Journey wouldn't inject any of the records that had been used in the test mode.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.