Monitor Braze Canvas abandoned browse journeys
Abandoned browse Canvas flows enter on product-view events, wait through delay nodes, and route users on custom properties. Each of those steps can drop without surfacing. Canvas reports the journey as active. The customer's inbox is empty.
Telltide confirms each step fires, in the right order, from the inbox.
What breaks quietly
Why abandoned browse Canvases fail without alerting
Canvas Analytics shows entry counts, conversion rates, and step progression. It does not alert when a single profile never enters because the product-view event schema changed, or when a delay node skips because a null property broke the calculation.
Event trigger stops firing
Canvas entry is triggered on a product-view event. An engineer updates the event schema. The new schema omits a property the Canvas entry criteria depend on. Zero new users enter. Canvas logs zero entries as normal behaviour. No alert fires.
Delay node skips on null property
A delay step waits for a relative offset calculated from a browse timestamp. The timestamp is null for users who viewed a product but never logged the full event payload. The delay resolves to zero. Users advance immediately. The next step's entry condition fails.
Exit condition fires too broadly
An exception event ejects users who complete a purchase. The event criteria accidentally match users who added to cart but have not checked out. Half the audience exits before the first email. Canvas logs the exits. No broken state is flagged.
Liquid template references missing category field
The email pulls a product category from a custom attribute. The attribute is deprecated after a catalog rebuild. The template renders with a blank value. Braze logs the send as delivered. The email arrives with broken personalisation.
Audience split routes backward after edit
A Canvas splits users on viewed-product price. An attribute rename updates the property reference. The boolean logic is accidentally inverted. High-price viewers receive the low-price variant. Both paths report full sends.
Update-user step overwrites the viewed-product ID
A Canvas step updates a custom attribute. The next step triggers on that attribute matching a specific product ID. The update writes a different value than expected. The trigger never fires. Braze logs the update as successful.
Real breakage pattern
When browse-recovery emails go missing on Saturday mornings
A broadcaster sent a Saturday-morning newsletter to 80,000 subscribers. Canvas logged full delivery. The first hour of the send window passed with no inbox arrivals. The symptom was not an error event. It was the absence of the expected send.
Late arrival is usually a scheduling issue, not a broken Canvas
When an email arrives in the first 30 minutes of a window but later than expected, the cause is often a timezone miscalculation or an Intelligent Timing shift. A genuine breakage shows up as no arrival at all, or arrival outside the configured window entirely.
Heartbeat mode catches the symptom before the support ticket
The absence of the expected send is harder to spot than a delivery error. Scheduled monitoring fires a test event on a cadence. If the Canvas does not send within the arrival window, an alert fires. The operator knows the Canvas is idle before customers notice.
Canvas Analytics will not flag zero entries as broken
When a product-view event stops firing and Canvas entry drops to zero, Canvas treats that as valid state. There is no threshold for alerting on abnormally low entry counts. Inbox-side monitoring fills the gap by confirming the test profile enters and receives the first step.
How Telltide fits
A monitored profile for every browse-abandon path
Telltide runs alongside Canvas, not inside it. You add a test user to the entry audience. Telltide watches the inbox for the sends Canvas says it made.
Add the monitor address to your Canvas entry segment
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. For action-based entry, you fire the product-view event from a test harness on a schedule.
Set the arrival window per step
For a step with no delay, the window might be five minutes. For a 24-hour browse-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 Canvas
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. Canvas might still report the step as healthy. The alert tells you what actually reached the inbox.
Monitoring specific abandon-browse components
Event triggers, delay nodes 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 in browse-recovery flows.
Fire the product-view event from a test harness
For a Canvas that enters on a product-view event, trigger the event from a scheduled script or API call. 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.
Match the arrival window to the delay duration
A Canvas with a 24-hour browse-delay needs a 24-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 variant path separately
If a Canvas splits users on product category or price, create a separate monitor for each path. Each monitor gets a unique user profile with the property that qualifies it for one variant. 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.
Canvas observability vs native analytics
What Canvas Analytics shows, and what it cannot
Canvas Analytics are detailed. They show every step, every conversion, every exit. What they cannot show is whether the email that Canvas logged as delivered actually arrived in the shape you intended.
Canvas reports delivery, not inbox arrival
When Canvas 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.
Exit events are logged, not alerted
When a user exits a Canvas early, Canvas 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, Canvas 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 Canvas send surfaces.
- Canvas monitoring: step-by-step confirmation for multi-step journeys.
- Journey step: what constitutes a step and why each one needs independent confirmation.
- Workflow monitoring in other platforms: how the same patterns apply across sending systems.
FAQ
Common questions about monitoring abandoned browse Canvases
What causes an abandoned browse Canvas to stop firing?
Event schema changes upstream, trigger properties that get renamed, audience-entry criteria that exclude more users than intended, or delay nodes that skip when a custom attribute is null. Canvas logs each component as executed or not met. The inbox tells you whether the email actually fired.
How do I monitor a Canvas with a 24-hour browse-delay window?
Set the monitor's arrival window to 24 hours 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 triggers an alert.
Can I monitor multiple browse-abandon variants in one Canvas?
Yes. Create a separate monitor for each variant. Each gets a unique inbox address and a user profile with the custom attributes that route it to one path. If one variant stops sending, you know immediately which path broke.
What happens when the product-view event changes and the Canvas stops entering users?
A scheduled test event fires the product-view action from a test harness. The monitored profile enters the Canvas. If the event schema change breaks entry, the monitor catches the missing email within 15 minutes.
Start watching your abandoned browse Canvases
One monitor free. Paid plans from $49 USD per month. Set up takes about two minutes.