Hi @Michael_Soprano , The reason you have multiple is due the merge policies which are present in the Adobe Experience Platform Environment.  The profile snapshot is run daily after the daily segmentation job.

The profile store is a different storage layer than the datalake.   Please refer to the following diagram.

@Michael_Soprano These functions are not directly in the UI, but could be done using the UI functionality for selecting arrays for targeting.

Hi @Michael_Soprano  PQL is the syntax when a segment is created from an API.  You can define values within an array attribute using the UI similar to the following screenshot.

A null value is a relational database term which is used to represent a value which does not exist in the column of the database table. If data is ingested into the Adobe Experience Platform profile store the data will be represented as the text of null or an empty string depending on the transforma...

Hello @GabrielaNa1 I would recommend reviewing the following page for date formatting functions within the PQL syntax for segmentation.  https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/pql/datetime-functions The interval function typically is used a function within the Ad...

 With the May 2025 release retention can be set within the Datalake. Please refer to the following articles. https://experienceleague.adobe.com/en/docs/experience-platform/catalog/datasets/user-guide#data-retention-policy https://experienceleague.adobe.com/en/docs/experience-platform/catalog/dataset...

Hi @stephentmerkle  If you are attempting to re-ingest data upon a new dataSet your best options could be the following:1) Use the Data Access API to export data out of platform and then re-ingest data.Data Access API 2) Using a dataSet export to a cloud based destination and then re-import the data...

Hello @AEP_guy / @DavidRoss91  When dates are used we need to ensure the data is ingested in the correct format of the field which is collecting data. https://experienceleague.adobe.com/en/docs/experience-platform/xdm/schema/field-constraints#basic-types Based upon the screenshots it does appear the...

Hello @ChanuteJo  It appears your syntax in your body is not correct.  Please update your body to include the array notation as noted below.  This will execute a single segment.[ { "segmentId": "de252a01-c4f8-473b-99ec-341db56221ca" } ] you can use the following for multiple segments in a single ...