toggle to use or not use profile data from the batch segment snapshot in a campaign / journey

[#1]

Use-case:

Creating journeys or campaigns that use batch created audiences for communication, while updating the profile data through streaming connections before the campaign executes.

............................

Current/Experienced Behaviour:

we have been informed that when batch segmentation occurs once a day, the current state of each profile that qualifies is written to the batch segment profile dataset snapshot.

This is then used in any journey or campaign, and for updates to the profile to take place in the dataset the segmentation must rerun. This is understandable to optimise time when sending a very

large campaign, but it would be great to have a toggle of sorts or a different read audience type that uses the ups segmentation to identify the profiles for the audience and then gather the latest

fragments, much like what you see in the identity graph / hub.

............................

Business Impact:

AEP defaults to batch segmentation , but profile updates then are affected for personalisation. Imagine a newsletter being sent via a batch audience, but in the interim the customer

has placed an order in an external system, updated their email address or first name, and this isn't reflected in the profile for the send.

............................

Improved/Expected Behaviour:

allow an option like mentioned above where we can pull the latest profile data rather than use the dataset snapshot

............................

Environment Details (version(s)/service pack, any other specifics if applicable):

none to provide

............................

Customer-name/Organization name:

Recruitment Partnership Project / MOD

............................

Screenshot (if applicable):

............................

Code package (if applicable):  

............................

[#2]

@marc_stowe_za 
use a wait in your journey. it's a work around I shared previously and Adobe officially added it into the documentation this month 

Profile refresh after wait

When a profile is parked at a Wait activity in a journey starting with a Read Audience activity, the journey automatically refreshes the profile’s attributes from the Unified Profile Service (UPS) to fetch the latest available data.

• At journey entry: Profiles use attribute values from the audience snapshot that was evaluated when the journey started.
• After a wait node: The journey performs a lookup to retrieve the latest profile data from UPS, not the older snapshot data. This means profile attributes may have changed since the journey began.

This behavior ensures that downstream activities use current profile information after a wait period. However, it may produce unexpected results if you expect the journey to use only the original snapshot data throughout execution.

Thanks,

David