Why did my scheduled Journey reach fewer users than expected based on the segment size?

When a journey uses Audience-based entry with One-time entry > Schedule for a specific day, the entry time is evaluated per user, so the launch moment and a few entry settings decide how many users actually get in.

1. What happens for users whose scheduled time has already passed

This is now an explicit setting in the entry element: Choose what happens when a user's scheduled entry time (in their local timezone) has already passed.

• No, exclude them from this journey — those users never enter. If reach is lower than the segment size, this is the most likely cause.
• Yes, let them enter immediately — those users enter right away instead of being dropped.

Check which option the journey uses before assuming users were lost.

2. Timezone option and fallback

By default entry uses the subscriber's device timezone; devices with no known timezone fall back to a configurable zone (click Change fallback to set it). Choosing Specific timezone instead gives every user the same absolute entry time.

3. Who is allowed to enter

• Existing users only (default) — only users matching the segment at launch.
• Existing + new users — later matches enter too.
• New users only — nobody enters at launch.

Event-based segments are not supported by the last two options; CSV-imported segments are static; RFM segments only admit new users after you recalculate them in Audience > RFM Segmentation.

Recommendation: for time-sensitive scheduled journeys, either activate the journey well before the earliest local start time across the target timezones, or set the already-passed option to let them enter immediately. Reach can also legitimately fall below segment size because of opt-outs, frequency capping, the global control group, or devices without a valid token.