are you looking for profiles which have an upcoming subscription end date which is N days from current date?

If you bring in all three events into a single string field then you can only perform the operations of contains or equals.   Segments ideally are using event Types to create event patterns to create an audience.   Another option is the data is written into the Adobe data lake and data distiller is ...

Hello @Harveer_SinghGi1 , I would recommend using each event as it own sentEvent action into the Adobe Experience Platform.  This will make things easier for both segmentation and evaluation in CJA. Is the main reason to reduce the number of sendEvent calls which is being performed?

@DavidRoss91 @jlasso71  We need to consider the data processing of components and timing. The profile attribute can be evaluated in the edge segmentation, but the following is a process on how it must flow. Data ingestion batch > data directed to datalake > data prompted to profile > segmentation ev...

@jlasso71  Edge segmentation can be validated using the edge API as noted in the documentation below. https://developer.adobe.com/data-collection-apis/docs/endpoints/interact/ A profile only attribute is edge eligible for segment evaluation.https://experienceleague.adobe.com/en/docs/experience-platf...

The source of the profile_export_for_destination_merge_policy__XXX is all record based datasets which have been marked for profile.

Hello @Indra  The profile_export_for_destination_merge_policy is updated on periodic basis as profile attributes are updated. The Profile_Snapshot is updated 1 x / day after the segmentation evaluation job completes.

Hello @SaurabhCh3  if you have data in dataSet A under the path of _abc.phone.number.number I would create an a query similar to the following.  Each object should be represented by a struct. insert into dataSetB select struct(              struct(              struct(          (x.number as number) ...

@SahuSa1 Can I ask why the source is producing duplicate rows of data with the latest timestamp? If the data is not changing why is the data being re-ingested?

The merge policy has an impact on the profile store.  What is the use case you are attempting to achieve with audiences of two different merge policies.