You bought the platform. You migrated your contacts. You built a welcome sequence and a re-engagement campaign. And yet, six months in, the results look suspiciously like the results you were getting from your previous email tool.
The platform isn’t the problem. The orchestration layer is.
This post is a deep-dive on Layer 2 of the 5-layer capability framework covered in the Capability-Led Approach to Marketing Automation: A Complete Planning Guide. If you’ve read that, you’ll know the orchestration layer is where triggers, logic, and sequencing live — the engine that decides who gets what, when, and under what conditions. It’s also where the gap between what automation promises and what most businesses are actually running is largest.
The Three Levels of Orchestration Maturity
Not all automation is equally automated. There’s a meaningful difference between having a marketing automation platform and using it as an automation engine.
Level 1: Broadcast + basic triggers
You’re sending campaigns to segments. You have a welcome sequence that fires when someone joins a list. Maybe an abandoned cart email triggered by a purchase event. The logic is simple: one trigger, one action, no branching. This describes the majority of SMB implementations.
Level 2: Conditional branching and multi-step sequences
Journeys fork based on behaviour. If someone opens but doesn’t click, they go one way; if they don’t open at all, they go another. Sequences run to ten or more steps. You’re starting to use filters and conditions, not just triggers. A meaningful minority of SMBs are here — usually teams with a dedicated marketing ops person or a consultant who built the flows properly.
Level 3: Full conditional logic, goal exits, dynamic content, cross-channel suppression
Contacts move through journeys based on real-time data from multiple sources. Sequences exit automatically when a goal is achieved — a purchase, a meeting booked, a score threshold hit. Content is dynamically assembled per contact. Suppression logic prevents a contact who just bought from being served a win-back offer the same day. Most SMBs aren’t here. Some enterprise teams aren’t here either.
The uncomfortable truth
Levels 1, 2, and 3 are often indistinguishable on a feature comparison grid. A platform can technically support goal exits and still require three separate flows, a custom property update, and a webhook to make it work reliably. That’s the gap this framework is designed to expose.
The Five Capabilities That Separate Level 2 from Level 3
If you want a practical lens for assessing where your orchestration really sits — or for evaluating whether a platform will get you where you need to go — these are the five capabilities that matter.
1. Date-relative triggers per contact
Not “send this campaign on the 15th of every month.” Rather: “trigger this sequence 30 days after this contact’s last purchase, relative to each contact individually.” Many platforms offer date-based sending but struggle with truly individualised date-relative logic at scale.
2. Conditional branching on multiple simultaneous data points
Level 1 branching is binary: did they open? Yes/no. Level 3 branching evaluates multiple conditions at once — purchase history AND engagement score AND acquisition source — and routes accordingly. The more conditions you need to combine, the more quickly platforms diverge in their actual usability.
3. Goal-based exits
A contact should leave a nurture sequence the moment they convert, not when they reach the end of the flow. Goal exits are the mechanism that makes this happen automatically. Without them, you’re manually managing exceptions — or worse, sending 201Care you ready to buy?201D emails to customers who bought yesterday.
4. Cross-channel suppression logic
If a contact has received three emails in four days, should they also receive an SMS today? If they’ve just converted via a paid retargeting ad, should they still be in the win-back flow? Suppression logic coordinates across channels to prevent the incoherence that makes customers feel like they’re talking to a company that doesn’t know them.
5. Sequence depth beyond five steps
This sounds obvious, but many implementations simply stop at five or six emails because that’s where the template library ends. Genuine automation for longer buying cycles — B2B nurture, high-consideration B2C purchases — requires flows that can sustain logic across weeks or months without manual intervention.
Why Most Platforms Claim Level 3 but Deliver Level 2 in Practice
Every modern marketing automation platform will tell you it supports conditional branching, goal exits and dynamic content. Most of them are technically correct.
The distinction worth drawing is between a feature existing and a feature being usable without significant technical overhead.
Goal exits might exist, but only as a workaround through a webhook and a custom field update — workable for a developer, impractical for a marketing team. Cross-channel suppression might be possible, but only if you’ve set up a unified contact record that pulls from your CRM, your e-commerce platform, and your paid media tool — which requires a data layer that most SMBs haven’t built yet.
This is why platform evaluation without a capability map produces misleading results. You end up comparing feature lists instead of asking: “What does it actually take to use this feature reliably, at our data maturity level, with our team’s technical skills?” The B2C platform selection post and B2B platform selection post in this series apply exactly this test to orchestration requirements across the most common SMB use cases.
Self-Assessment: Which Level Is Your Orchestration Actually At?
Work through these questions honestly. They’re designed to surface the gap between what your platform can theoretically do and what you’re actually running.
On triggers
- Are your automations triggered by individual contact behaviour, or by campaign sends?
- Can you trigger a sequence 30 days after a specific contact-level event — without manual intervention?
On branching
- Do your sequences fork based on more than one condition simultaneously?
- If a contact doesn’t engage with steps 1–3, does the sequence respond differently — or just keep going?
On exits
- Do contacts exit sequences automatically when they achieve a goal?
- Can you confirm that no contact in a re-engagement flow has also been a customer for the past 30 days?
On suppression
- Is there logic preventing a contact from receiving email and SMS on the same day without an explicit reason?
- Do your email flows know what your paid campaigns are doing — and vice versa?
On depth
- What’s the longest sequence currently running? How many steps?
- Were any of those steps added in the last three months — or did the flow stop getting maintained after launch?
How to score yourself
If most of your answers point to manual workarounds, campaign-level logic, or flows that stop at five steps, you’re at Level 1. Branching on single conditions with sequences beyond five steps puts you at Level 2. The full combination — goal exits, multi-point conditional logic, suppression across channels, individualised date-relative triggers — is Level 3.
Scored yourself at Level 1 or 2 despite paying for a Level 3 platform?
We can help you identify the specific gaps in your setup. Learn more about our MAP Evaluation service.
How to Move Up: The Dependency Chain
Here’s what most orchestration improvement projects get wrong: they try to build Level 2 or Level 3 logic on top of a data layer that can’t support it.
Conditional branching on multiple simultaneous data points requires that those data points exist, are clean, and are accessible in your platform. Goal exits require that goal completion events fire reliably into your MAP in real time. Cross-channel suppression requires a unified contact record that reflects channel history across email, SMS, and paid.
None of that is an orchestration problem. It’s a data layer problem. Which is why the Data Layer Audit is the prerequisite step, and the 12-month sequencing methodology in the planning guide puts data layer remediation before orchestration development for exactly this reason.
The practical sequence:
- Audit your data layer first. What contact properties do you actually have? Are they populated, consistent, and current? Which events fire reliably into your platform?
- Map your highest-value use cases to the orchestration capabilities they require. A win-back sequence for a D2C brand needs date-relative triggers and goal exits. A B2B nurture sequence needs conditional branching on firmographic and behavioural data.
- Build to the data you have, not the data you plan to have. Level 2 built on clean data outperforms Level 3 built on assumptions.
- Add complexity incrementally. Goal exits before cross-channel suppression. Suppression before full dynamic branching. Each layer of complexity requires the previous one to be stable.
Ready to Map This Against Your Stack?
If you’re already facing a renewal or suspect your current platform isn’t meeting these requirements, our MAP Evaluation for SMBs provides a structured, 4-week audit to help you decide whether to stay or switch
If you’re not sure whether your underlying infrastructure is ready to support Level 3 orchestration, the AI Strategy and Readiness Assessment will tell you.
