Examples for Decisioning Studio Go
Decisioning Studio Go works best for recurring email programs where the agent has time to learn from engagement and where your content includes enough variant options for meaningful personalization. This page groups common email use cases by fit level, with examples and guidance for each.
For an overview of how Decisioning Studio Go works, see BrazeAI Decisioning Studio Go.
Each example in this guide is labeled with one of the following fit levels:
| Fit level |
Description |
| Best fit |
The agent has enough time to learn, your audience is stable enough to show lift, and personalization can meaningfully affect engagement. Start here. |
| Supported |
The example can work well, but success depends on timing, audience size, or sequencing. Review the considerations before you commit. |
| Not recommended |
The example conflicts with how the agent learns. Choose a different program type, or talk with your customer success manager or solutions consultant about a different setup. |

note
Across all fit levels, the agent learns best when your audience generates enough engagement signal for the algorithm to detect patterns. As a working rule, target audiences in the tens of thousands of users or more, with consistent weekly send volume. The agent can run on smaller audiences, but expect a longer learning period and less reliable lift. Your customer success manager or solutions consultant can help you confirm whether a given audience is sized appropriately.
Best fit
Always-on calendared campaigns
| Topic |
Details |
| What it looks like |
A marketing calendar that runs for several months or longer, with content swapped in and out over time—for example, a rewards-member calendar, a content drop schedule, or a lifestyle or inspiration calendar. |
| Why it fits |
Long-running programs give the agent time to learn what works for different users. The audience is stable, content is refreshed regularly, and clicks are usually a meaningful indicator of engagement. |
| What to bring |
Multiple base creatives or variant sets that you’re comfortable rotating. The agent selects which version works for each user, but it needs enough variety in the options you provide. |
Evergreen programs
| Topic |
Details |
| What it looks like |
Ongoing campaigns that aren’t tied to specific dates or events—winbacks, re-engagement programs, dormant-account nudges, or milestone celebrations. |
| Why it fits |
Like calendared campaigns, the audience is dynamic but the program runs indefinitely. The agent has time to learn, the content has flexibility, and clicks are a leading indicator the agent can optimize against. |
| What to bring |
Variant options for subject line and CTA that frame the message for different motivations. Image variants help if you have them. |
Supported use cases
| Topic |
Details |
| What it looks like |
A set of emails sent over several weeks under the same promotional theme—for example, a back-to-school series or a multi-week category promotion. |
| Why it works |
If the promotion runs long enough—at least several weeks—the agent has runway to learn within the promotion. Click-through is usually a strong leading indicator of promotional engagement. |
| Considerations |
For shorter promotions, the agent may not have enough days of data to learn before the program ends. As a general guideline, the agent needs at least 10 campaign-days to develop strong recommendations. If your promotion is shorter than that, consider whether an evergreen program could carry the learning instead, then apply what you learn to the next promotion. |
Action- or event-driven journeys
| Topic |
Details |
| What it looks like |
A single email or sequence triggered by a customer action—cart abandonment, browse abandonment, or post-purchase follow-up. |
| Why it works |
Triggers create a clean entry point. If the journey is recurring and audience volume is consistent, the agent can learn which content works for which users. |
| Considerations |
Timing matters. If the email must go out within minutes of the trigger event, work with your customer success manager or solutions consultant to confirm the agent’s send schedule is compatible. If users must receive emails in a specific order (email A before email B), you need to orchestrate audience moves yourself—the agent doesn’t sequence sends for a single user across a multi-email journey. |
Not recommended
Drip sequences
| Topic |
Details |
| What it looks like |
A multi-email sequence—for example, an onboarding tutorial—where users must receive email A, then email B, then email C in order. |
| Why it doesn’t fit |
The agent selects what to send each user based on what’s likely to drive a click for that user. It doesn’t model sequence requirements. If you need to enforce a specific order, you must orchestrate the audience yourself (moving users from segment to segment after each email), which reduces most of the benefit of using the agent. The agent also can’t independently confirm that email A succeeded before sending email B. |
| What to do instead |
Use Canvas to orchestrate the drip. If you want AI optimization within a drip, talk to your customer success manager or solutions consultant about whether Decisioning Studio Pro is a better fit. |
One-time email blasts
| Topic |
Details |
| What it looks like |
A single email sent in one blast—a Black Friday announcement, a new product launch, or a one-off corporate communication. |
| Why it doesn’t fit |
The agent needs time to learn. A single send gives it no opportunity to improve decisions before the campaign ends. By the time it has enough engagement signal to make better choices, the program is over. |
| What to do instead |
If you have an evergreen program with similar content—for example, a year-round product-announcement program—use Decisioning Studio Go there and apply what you learn to one-time sends. For a truly one-time blast, A/B testing or Intelligent Selection are better fits. |
At a glance
| Scenario |
Fit |
Key consideration |
| Always-on calendared campaigns |
Best fit |
Provide multiple base creatives or variant sets to refresh over time. |
| Evergreen programs (winbacks, re-engagement) |
Best fit |
Provide variant options that frame the same message for different motivations. |
| Multi-email promotions |
Supported |
Aim for at least 10 campaign-days of runway; shorter promotions limit learning. |
| Action- or event-driven journeys |
Supported |
Confirm send-timing requirements; you are responsible for sequence enforcement. |
| Drip sequences (onboarding tutorials) |
Not recommended |
Use Canvas for sequencing; revisit Decisioning Studio Pro for in-drip optimization. |
| One-time email blasts |
Not recommended |
Use A/B testing or Intelligent Selection instead. |
Next steps
Contact your Braze customer success manager or solutions consultant if you’re unsure whether your program is a fit. Strong signals include:
- The audience receives email regularly—at least weekly—over a window of a month or more.
- The audience is large enough to generate consistent engagement signal (tens of thousands of users is a useful starting target).
- You have at least two or three meaningful variant options to offer (subject lines, CTAs, or images that frame the message differently).
- Clicks are a leading indicator of business value for this program, not just a vanity metric.
- The segment isn’t actively used by another Canvas or campaign that would compete for the same users’ engagement.