Braze Canvas: Complete Guide
Quick Summary:
Canvas is Braze's multi-step, multi-channel journey builder -- the equivalent of Klaviyo Flows or HubSpot Workflows -- letting you orchestrate branching, behavior-triggered customer journeys across push, email, SMS, and in-app messaging.
What Is Braze Canvas?
Canvas is Braze's journey orchestration tool, letting you build multi-step, branching customer journeys that can span multiple messaging channels within a single connected flow. Where a Campaign handles a simpler, single-step send, Canvas is built for genuinely complex orchestration -- welcome series, lifecycle nurture, re-engagement flows -- with decision splits, delays, and channel switching built into one journey definition.
Canvas vs Campaign
| Consideration | Campaign | Canvas |
|---|---|---|
| Structure | Single-step or simple scheduled send | Multi-step, branching journey |
| Best for | One-time or recurring simple sends | Complex, multi-touch orchestration |
| Channels per send | Typically one channel | Can span multiple channels within one journey |
| Personalization depth | Standard merge fields | Entry properties carried through the full journey |
Core Building Blocks
Entry Sources: A Canvas can be entered via segment membership, a custom event, an API-triggered entry, or a recurring schedule -- choosing the right entry source is the first real design decision for any journey.
Message Steps: Individual send steps within the journey, which can use any supported channel (push, email, SMS, in-app, webhook) at each point in the flow.
Decision Splits: Branching logic based on user behavior, segment membership, or random A/B allocation, letting different users take genuinely different paths through the same journey.
Delays: Timed waits between steps, letting a journey space out touchpoints appropriately rather than sending everything at once.
A Simple Welcome Canvas Structure
Entry: Segment membership (New Users) | v Message Step: Welcome push notification | v Delay: 2 days | v Decision Split: Did they open the app? |-- Yes --> Message Step: Feature highlight email |-- No --> Message Step: Re-engagement push
Common Canvas Journey Patterns
Certain journey structures come up repeatedly across Braze implementations, and understanding these common patterns helps when designing a new Canvas rather than building from a blank slate every time.
Welcome/Onboarding Series: Entered on account creation or first app open, guiding new users through key product features over their first days, often with decision splits based on which features they've actually engaged with.
Abandonment Recovery: Entered via a custom event like cart abandonment or incomplete signup, with a time delay before the first message and often an escalating incentive structure across subsequent steps if the user still hasn't converted.
Re-engagement/Win-back: Entered via a segment of users who've gone inactive for a defined period, typically testing different message approaches to see what successfully brings dormant users back.
Lifecycle-Stage Nurture: Ongoing journeys tied to a user's current lifecycle stage (trial, active subscriber, at-risk), often re-evaluating and potentially re-routing users as their stage changes over time.
Canvas Performance Optimization
Beyond just building a functioning Canvas, a few practices genuinely affect how well a journey performs over time.
Monitor step-level drop-off, not just overall conversion: A Canvas with poor overall conversion often has one specific step where most of the drop-off actually happens -- fixing that one step is usually more effective than redesigning the entire journey.
Revisit entry criteria periodically: A Canvas that performed well at launch can degrade if the entry segment definition becomes stale relative to how your actual user base has evolved -- periodic review keeps the audience genuinely relevant.
Avoid over-messaging within a single journey: More touchpoints isn't automatically better -- a Canvas that message users too frequently within a short window often sees rising unsubscribe or opt-out rates that outweigh any marginal conversion lift from the extra touchpoints.
How to Build One
Define your entry source based on the behavior or audience that should trigger this journey.
Map out the journey structure -- steps, delays, and decision points -- before building in the UI.
Add message steps for each channel touchpoint, using entry properties for personalization where relevant.
Configure decision splits for any behavior-based branching your journey needs.
Set a goal conversion event to measure actual journey effectiveness, not just completion rate.
Test with a draft or limited audience before activating for your full target segment.
A Real-World Example
A mobile app wants to re-engage users who downloaded the app but never completed onboarding. A Canvas entered via a custom event ("App Installed") sends a welcome push immediately, waits a day, then checks via decision split whether the user completed onboarding. Users who did are routed into a feature-highlight email sequence; users who didn't receive a more direct re-engagement push with a specific onboarding completion incentive. Canvas's step-level reporting shows exactly what percentage of users are dropping off at the onboarding check, giving the team a concrete number to improve rather than a vague sense that "engagement could be better."
🚫 Common Mistake
Editing a live Canvas that's currently enrolling and progressing real users without testing the change first. A modification that seems minor can affect users mid-journey in unexpected ways -- always validate changes in a draft or duplicate Canvas before touching one that's actively live.
💡 Pro Tip
Set a goal conversion event on every meaningful Canvas, not just completion tracking -- knowing how many users finished the journey tells you less than knowing how many actually achieved the outcome the journey was built to drive.
Frequently Asked Questions
What\'s the difference between a Canvas and a Campaign in Braze?
A Campaign is a single-step or simple scheduled/triggered message send; a Canvas is a multi-step, branching journey with delays, decision splits, and multiple channels -- the equivalent of a Flow in Klaviyo or a Workflow in HubSpot. Canvas is where genuinely complex, multi-touch orchestration lives.
What entry sources can trigger a Canvas?
Canvases can be entered via a segment (audience-based entry), a custom event, an API-triggered entry, or on a recurring schedule -- giving flexibility for both behavior-driven and scheduled journey types.
Can a single Canvas span multiple channels, like email and push?
Yes, this is one of Canvas's core strengths -- a single journey definition can route users through email, push, SMS, and in-app messaging steps, choosing the right channel at each step of the journey.
What\'s a Canvas trigger send, and how is it different from a scheduled step?
A trigger send fires a message step immediately based on a real-time event (like a cart abandonment), while a scheduled step waits a defined delay before executing -- the same distinction as immediate vs. delayed steps in other platforms' flow builders.
Can Canvas branch users down different paths based on their behavior?
Yes, decision split steps let a Canvas route users differently based on whether they performed an action, met a segment condition, or based on a random A/B split for testing.
Does Canvas support multivariate testing, not just simple A/B splits?
Yes, Canvas supports testing multiple message variations within a single journey step, letting you optimize content beyond a simple two-way split.
Can a user re-enter a Canvas they\'ve already completed?
Re-entry behavior is configurable per Canvas -- some journeys (like a one-time welcome series) should block re-entry, while others (like a recurring engagement nudge) may need to allow it.
What does Canvas reporting actually show?
Canvas analytics show step-by-step conversion and drop-off, letting you see exactly where users are exiting the journey or failing to progress, not just overall campaign-level performance.
Can Canvas entry properties be used for personalization within the journey?
Yes, properties captured at Canvas entry (like the specific product that triggered a cart abandonment entry) can be referenced throughout the journey's messaging, keeping content relevant to why the user actually entered.
Why might a Canvas appear \'broken\' or stop progressing users through steps?
Common causes include a misconfigured entry condition no longer matching any users, a decision split with no valid path for certain users, or an API-dependent step failing silently -- Canvas reporting and step-level analytics are the first place to look when troubleshooting.
Can Canvas steps call external APIs mid-journey?
Yes, via webhook steps, a Canvas can call external systems mid-journey, similar in concept to custom code actions in HubSpot Operations Hub, extending journey logic beyond Braze's native capability.
Is there a limit to how many steps a single Canvas can have?
There's no small, restrictive step limit for reasonable journey complexity, though extremely long or deeply nested journeys become harder to maintain and debug regardless of technical limits -- simpler, well-organized journeys are usually more effective than maximally complex ones.
Can Canvas be paused or edited after it\'s already live and actively enrolling users?
Yes, though editing a live Canvas requires care -- changes can affect users currently mid-journey, so testing changes in a draft or duplicate Canvas before modifying a live one is the safer practice.
Does Canvas support goal conversion tracking?
Yes, you can define a goal event for a Canvas, letting reporting show what percentage of entrants actually achieved the intended outcome (like completing a purchase), not just how many completed the journey steps.