Audience Flows in Salesforce Marketing Cloud Next: A Summer '26 Guide

One of the most consequential changes in the Summer '26 release of Salesforce Marketing Cloud Next arrived without much fanfare: the Segment Triggered Flow is gone, replaced by the Audience Flow. The rename is cosmetic. What sits underneath it is not. Until Summer '26, every orchestration you built had to be triggered by a Data Cloud segment — no exceptions. You now get four unified entry points: segment, CRM record, actionable list, and campaign. This guide walks through when to reach for each one, how to populate an Actionable List programmatically, and what to audit in your existing flows before the change quietly costs you a quarter of momentum.

What actually changed in Summer '26

Through Spring '26, audience orchestration in Marketing Cloud Next rested on one hard assumption: if you wanted to message a group of people, that group had to exist as a Data Cloud segment. That assumption forced every campaign — however trivial — through Data 360 modelling. Want to follow up with the 400 people who scanned their badge at your conference booth? Build a segment. Wait for the data team.

Summer '26 breaks the dependency. The Start element of an Audience Flow now exposes a data-source picker. The orchestration itself is unchanged; what became plural is the way people enter it. In practice, marketing teams can now launch a campaign without queuing behind the data backlog for every new audience.

The point of Summer '26 isn't more entry points. It's decoupling marketing execution speed from Data Cloud modelling speed. Any audience that doesn't need advanced segmentation logic should no longer travel through Data 360.

The four entry points, and when to use each

Segment Flow

The direct descendant of the Segment Triggered Flow. It consumes a Data Cloud segment on a schedule or in real time. Save it for audiences that genuinely need identity resolution, calculated attributes, or aggregation across multiple sources. It is the most powerful entry point and the most expensive one in delivery time.

Record Query Flow

Queries CRM objects directly — Contact, Lead, Account, or your custom objects — with no Data Cloud hop. This is the natural fit for lifecycle use cases driven by the CRM: contract renewals, opportunity follow-ups, post-service notifications.

List Flow

Runs off an Actionable List: a static list of members you populate by import, by signup form, or by API. It is the fastest entry point to stand up, and it unblocks the majority of ad-hoc requests that land on a marketing ops team.

Campaign Flow

Takes Salesforce campaign members as its source. Particularly valuable in B2B, where the campaign is the shared unit of coordination between marketing and sales.

Entry point	Source	Typical use case	Needs Data Cloud
Segment Flow	Data Cloud segment	Multi-source behavioural targeting	Yes
Record Query Flow	CRM object	Contract and opportunity lifecycle	No
List Flow	Actionable List	Events, webinars, imported lists	No
Campaign Flow	Campaign Member	Sales-aligned B2B nurture	No

Populating an Actionable List by API

An Actionable List only earns its place in your stack if it fills itself. The REST call below adds members from an external system — an event platform, a badge scanner, an internal back office.

POST /services/data/v66.0/sobjects/ActionableListMember
Authorization: Bearer {access_token}
Content-Type: application/json

{
  "ActionableListId": "0LxAB0000004CvT0AU",
  "RelatedRecordId": "003AB000006h2LkYAI",
  "Source": "DreamforceBooth2026",
  "Status": "Active"
}

At volume, use the Composite API instead of looping single calls. You stay comfortably inside governor limits and the batch is handled as one unit of work:

POST /services/data/v66.0/composite/sobjects

{
  "allOrNone": false,
  "records": [
    { "attributes": {"type": "ActionableListMember"},
      "ActionableListId": "0LxAB0000004CvT0AU",
      "RelatedRecordId": "003AB000006h2LkYAI" },
    { "attributes": {"type": "ActionableListMember"},
      "ActionableListId": "0LxAB0000004CvT0AU",
      "RelatedRecordId": "003AB000006h2LmZAI" }
  ]
}

One caveat worth internalising: an Actionable List is static by design. It does not re-evaluate. If your use case needs people to trickle in continuously, a scheduled Record Query Flow is the better instrument.

Targeting precisely with a Record Query Flow

A Record Query Flow accepts conditions on the fields of the object you query. To reach contacts whose contract expires in thirty days, with no segment involved:

SELECT Id, Email, FirstName, Account.Name, Contract_End_Date__c
FROM Contact
WHERE Contract_End_Date__c = NEXT_N_DAYS:30
  AND HasOptedOutOfEmail = false
  AND Email != null
  AND Account.Segment__c IN ('Enterprise', 'Mid-Market')

Three habits are worth keeping in every query you write here. Filter opt-outs at the source rather than downstream in the flow. Drop records with no email address so they never inflate your failure metrics. And bound the business scope in the query itself, so you are not paying to process rows you will discard three steps later.

Personalising the message with Handlebars

Whichever entry point you pick, audience attributes reach the message through Handlebars. The available context differs by source, though: a List Flow exposes the related record, a Campaign Flow exposes the campaign member.

<p>Hi {{Contact.FirstName}},</p>

{{#if Contact.Contract_End_Date__c}}
  <p>Your contract is up for renewal on
  {{formatDate Contact.Contract_End_Date__c "MMMM d, yyyy"}}.</p>
{{else}}
  <p>We wanted to check in on your subscription.</p>
{{/if}}

{{#each Contact.Account.ActiveProducts}}
  <li>{{this.Name}}</li>
{{/each}}

Always preview against a record where the optional fields are empty. Half-rendered emails in production almost always trace back to an untested null.

Migrating your existing Segment Triggered Flows

The good news is that there is no migration to run. Your Segment Triggered Flows become Audience Flows using the Segment source automatically, with no downtime and nothing for you to configure.

The interesting work is the audit that follows. Of your existing Data Cloud segments, how many exist only to reproduce a static list or a single-object CRM query? In the engagements we run, that share regularly exceeds a third. Every one of those segments carries a maintenance cost and a lead time that an Actionable List or a Record Query Flow simply removes.

We suggest three passes: inventory the segments that trigger a flow, flag the ones whose logic fits in a single-object query, then rebuild the simplest cases on the new entry points before retiring the segments that no longer earn their keep.

Key takeaways

Audience Flow replaces Segment Triggered Flow. The name change is cosmetic; opening up the entry model is not. Four sources now coexist inside one orchestration.

Data Cloud is no longer a toll booth. Actionable lists, CRM queries, and campaigns let you reach an audience without Data 360 segmentation logic.

Pick the simplest entry point that solves the problem. Segments for behavioural complexity, Actionable Lists for operational speed.

Actionable Lists are static. Plan for API or form-driven population, and use a scheduled Record Query Flow when entry needs to be continuous.

Audit the segments you already have. Any segment that merely mirrors a list or a simple query is an immediate candidate for simplification.

Planning your move to Marketing Cloud Next, or want a second opinion on your current audience entry points? Get in touch — our Salesforce Marketing Cloud consultants work with you from audit through to production.