Audience split
An audience split is a decision step that routes subscribers to different paths based on data or behaviour. The platform evaluates conditions and directs each subscriber down the matching branch.
Definition
What an audience split is
An audience split is a journey step that branches subscribers based on if-then logic. If a subscriber's city field is Sydney, send the Sydney-specific offer. If the subscription tier is premium, route to the premium nurture path. If engagement in the last 30 days is zero, skip the upsell sequence.
The split evaluates conditions at the moment the subscriber reaches the step. The condition might check static profile fields (location, subscription tier), calculated attributes (total spend, days since last purchase), or behavioural data (clicked the last email, visited a specific page). If the condition is true, the subscriber moves down one branch. If false, they move down another. Most platforms also support an else branch for subscribers who match none of the defined conditions.
Common failure modes
How audience splits break
Overlapping conditions
Two branches have conditions that can both be true for the same subscriber. The platform picks one branch, but the logic is ambiguous and the subscriber might receive the wrong content.
Missing else branch
A subscriber matches none of the defined conditions and there is no fallback path. The journey stops, and the subscriber receives nothing.
Data sync delay
The split checks a field that updates in an external system but syncs to the ESP on a delay. The subscriber reaches the split before the latest value has arrived, and the decision is based on stale data.
Field rename or removal
The split references a field that has been renamed or deleted. The condition evaluates as false for all subscribers, and everyone routes to the same branch regardless of actual attribute values.
Why the platform does not catch it
Split logic runs silently
The platform evaluates the split condition and routes the subscriber without logging whether the routing was correct. If the condition references a missing field, the platform does not error. It treats the field as empty or null, evaluates the condition as false, and routes the subscriber to the false branch or the else branch. The journey continues, the subscriber receives an email, and the platform reports success.
I have seen this in a welcome flow for a content subscription platform. New subscribers were supposed to split into two paths based on their chosen category preference. One Saturday morning, the category field was renamed in the CRM as part of a data-model cleanup. The journey was not updated. Every new subscriber for the next six hours hit the split, evaluated as no-match because the old field name no longer existed, and routed to the else branch. Everyone received the generic welcome email regardless of preference. The platform logged each send as successful. No alerts fired. The first signal was a support ticket asking why a subscriber who selected podcasts received the blog-focused email instead.
How monitoring catches it
Live-journey checks with known branch paths
Telltide monitors enrol test identities with known attributes into live journeys. A test identity with the Sydney location attribute enters the journey and should receive the Sydney-specific email. If the inbox instead receives the generic email, or no email at all, the split logic has failed. The monitor alerts within minutes of the breakage, before real subscribers are affected at scale.
The check is inbox-side. Telltide does not parse the platform's internal logs or validate split conditions in the platform's interface. It waits for the email to arrive and checks whether the content matches the expected branch. This catches overlapping conditions, missing else branches, and data-sync delays that would otherwise remain invisible until customer complaints surface.
Related terms
Concepts that travel with audience splits
- Journey step: the unit of work in an email journey. Splits are one type of step.
- Merge tag: often used inside content blocks on different split branches to personalise further.
- Dynamic content: an alternative to splits where branching happens inside a single email template rather than as separate journey paths.
Monitor split logic from the inbox
One monitor free. Paid plans from $49 USD per month.