How to test Percentage split and Profile cap conditions in journeys? | Adobe Higher Education
Skip to main content
LuisCardenas
Level 2
September 30, 2025
Répondu

How to test Percentage split and Profile cap conditions in journeys?

The journey is triggered by a custom unitary event, the idea is to limit the volume of profiles to receive specific communications. Therefore, I want to place a profile cap condition (or a percentage split) to separate the profiles and make them advance to the correct email comm. However, I see in the documentation that to be able to test this conditions the only way to do it is with at least 1000 profiles...

 

Note: I've tested using profile cap = 1 as condition to move to alternative path when reaching the limit but the behaviour has been nothing but accurate (works sometimes but not always).

1. Is this accurate or I'm missunderstanding something here?

2. How would you test the described scenario?

 

Appreciate any help on your end.

 

CC: @Mayank_Gandhi @SatheeskannaK 

Meilleure réponse par Mayank_Gandhi

@luiscardenas 

Emulate at Scale (Recommended for Accuracy)

  • Use a test segment of >1000 profiles in a dev/sandbox environment.
  • Trigger your custom unitary event for the segment.
  • Observe distribution - results should match your split/cap logic.

2 commentaires

Mayank_Gandhi
Adobe Employee
Adobe Employee
September 30, 2025

@luiscardenas You are mostly correct. Profile caps and percentage splits are designed for journeys involving at least 1,000 profiles to ensure reliable results. If you set a cap to 1, you’ll see inconsistent behavior because the system wasn’t designed to enforce hard “single-slot” consumption. 

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/about-journey-building/condition-activity

Mayank_Gandhi
Adobe Employee
Adobe Employee
September 30, 2025

@luiscardenas 

Emulate at Scale (Recommended for Accuracy)

  • Use a test segment of >1000 profiles in a dev/sandbox environment.
  • Trigger your custom unitary event for the segment.
  • Observe distribution - results should match your split/cap logic.