Braze Certified Marketer common mistakes
Braze Certified Marketer · Understand the traps and how to avoid them.
Treating every message as a one-off campaign and never setting up Canvas or scheduled recurring sends for lifecycle moments, so the candidate cannot explain when to use a campaign versus a Canvas.
Candidates often study channels in isolation (email, push, in-app) and memorize feature lists instead of learning the decision logic that maps a business goal to the right orchestration primitive.
What to do instead
Build a one-page decision table: single blast to a defined segment, time-based recurring send, and multi-step journey with entry criteria and exit rules. For each of ten sample goals, write which primitive you would pick and the two reasons why.
Designing Canvas journeys that let users re-enter the same path repeatedly or that lack exit criteria, then being unable to answer questions about suppressing duplicate sends.
Entry schedules, re-eligibility, and exit rules are configuration details that are easy to skim; candidates focus on message content and skip the flow-control settings that determine who actually receives what.
What to do instead
For every practice Canvas, write down entry audience, re-entry setting, exit criteria, and the expected behavior for a user who converts mid-journey. Trace one sample user step by step on paper before answering questions.
Confusing a Canvas step delay with a send-time window or with Intelligent Timing, and choosing the wrong option when a scenario asks when a message will actually be delivered.
The three controls sound similar and all relate to timing, so candidates pattern-match on the word 'time' rather than on what each control actually governs.
What to do instead
Memorize one distinguishing sentence per control: step delay controls when the next step opens, send-time windows restrict delivery to allowed hours, and Intelligent Timing picks a per-user predicted optimal hour. Then answer five timing scenarios and justify each choice with that sentence.
Assuming a message sent from a Canvas automatically respects frequency capping, quiet hours, or global holdouts without verifying the settings, and answering scenario questions as if those protections are always on.
Candidates overgeneralize from the platform's safety features and do not check which controls are opt-in per message or per workspace.
What to do instead
Create a checklist of send-level and workspace-level controls and mark each as on by default, off by default, or configurable. Rehearse the scenario where a promotional push must be suppressed during a user's quiet hours and state exactly which setting enforces it.
Choosing a channel by habit (usually email) instead of by user reachability and urgency, so recommendations ignore push opt-in status, in-app context, or SMS consent.
Candidates have the deepest personal familiarity with email and default to it, while exam scenarios are deliberately written so the obvious channel is the wrong one for the user's state.
What to do instead
For each scenario, first classify the user's channel eligibility and the message urgency, then select the channel. Practice writing a one-line rationale that names eligibility, urgency, and fallback channel.
Treating segmentation as a static list and never considering that segment membership is evaluated at send time, so the candidate mispredicts who receives a scheduled message.
In everyday marketing work, lists are often exported and frozen; the exam tests dynamic evaluation, which behaves differently from an exported list.
What to do instead
Work through a scenario where a user joins a segment between scheduling and send time, and state who receives the message and why. Repeat with a user who leaves the segment, and note the difference between real-time and scheduled evaluation.
Ignoring Liquid personalization fallback values and default attributes, then failing questions about what renders when a profile attribute is missing or null.
Candidates learn the syntax for inserting a first name but skip the default-value filter and the behavior for empty attributes, so they cannot predict the rendered output.
What to do instead
Write and trace five Liquid snippets, each with a populated attribute, an empty attribute, and a null attribute, and record the exact rendered result. Include one conditional block that shows alternate content when the attribute is blank.
Confusing conversion events with entry events or with Canvas goals, so the candidate cannot say what triggers a user to enter a journey versus what ends it.
All three are event-based concepts and are often described loosely in study notes, which blurs the trigger-versus-outcome distinction.
What to do instead
For one Canvas, draw two columns labeled trigger and goal, place each event in the correct column, and add the exit behavior when the goal is met. Then write a two-sentence explanation of the difference in your own words.
Skipping hands-on work in a test workspace and relying only on reading, so the candidate cannot reason about where a setting lives or how a change propagates across a multi-channel journey.
The exam asks applied questions about configuration and side effects; reading creates recognition but not the causal understanding that hands-on building produces.
What to do instead
Build three small artifacts end to end: a one-step campaign with a segment, a three-step Canvas with a delay and a branch, and a message with a personalization fallback. Document the settings you changed and what each one affected.
Answering with the most feature-rich option instead of the option that satisfies the stated constraint, such as budget, timeline, or a single required channel.
Candidates equate sophistication with correctness and overlook the qualifier in the question stem that rules out the complex solution.
What to do instead
Before choosing, underline the constraint words in the stem (only, must, within, cannot) and eliminate any option that violates one. Practice ten stems by listing the constraint first, then the answer.