Skip to content

Fall ’26 release

Fall ’26 turns audiences into living, measurable assets: reuse filters under governance, see who joined or left, automate safely, and see what people do after you add them.

New. Save a proven filter once and reuse it across audiences as a fixed copy, a configured copy, a synced reference, or a locked policy administrators enforce. Entries can cover one object, a connected-object chain, or an aggregate qualification, and Cabby can find or author them. See Reuse and govern filters with the Filter Library.

New. Filter an audience with your own Apex when fields and related objects cannot express the rule. See Custom Filters.

New. Collapse duplicate records inside the run by match field, and exclude the audiences that must keep every copy. See Remove duplicate records from audience results.

New. Move a filter condition with its grip handle, by drag, menu or keyboard, and custom logic keeps its meaning. Every dialog that edits a filter has Undo and Redo in its header for all changes in the dialog. Removing a condition under custom logic now updates the logic instead of showing an error. See Define Filter Conditions.

New. Paste or type several values into one text condition, such as postal codes, and split them into a list with one click. The condition matches any of the values, or none of them with the negative operators. See Choose the right filter operator.

Changed. The canvas lays out complex audiences in a predictable left-to-right reading order, keeps connection logic aligned, and adds a compact plain-language summary. Each user can switch between the new and the previous layout; switching doesn’t change any audience definition. See Work on the audience canvas.

Changed. The sequence record page presents a combination or waterfall as one table carrying each step’s setup and its result together, replacing the separate setup and results panes. It also tracks which results an edit invalidates and offers a partial or full re-run. See Build audience sequences.

New. Beyond a result count, see what the group looks like: prominent values, recency bands, missing data, differences from the organization baseline, and a short Cabby narrative. See Understand an audience with composition profiles.

Changed. Run history separates “how large was this audience?” from “who actually changed?”, showing size trends at a glance while eligible runs record who joined and who left since the run before. Read more in See audience size and membership change over time.

New. Group campaign cards of a schedule into a split so each new audience member lands in exactly one of its campaigns. Give campaigns a fixed number of members or a percentage and let one campaign take the rest; members already in one of the campaigns stay there on every later run. See Split a schedule’s new members between campaigns.

Changed. In orgs with Person Accounts, Account audiences can be split and added to campaigns, by hand or on a schedule, without Salesforce’s Accounts as Campaign Members. Person Accounts become campaign members through their contact; business accounts are skipped, and the “Add to Campaign” and “Split” windows say so. See Build and activate Account audiences.

Changed. The results-table download opens a configurable export rather than one fixed CSV: choose file type, encoding, and columns, and for Excel include the audience definition and run metadata. See Export results in the format your downstream work needs.

New. A scheduled run can send an alert — or skip its actions and pause the schedule until someone approves the change — when total churn crosses the schedule’s thresholds, with the decision made in the app and org defaults an administrator can lock. See Review large membership changes before actions run.

New. An eligible scheduled action can process only the membership changes since its last successful activation instead of the whole audience every time. See Process only what changed between scheduled runs.

Changed. Combination and waterfall sequences can run on a recurring schedule with the same automation controls as a standalone audience, including delta processing, outcomes, and change approval. See Schedule combination and waterfall sequences.

New. See what people do after you add them to a campaign or data extension, or run a final action on them: pick an outcome, such as a gift within 30 days, and CAB counts how many of them did it, by audience and by campaign. Keep a random control group out of a campaign to see how many extra gifts or sales the campaign itself brings, and build your next audience from who gave and who didn’t. Available in the CAB Professional Edition and higher. An administrator turns it on in CAB Settings, and results appear on the CAB Outcomes tab, where you can organize outcomes in folders. Read more in See what happens after you add people.

Changed. A new Status column shows each audience’s schedule, the state of its last run, and large result changes together, always in the same order. A cell shows only what needs attention, so an empty cell means there is nothing to report. The Name column gets the free space and shows each audience’s description next to its name, and Created By combines the creator and the creation day. Last Run shows short values such as “Today, 03:59 PM”, every cell stays on one line, and the list keeps your last sort order. See Read and sort the audience list and Read the Status column.

Changed. Standing, actionable notifications appear as a consistent stack of cards whose severity, message, and call to action follow the current user, so administrators see setup controls where others see next steps. See Act on important setup and runtime conditions in CAB.

New. The open-source sf CLI plugin sf-plugin-cab copies audience definitions from one Salesforce org to another, for example from a sandbox to production at a go-live. See Move audiences between orgs.

  • Campaign cleansing with blocked removals. When automation in your organization rejects the removal of some Campaign Members, CAB keeps the removals that succeeded, still adds the new members, and lists the members that could not be removed in Audience Details, by name and with their errors. See Add audience results to a Campaign.
  • Fiscal relative dates. A relative date with FISCAL and a number, such as LAST 4 FISCAL QUARTERS or 2 FISCAL YEARS AGO, selects the fiscal period your organization’s fiscal year defines, and the relative date field accepts these values. See Choose the right filter operator.
  • Schedule times and daylight saving time. A schedule that runs every 24 hours keeps its time of day when the clocks change for daylight saving time, and the schedule window shows times in your Salesforce time zone. See Schedule and automate an audience.