Hi kyriakosgg
It sounds like the core issue is related to the wait periods before each Audience Path, not the Audience Path logic itself.
For example, if Email #1 sends at 10:00 AM and you only have a 1-hour wait before the Audience Path for Email #2, Braze will evaluate the “Opened Email #1” condition only based on opens that happened during that first hour. Anyone who opens after 11:00 AM won’t be routed correctly because they’ve already passed the evaluation point.
Also, if users reach an Audience Path immediately-meaning there’s no wait before the path-Braze will filter them instantly, long before they’ve had a realistic chance to open the previous email.
With your specific use case, it’s also important to note that the Audience Path approach will never produce matching or expected audience counts. Users can open an email days, weeks, or even months later. So if your wait periods are configured in days, and someone opens Email #1 two months later, the filter will never capture that behavior-Braze only checks the condition at the moment the user reaches that node.
If you’re using Opened/Clicked Step filters, this is expected behavior: Braze does not continuously re-check conditions after the user moves past the Audience Path.
To help troubleshoot properly, could you confirm the exact wait periods configured before Emails 2, 3, and 4?
Thank you very much for your input! As a general rule of thumb, and for this specific campaign, we basically wanted to send 1 email per 1 week, so the Delays between, and before each audience path, is set to 1 week.
After looking into it further, I can have a specific Calendar date set instead of Duration to X amount of Days/Weeks etc. Would this be better for the implementation of the campaign described above? Also, the kpi are measured for the first 3 days after being sent.
