with the case noted above since the segment was created after the event occurred, the streaming segment would be evaluated by the batch_segmentation process.
Since event occurred before the segment was created I do not believe it would be realized in the segment. If the event occurs after the seg...
Description - Provide visibility of the active user connection(s) to the AEP datalake.
Why is this feature important to you - Feature is important for administration of the AEP sandbox to understand what the active connections to the datalake
How would you like the feature to work - Provide an API ...
Hi @Michael_Soprano
The way you can think of streaming segment is the evaluation of the segment will occur on the incoming hit of data.
If data is ingested for the profile the segment will evaluated the profile to determine the qualification for the segment. The streaming segment would be ev...
Hello @SaravananKa
You can use the /GET Profile Entity API to return the segment membership of a profile.
https://experienceleague.adobe.com/en/docs/experience-platform/profile/api/entities.
example:
curl -X GET \'https://platform.adobe.io/data/core/ups/access/entities?schema.name=_xdm.conte...
Hi @RyanMoravick
There are few way to get at the audience.
You can build an initial audience where there is at least 1 purchase event and then build exclusion logic of when there is more than 1 purchase event.
you could also use a computed attribute to find the most recent purchase event to...
Hello @Dave_Hamel_2024
Ideally you would want to have a different data Stream id for each environment. You 'could' set the data collection propertry in DEV, TEST, PROD to write to the same dataStream, but this could lead to downstream confusion.