Monitor Braze Canvas abandoned cart journeys
Abandoned cart Canvas flows enter on cart-add events, wait through delay nodes, and pull product details from custom attributes. Each step 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 cart 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 webhook payload changed, or when a delay node skips because cart data is null.
Webhook payload changes upstream
Canvas entry is triggered on a cart-add webhook from your storefront. An engineer updates the payload structure. The new payload 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 cart total
A delay step waits for a relative offset calculated from cart value. The cart total is null for users who added an item but never completed the add-to-cart flow. The delay resolves to zero. Users advance immediately. The next step's entry condition fails.
Liquid merge tag references missing product field
The email pulls product name and price from custom attributes. The attributes are deprecated after a catalog rebuild. The template renders with blank values. Braze logs the send as delivered. The email arrives with broken personalisation.
Exception event fires too broadly
An exception event ejects users who complete a purchase. The event criteria accidentally match users who viewed the cart but have not checked out. Half the audience exits before the first email. Canvas logs the exits. No broken state is flagged.
Audience split routes backward after edit
A Canvas splits users on cart value. An attribute rename updates the property reference. The boolean logic is accidentally inverted. High-value carts receive the low-value variant. Both paths report full sends.
Update-user step overwrites the cart ID
A Canvas step updates a custom attribute. The next step triggers on that attribute matching a specific cart identifier. The update writes a different value than expected. The trigger never fires. Braze logs the update as successful.
How Telltide fits
A monitored profile for every cart-recovery 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 cart-add 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 4-hour cart-delay, the window is 4 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.
Real breakage pattern
When scheduled sends arrive late in the first 30 minutes
Late arrival in the first half-hour of a scheduled window is almost always a scheduling or timezone issue, not a genuine Canvas breakage. If your monitor fires an alert at the 10-minute mark but the email shows up at 28 minutes, that is the kind of false positive that wastes time.
Set realistic buffers for scheduled sends
A Canvas scheduled to send 4 hours after cart-add might arrive 4 hours and 20 minutes later due to send-queue depth or Intelligent Timing. Build a 30-minute buffer into your monitor window. If the email arrives within that buffer, it is not broken. If it arrives after, something downstream held it up.
Heartbeat mode catches the symptom before customers notice
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 cart-add webhook 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.
Monitoring specific cart-recovery components
Webhooks, delay nodes and merge tags
Each Canvas component has its own monitoring considerations. Here is how to set up Telltide for the components that break most often in cart-recovery flows.
Fire the cart-add event from a test harness
For a Canvas that enters on a cart-add webhook, 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 webhook schema changes and entry stops, the monitor alerts within 15 minutes.
Match the arrival window to the delay duration
A Canvas with a 4-hour cart-delay needs a 4-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 cart value or product category, 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 for Liquid template breakage
If a Canvas email includes merge tags that pull product name, price, or image URL from custom attributes, monitor the arrived email against a reference template. Telltide compares the structure and alerts on missing or malformed content blocks.
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.
- Abandoned browse monitoring: how the same patterns apply to product-view recovery flows.
- Flow trigger failure: what happens when the entry event stops firing.
FAQ
Common questions about monitoring abandoned cart Canvases
What causes an abandoned cart Canvas to stop firing?
Webhook payloads that change after a platform update, trigger properties that get renamed, delay nodes that timeout when cart data is null, or merge tags that reference deprecated product fields. Braze logs each step. The inbox tells you whether the email actually arrived.
How do I monitor a Canvas with a 4-hour cart-delay window?
Set the monitor arrival window to 4 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 cart-recovery variants in one Canvas?
Yes. Create a separate monitor for each variant. Each gets a unique inbox address and a user profile with the cart value or product type that routes it to one path. If one variant stops sending, you know immediately which path broke.
What happens when the cart webhook changes and the Canvas stops entering users?
A scheduled test event fires the cart-add action from a test harness. The monitored profile enters the Canvas. If the webhook schema change breaks entry, the monitor catches the missing email within 15 minutes.
Start watching your abandoned cart Canvases
One monitor free. Paid plans from $49 USD per month. Set up takes about two minutes.