Hi @arvG10s ,Please try belowcount(#{ExperiencePlatform.ProfileFieldGroup.profile._abc.customerAttributes.exclusionType.all(* == "EML")}) > 0

In AJO, how can I ingest and process millions of streaming events per hour for profile enrichment and split-criteria evaluation - while preserving sub-second decision latency and avoiding backpressure or throttling?

Hi @arvG10s ,Based on below reference linkshttps://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/building-advanced-conditions-journeys/syntax/collection-management-functionshttps://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/persona...

Hi @Alexis_ZaccariasO ,You can follow steps mentioned in below linkshttps://experienceleague.adobe.com/en/docs/target/using/experiences/vec/troubleshoot-composer/troubleshooting-issues-related-to-the-visual-experience-composer-vechttps://experienceleague.adobe.com/en/docs/target/using/experiences/ve...

Hi @AEPuser16 ,You can re-ingest into the same dataset if the data contains a timestamp field used in the merge policy, as it will not create entirely new records but will update existing ones based on the primary identity.Alternatively, you can create a new temporary dataset for re-ingestion and th...

Hi @montezh2001 ,I might have misunderstood. I assumed that you had multiple branches in your journey for the email, with each branch containing an individual treatment. 

How can I configure journey to route users into different content variants within a single journey based on real-time event thresholds like >10 purchases in the last 72 hours without having to create separate segments for each threshold?

Hi @itsMeTechy ,In the UI, merge policies have a user-friendly ID (human-readable name).But in the profile snapshot dataset name, you’ll often see a suffix like numbers and dash included into it (real internal identifier).Real internal identifier gets used when a snapshot is generated.You can list a...

Hi @itsMeTechy ,Yes, when multiple merge policies are defined in AEP, each profile snapshot table is created per merge policy, because each merge policy produces a different view of the unified profile. To differentiate which profile snapshot table corresponds to which merge policy, you can follow t...

Hi @Ikmo7 ,You can follow 2nd step which I have mentioned in previous reply. ThanksAnkit