AJO update profile activity

[Balrajm]

Hi All,

I have been trying to update profile using the activity in the journey at end step, so that I can use it in other journey, however the segment I have created using the profile attribute value which I am updating in the journey is not reflecting, it is still using old value for audience evaluation.

Example: I added attribute life_stage= Welcome

Created audinece : life_stage= welcome

Updated the lifestage value in the journey using update Profile activity, via test run and made value as Started.

Now when I run journey in dry run mode I am seeing a audinece still reading as 2 count for life_stage conditions.

Please let me know does audinece evaluation considers data lake data or profile store ?

[Mohan_Dugganab]

Audience evaluation is based on the data in UPS.

Kindly check if you have created the audience as of type streaming. 

Reference - https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/methods/overview 

[Balrajm]

No, I created as a batch audience.

[Mohan_Dugganab]

Kindly create it as of type streaming if you want the profile to qualify in near real time or you can wait for the daily batch job segmentation to be completed.

[Balrajm]

I created these yesterday, waited 24 hours for evaluation.

[Mayank_Gandhi]

@Balrajm Audience/segment evaluation considers the Real‑Time Customer Profile store, not the raw data lake. The data lake feeds Profile, but segmentation and journey audiences work off Profile and exports derived from it.
Journey Dry run is designed to simulate journeys without changing live data.

Recommended steps:

1. Clone the journey (optional but safer) and:
   • Turn Dry run OFF.
   • Keep Update profile: life_stage = "Started" at the end.
2. Use a test profile:
   • Make sure it currently has life_stage = "Welcome".
3. Publish and run the journey in Live mode with that test profile.
4. After the profile reaches the Update Profile node:
   • Wait ~10–15 minutes.
   • Open the profile in AEP Profile UI → check JSON:
     • Confirm life_stage is now "Started".
5. After the next batch segmentation + snapshot completes (usually overnight, or via a Run now + export if you use that operational pattern):
   • Re‑check the batch audience:
     • Your test profile should drop out of the life_stage = "Welcome" audience.
     • If you create a new audience life_stage = "Started", it should include that profile after the batch run.

[Balrajm]

Thanks you Mayank, will go through your steps and check.

[SukhVgill]

Right, you can check dry run execution logic here : https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/create-journ...