Is there a way to set a most recent timestamp for each record of event data in Audience Build

[NickMannion]

Hi Adobe Community,

So my company uses RTCDP and CJA. So for some datasets, we bring them in as events so that they can be used in CJA. However, for audience building purposes, we don't really need the data as events. I have an instance where I just want to most recent record of data for every customer number that qualifies for my audience. I am wondering if there is a way to set the timestamp or somethign so that it's just giving me the most up to date record for each customer. I don't want to set the criteria and have it include a customer that used to qualify but does not qualify anymore.

Thanks,

Nick

[KumarRishii]

To ensure your audience in RTCDP only includes customers who currently qualify (based on the most recent record):

➤Use a Profile dataset (not an Event dataset) — it keeps only the latest record per customer.

 ➤If using Event datasets, you’ll need to:
-Filter on recent timestamps (not perfect),
-Or pre-process your data to send only the latest record (e.g., add is_latest = true).

I will suggest you to use a separate Profile dataset for audience building, and keep the Event dataset for CJA use.

[Michael_Soprano]

So you have multiple events with the same eventType and you want most recent one?

Could you explain a little bit more

Computed Attributes?

[NickMannion]

Hey Michael,

Yeah, the event that we will receive at any given time will be the same type of action. So, for example, the event might be like a customer's loyalty score changed. In CJA, we might want to track the journey of a customer's loyalty score to see what helped it improve. However, in RTCDP, for our campaign, we just care about if the customers latest loyalty score is below a 50 for our new loyalty campaign. So, I need to figure out a way to set an exclusion that gives me latest loyalty score < 50. Does that make sense?

[NickMannion]

And since a customer's loyalty score can stay the same for months but change at any given time, there's not really a good way to use timestamp to do this