Event-triggered flows are changing how CRM teams orchestrate engagement in Salesforce Marketing Cloud Next. Instead of scheduled batch sends, they fire in real time the moment a data record changes — an order placed, a cart abandoned, an engagement score crossing a threshold. The Summer '26 release raises the bar with re-entry conditions, an "Exit from a Flow" element, and content variables that need no Apex. In this hands-on guide, you'll build an event-triggered flow end to end, personalize email on the fly, and sidestep the most common mistakes. The goal: a robust, measurable journey that's ready for production.

What is an event-triggered flow in Marketing Cloud Next?

An event-triggered flow runs the instant a record changes in Data Cloud. Unlike a scheduled send, it reacts to a signal rather than a calendar. Marketing Cloud Next runs on the Salesforce Core platform's Flow engine, which finally unifies marketing automation and CRM data in one place — no more shuttling records between a separate marketing tenant and your system of record.

The marketing flow types

Marketing Cloud Next ships several flow types: scheduled journeys, event-triggered flows, segment flows, and transactional flows. For any real-time use case — welcome, win-back, confirmation — the event-triggered flow is the right tool. It listens to a Data Model Object (DMO) and starts one journey per affected record.

Prerequisites: Data Cloud, DMOs, and Data Graphs

Before you build, make sure your data is modeled correctly. Three pieces are non-negotiable:

• A primary DMO that carries the event, such as an order or a cart.
• A Data Graph that links that DMO to the contact's unified profile and attributes.
• Valid, consented email contact points to send to.

New in Summer '26: aggregation functions now work on numeric attributes pulled from a Data Graph's related data. That means you can compute an average order value or a 30-day spend total right inside the flow, with no external automation to maintain.

Configure the trigger and re-entry conditions

The trigger defines which change starts the flow. In Marketing Cloud Next you pick the DMO, the operation (create or update), and an entry condition. Summer '26 adds two decisive levers: finer trigger conditions based on fields from the primary DMO, and — most importantly — re-entry conditions that govern whether the same contact can re-enter the journey.

Here's a typical entry condition for an abandoned-cart flow, expressed in declarative logic:

Trigger: Cart__dlm (Update)
Entry condition:
  Cart.Status = 'Abandoned'
  AND Cart.TotalValue >= 50
  AND Contact.EmailOptIn = true

Re-entry rule:
  Allow re-entry: true
  Re-entry wait: 14 days
  Max entries per contact: 3

Why re-entry is a big deal

Before Summer '26, stopping a contact from getting the same reminder ten times meant suppression tables and SSJS. Now the re-entry window and the entry cap are declared in the UI. You protect send pressure without writing a single line of code.

Personalize email with content variables

The headline content feature in Summer '26 is content variables. They inject CRM data into an email without Apex — work that used to demand custom code. You declare a variable, bind it to a Data Graph field, then call it in the message body.

{{!-- Declare the content variables --}}
firstName  -> UnifiedIndividual.FirstName
lastItem   -> Cart.LastProductName
cartTotal  -> Cart.TotalValue (currency, USD)

{{!-- Use them in the template --}}
Hi {{firstName}},
your cart with {{lastItem}} is still waiting.
Total: {{cartTotal}}.

Always set fallbacks

An empty variable can break your layout or leave an awkward blank. Set a default every time — "there" for a missing first name, a generic label for a product — so every recipient gets a coherent message even when the profile is incomplete.

Handle the exit: the "Exit from a Flow" element

A journey that never closes keeps emailing people who already converted. The Exit from a Flow element, new to marketing flows, explicitly removes an individual from a given flow. Drop it right after a conversion to stop the follow-up immediately.

Decision: Has the cart been purchased?
  Yes -> Exit from a Flow (Cart Abandonment)
  No  -> Wait 24h -> Send reminder email 2

Paired with re-entry conditions, this element gives you full control over the contact's lifecycle in the journey: conditional entry, progression, and a clean exit.

The real breakthrough in Summer '26 isn't any single feature — it's the combination. Re-entry conditions, content variables, and an explicit exit finally let you build governed, real-time journeys with no Apex and no SSJS.

Test, measure, and go to production

Before you activate the flow, validate every branch in a sandbox. Create test records in the DMO, check how the content variables render, and confirm the exit element fires after conversion.

Go-live checklist

• Verify email consent on every contact point.
• Check the re-entry window to avoid over-messaging.
• Track the key metrics: entry rate, conversion rate, exits triggered.
• Document the flow logic for whoever maintains it next.

The metrics that matter

An event-triggered flow isn't judged on open rate alone. Watch the entry rate (how many contacts actually trigger the journey), the average time to conversion, and the number of exits fired by the exit element. That last number tells you whether your closing logic works: an exit rate close to your conversion rate is the sign of a healthy journey.

Once these checks pass, activate the flow and watch the first hours of production closely. Want a hand designing your Marketing Cloud Next journeys? Talk to the CGC-Agency team.

Key takeaways

Real time over batch. Event-triggered flows react to a Data Cloud change and deliver the right message at the right moment.

Governed re-entry. Summer '26 lets you cap and space re-entries with no code, protecting send pressure.

Personalization without Apex. Content variables inject CRM data into email through a simple Data Graph binding.

Clean exits. The "Exit from a Flow" element removes a converted contact and prevents pointless follow-ups.

Test before you activate. Validate every branch in a sandbox and track metrics from the first hour of production.