@Luca_Lattarini Another thing to consider is if a Purchase Order would ever change (e.g. status)?  If so, remember: Events are immutable.It will need to be ingested as a new Event Any _id strategy will need to accommodate this (e.g. concat(purchaseId + latest updated date) )

@Luca_Lattarini @AtulChavan One trick I use so I don't have to change timestamps is "order by": orderby=-timestamp&limit=10

@vkt1989 What about something like this: select struct( 'NY' as city) "_Tenant.ProfileAttributes.address", struct('VP' as role) "_Tenant.ProfileAttributes", struct('123' as customerID) "_Tenant"   OR select struct( 'NY' as city) "_Tenant.ProfileAttributes.address.city", struct('VP' as role) "_Tenant...

I connected with @ssagarnayak13 offline and I'll leave it to them to post the final solution here.   One thing to note for anyone following along: filtering on identityMap is not supported even though it is available in the UI.

@navink386520 I can imagine how this might work in CJA, but I'm still unsure this would work in Segmentation.  Have you tried it there?

@ChetanyaJain @vikash4 A small tweak: "if you have two records with the same _id, then the oldest data will be reflected when you look-up this data using queries/APIs" For time-series data the _id is used to prevent duplicates from being loaded and thus, will ignore/reject any subsequent records wit...

@Pradeep_Kumar_Srivastav Quite an interesting question there.  It has a number of challenges though as we drift away from cookies and in the AEP world since AEP has a broader view of the world (i.e. events beyond just web events).  Also, since AEP links identities such as ECID with each other, it fo...

Since you keep modifying the Segment you may need to wait for the baseline to run.   "Once streaming evaluation has been enabled, a baseline must be created (after which the segment will always be up-to-date)." https://experienceleague.adobe.com/docs/experience-platform/segmentation/api/streaming-se...