Expand my Community achievements bar.

Your voice matters! Help shape the future of Adobe Journey Optimizer by sharing your feedback.

Best practice in doing unit testing of AJO journeys which are highly dependent on read audience activity which contains queries to AEP Segments

Avatar

Level 1

Hi Team 


Today in our AJO journey testing, we are highly dependent on Profile snapshot update which usually takes 24 hours 

 

We can’t use the Test mode functionality of AJO since we are using Read audience activity which is querying the profile segments 

 

Can anyone from the community please suggest the best approach where we can skip the 24 hour wait of Profile update 

 

with regards 

Richa Chaubey 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

4 Replies

Avatar

Community Advisor

Hi @richachaubey90 

 

I will say the best approach is the test profiles. You can turn an existing profile into a test profile: you can update profiles attributes in the same way as when you create a profile.

 

A simple way to do this is by using an Update Profile action activity in a journey and change the testProfile boolean field from false to true.

 

Your journey will be composed of a Read Audience and an Update Profile activity. You first need to create an audience targeting the profiles you want to turn into test profiles.

Once it's done, AJO test mode You can now go to your draft journey, enable test mode, and test the journey safely only on the test profiles you have designated.

Create a Test Profile 

Thanks,

David



David Kangni

Avatar

Level 1

@DavidKangni Thank you so much for your response. 
If suppose, I don’t enable the journey in test mode and just create test profiles can I still run the journey 

Based on my understanding, The test mode skips the read audience activity.

As Read audience activity handles required segmentation logic in my journeys

Avatar

Community Advisor

The test mode will not send to your audience but it will allow you to use a profile who qualified for this audience and have the flag testprofile = true to test your journey.

 

Hope it helps.

Thanks,

David



David Kangni

Avatar

Level 4

The purpose of this testing is to verify whether the profiles meet the defined rules and match the intended audience. I recommend conducting this testing in your DEV/QE sandbox using the following approach:

  • Since the final launch journey relies on a batch audience, which requires a 24-hour evaluation period, this may slow down your testing.
  • To accelerate the process, create a copy of the audience with the same rules but set the evaluation type to streaming.
  • Duplicate the journey, and in the test version, replace Read Audience with Audience Qualification.
  • Publish the test journey and ingest test profiles that meet the criteria to validate the expected outcomes.
  • Once all test cases are successfully validated, deploy the final journey to production using the batch audience and the original Read Audience setup.

Hope this helps to streamline your testing process!