Monitor Braze Canvas journeys from the inbox
Canvas steps fire on entry events, delay nodes, audience splits and conditional paths. Each can drop without surfacing. Braze logs the step as executed. The customer's inbox is empty.
Telltide confirms each Canvas step reaches the inbox, in the right order, at the right time.
Why Canvas breaks quietly
The failure modes native analytics miss
Canvas analytics show aggregate metrics across hundreds or thousands of users. They do not alert when a single step fails for a single profile. That single profile is often your highest-value customer.
Delay nodes skip or miscalculate
A delay step waits for a relative time offset or an absolute timestamp. If the calculation references a null property, the delay resolves to zero and the user advances immediately. The next step's entry condition fails. The user drops out. Braze logs the delay as complete.
Audience splits reverse after edits
An audience split routes users on a custom property. An engineer renames the property. The Canvas is updated to reference the new name, but the boolean logic is accidentally inverted. Users flow to the wrong variant. Both paths report full sends.
Exception events fire too broadly
An exception event is added to exit users on a specific action. The event criteria are slightly broader than intended. Users leave the Canvas before the email step fires. The Canvas is working as configured. The customer never sees the email.
Update-user steps overwrite trigger properties
A Canvas step updates a user attribute. The next step triggers on that attribute equalling a value. The update writes a different value than expected. The trigger never fires. Braze logs the update as successful and the trigger as not met.
Liquid templates reference missing attributes
An email step includes a Liquid block that pulls a custom attribute. The attribute is deprecated. The template renders with a blank value. Braze logs the send as delivered. The email arrives with broken personalisation.
Action-based entry stops firing
Canvas entry is triggered on a custom event. The event schema changes upstream. The Canvas sits idle. Braze reports zero new entries. No alert fires because zero entries is a valid state.
Canvas vs campaign scope
Why multi-step journeys need step-by-step confirmation
A Canvas is not a single send. It is a sequence of conditional steps. Each step depends on the state written by the previous step. One misconfiguration cascades.
Campaigns are stateless
An action-based campaign fires once when the trigger condition is met. If it fails, you know immediately because the send count is zero. Canvas steps are stateful. They inherit context from earlier steps. A failure in step three looks like a drop in conversion rate, not a send failure.
Canvas steps can skip silently
A campaign either fires or it does not. A Canvas step can be skipped because an earlier delay miscalculated, because an audience split routed the user elsewhere, or because an exception event ejected the user. Braze logs the skip. It does not alert on it.
Aggregate metrics hide single-user failures
Canvas analytics report conversion rates and send counts across the entire audience. If 999 users receive step four and one user drops out, the metrics look healthy. The dropped user might be the one who was about to convert.
How Telltide fits
A monitored profile for every Canvas path
Telltide runs alongside Braze, not inside it. You add a monitored user to the Canvas entry audience. Telltide watches the inbox for each step Braze says it sent.
Add the monitor address to your Canvas audience
Telltide gives you a unique inbox address per monitor. You create a user profile with that address, assign the custom attributes or event history the Canvas needs, and let it enter at the first step.
Set the arrival window per step
For a step with no delay, the window might be five minutes. For a 24-hour delay, the window is 24 hours plus a buffer. For Intelligent Timing, you set a wider window to account for send-time variation.
Get alerted when the inbox disagrees with Braze
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. Braze might still report the step as healthy. The alert tells you what actually reached the inbox.
Monitoring specific Canvas components
Delay nodes, audience splits and variant paths
Each Canvas component has its own monitoring considerations. Here is how to set up Telltide for the components that break most often.
Match the arrival window to the delay duration
A Canvas with a 48-hour delay needs a 48-hour arrival window plus a 30-minute buffer. If the email arrives early, the delay was skipped. If it arrives late, something downstream held it up. Either case fires an alert.
Monitor each audience-split variant separately
If a Canvas splits users into two paths based on a property value, create two monitors. Each monitor gets a unique user profile with the property that qualifies it for one path. If one path stops sending, you know which variant broke.
Watch the step after an update-user action
If a Canvas includes an update-user step followed by a trigger that depends on the updated value, monitor the email step that follows the trigger. If the update writes the wrong value, the trigger will not fire, and the monitor will catch the missing email.
Fire entry events from a test harness
For a Canvas that enters on a custom event, trigger the event from a script or API call on a schedule. The monitored profile receives the event, enters the Canvas, and Telltide confirms the first step fires. If the event schema changes and entry stops, the monitor alerts within 15 minutes.
Canvas observability vs native analytics
What Braze shows, and what it cannot
Braze Canvas analytics are detailed. They show every step, every conversion, every exit. What they cannot show is whether the email that Braze logged as delivered actually arrived in the shape you intended.
Braze reports delivery, not inbox arrival
When Braze logs a send as delivered, it means the receiving mail server accepted the message. It does not confirm inbox placement, spam filtering, or correct rendering. Inbox-side monitoring closes that gap.
Canvas exits are logged, not alerted
When a user exits a Canvas early, Braze logs the exit reason. It does not alert you that the exit happened. If the exit was caused by a misconfigured exception event, you will not know until you actively review the exit logs.
Liquid errors render silently
When a Liquid template references a missing attribute, Braze renders the block as blank. The email is logged as delivered. The customer 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 Canvas monitoring context and how it fits with other journey types.
- Monitor Braze: the parent guide covering all Braze send surfaces.
- Triggered flow: how entry events and conditional logic interact across platforms.
- Email monitoring tools compared: where native analytics end and independent monitoring picks up.
FAQ
Common questions about Canvas monitoring
What Canvas failure modes does inbox-side monitoring catch?
Delay nodes that skip or miscalculate, audience splits that route incorrectly after a property rename, exception events that fire too broadly, and update-user steps that write the wrong values. Braze logs each step as executed. The inbox tells you whether the email actually arrived.
How do I monitor a Canvas with multiple delay steps?
Set the arrival window in Telltide to match the cumulative delay duration. If a Canvas includes a 24-hour delay followed by a 12-hour delay, the monitor expects the email 36 hours after entry. If the email arrives early or late, the alert tells you which delay node broke.
Can I monitor Canvas variants independently?
Yes. Create a separate monitor for each variant path. Each monitor gets a unique inbox address. You build a user profile for each address with the properties that qualify it for one variant. If one path stops sending, you know immediately which variant is affected.
Do I need Braze API access to monitor a Canvas?
No. Telltide operates independently of your Braze workspace. You add the Telltide monitoring address as a user profile in the Canvas entry audience. The Canvas treats it as a normal user. Telltide watches the inbox for the sends Braze logs.
Start watching your Canvas journeys
One monitor free. Paid plans from $49 USD per month. Set up takes about two minutes.
Braze and Canvas are registered trademarks of Braze, Inc. Telltide is an independent monitoring service and is not affiliated with, endorsed by, or sponsored by Braze.