Monitor Salesforce Marketing Cloud journeys for missed sends
Journey Builder steps fire on entry sources, wait activities, decision splits and conditional logic. Any component can drop without surfacing an error. Marketing Cloud logs the activity as complete. The customer's inbox stays empty.
Telltide confirms each send activity reaches the inbox, in the right order, within the expected window.
What breaks quietly
Why Journey Builder journeys fail without alerting
Journey Builder analytics show entry counts and activity progression. They do not alert when a contact never enters because the entry source changed, or when a wait-until condition times out.
Entry source stops firing
A journey enters on a data extension update or API event. An engineer updates the event schema or renames a field. The entry source stops matching. Zero contacts enter. Journey Builder logs zero as normal. No alert fires.
Wait-until condition times out
A wait activity holds contacts until an attribute updates. The attribute never updates for a subset. The timeout passes. Contacts exit early. Journey Builder logs the timeout as expected.
Decision split routes everyone to the wrong path
A decision split checks a data extension field. The field is renamed. The logic references the old name. All contacts fail the condition and route to default. Both paths report sends. No error is flagged.
AMPscript syntax breaks the email content
A send activity includes AMPscript pulling data from a data extension. The extension is deprecated. The script throws a runtime error. Journey Builder logs the send as delivered. The email arrives with blank personalisation.
Update contact activity overwrites the next input
An update contact activity writes a new value to a subscriber attribute. The next decision split depends on that attribute equalling a specific value. The update writes a different value. The split routes incorrectly. Both log as successful.
Send throttle holds back the entire batch
A send activity throttles to 10,000 contacts per hour. A batch contains 50,000. The first 10,000 send on time. The remainder queue. If the queue expires, contacts exit without the email. Journey Builder logs the expiry.
Real operator pattern
When scheduled sends arrive late and the symptom is subtle
A broadcaster ran a Saturday-morning newsletter to 80,000 subscribers through Journey Builder. The platform logged full delivery at the scheduled time. The first hour passed with no inbox arrivals. The symptom was not an error event, but the absence of the expected send.
Late arrival in the first 30 minutes is usually a scheduling issue
When an email arrives in the first half hour but later than expected, the cause is often a timezone miscalculation or Einstein Send Time Optimization shift. Genuine breakage shows up as no arrival, or arrival well outside the window.
Scheduled monitoring catches the absence before customers notice
The absence of the expected send is harder to spot than a delivery error in Email Studio. Inbox-side monitoring fires a test contact through the journey on a cadence. If the send activity does not reach the inbox within the window, an alert fires.
Journey Builder analytics will not flag low entry counts as broken
When an entry source stops matching and entry drops to zero, Journey Builder treats that as valid state. There is no threshold for alerting on low entry volume. Inbox-side monitoring confirms a test contact enters and receives the first send on schedule.
How Telltide fits
A monitored contact for every journey path
Telltide runs alongside Salesforce Marketing Cloud. You add a test contact to the journey entry source. Telltide watches the inbox for the sends Journey Builder says it made.
Add the monitor address to your journey entry source
Telltide gives you a unique inbox address per monitor. Create a contact record with that address, populate the data extension fields or subscriber attributes the journey needs, and let it enter at the first activity. For API-triggered journeys, fire the entry event from Automation Studio or an external script on schedule.
Set the arrival window per send activity
For a send activity with no wait, the window might be five minutes. For a 24-hour wait activity, the window is 24 hours plus a buffer. For Einstein Send Time Optimization, set a wider window to account for send-time variation.
Get alerted when the inbox disagrees with Marketing Cloud
If the email does not arrive in the window, an alert fires. If it arrives twice, an alert fires. If the content deviates from the reference template, an alert fires. Journey Builder might still report the activity as executed. The alert tells you what reached the inbox.
Monitoring specific Journey Builder components
Entry sources, wait activities and decision splits
Each Journey Builder component has its own monitoring considerations. Here is how to set up Telltide for the components that break most often in multi-step journeys.
Fire the entry event from Automation Studio on schedule
For a journey that enters on data extension row insert or API event, trigger the entry action from a scheduled script. The monitored contact receives the event, enters the journey, and Telltide confirms the first send activity fires. If entry stops, the monitor alerts within 15 minutes.
Match the arrival window to the wait duration
A journey with a 48-hour wait activity needs a 48-hour arrival window plus 30-minute buffer. Early arrival means the wait was skipped. Late arrival means something downstream held it up. Either fires an alert.
Monitor each decision split path separately
If a journey splits contacts on a subscriber attribute or data extension field, create a separate monitor for each path. Each monitor gets a unique contact record with the field value qualifying it for one path. If one path stops sending, you know which branch broke.
Watch the send activity after an update contact step
If a journey includes an update contact activity followed by a decision split depending on the updated field, monitor the send activity that follows the split. If the update writes the wrong value, the split routes incorrectly, and the monitor catches the misrouted email.
Journey observability vs native analytics
What Journey Builder analytics show, and what they cannot
Journey Builder analytics show every activity, every goal conversion, every exit. What they cannot show is whether the email that Journey Builder logged as sent actually arrived in the inbox in the shape you intended.
Journey Builder reports send completion, not inbox arrival
When Journey Builder logs a send activity as complete, it means Email Studio handed the message to the mail transfer agent. It does not confirm inbox placement, spam filtering, or correct rendering. Inbox-side monitoring closes that gap.
Exit events are logged, not alerted
When a contact exits a journey early due to a goal conversion or timeout, Journey Builder logs the exit reason. It does not alert you. If the exit was caused by a misconfigured wait-until condition, you will not know until you review the journey reports.
AMPscript errors render silently
When AMPscript references a missing data extension field, Journey Builder renders the block as blank. The email is logged as sent. The contact receives broken content. Telltide compares the arrived email against a reference and alerts on structural deviation.
Pair it with
Concepts and related monitoring guides
The pages below cover the broader Marketing Cloud monitoring context and how it fits with other lifecycle journey types.
- Journey Builder monitoring: the parent guide covering all Journey Builder send surfaces.
- Journey step: what constitutes a step and why each one needs independent confirmation.
- How to audit a lifecycle journey: the process for reviewing multi-step journeys before they break.
FAQ
Common questions about monitoring Journey Builder journeys
What causes a Journey Builder send activity to drop without alerting?
Entry source failures, AMPscript syntax errors in the email content, decision split criteria that exclude everyone, wait-until conditions that timeout, or missing data extension fields. Journey Builder logs each component as executed or not met. The inbox tells you whether the email actually arrived.
How do I monitor a journey with a 48-hour wait activity?
Set the monitor's arrival window to 48 hours plus a 30-minute buffer. If the email arrives early, the wait was skipped. If it arrives late, something downstream held it up. Either case triggers an alert.
Can I monitor multiple journey paths in one Journey Builder flow?
Yes. Create a separate monitor for each decision split path. Each gets a unique inbox address and a contact record with the data extension fields that route it to one path. If one path stops sending, you know immediately which decision branch broke.
What happens when an entry source stops firing and the journey goes idle?
A scheduled test event fires the entry action from Automation Studio or an external script. The monitored contact enters the journey. If the entry source change breaks entry, the monitor catches the missing email within 15 minutes.
Start watching your Journey Builder journeys
One monitor free. Paid plans from $49 USD per month. Set up takes about two minutes.