Skip to content
Campaign Audience BuilderCampaign Audience BuilderCAB Documentation

Version history 2026

Every Campaign Audience Builder package version of 2026, newest first. The newest versions are also on the Version history page.

Version 1.231.0

Released on 10 November 2026.

New

  • After an upgrade with new or changed features, a small notice at the bottom right of CAB says Updated to the new version, with a What's new link to the changes since your previous version. The new settings section CAB Updates shows your installed version and links to the version history, and CAB administrators can turn off push upgrades there.

Changed

  • Waterfall and combination sequences now run also in orgs that do not use the Platform Cache, and a run no longer stops or changes its result when the Platform Cache drops data during the run. While a sequence removes duplicates, the ledger shows each finished step without a count, and the progress bar shows how far it is, for example Removing duplicates: rule 1 of 2, step 2 of 3. When the run ends, every step count and the total already reflect the removed duplicates.

Fixed

  • Scheduled actions on combination sequences now run when Track membership changes between runs and Automatically compute composition profiles after each run are both off. Before, the scheduled run finished with the right number of results, but the action did not deliver, for example the campaign stayed empty, and after two hours the action failed.
  • Users without access to Campaign Audience Builder, or without a Campaign Audience Builder license, no longer get an error message such as "Missing permissions" when they open a Campaign record page that has the Campaign Audience Builder component. For users without access, the component now shows nothing.
  • In orgs with the setting Persist cached results as audience member records turned on, a run that added members to a campaign with Campaign Cleansing could fail with a record lock error. This happened when CAB stored the audience members while it removed the people who left the audience from the campaign; CAB now waits for the lock, so both steps finish.
  • In the schedule dialog, the Change approval step said that Track membership changes between runs was off for this audience. It is an org setting: the note now says so, and links CAB admins to Settings > Changes & Approvals. See Review large membership changes before actions run.
  • In the schedule dialog, the Add to Data Extension step could show Advanced Settings outside the dialog, below its buttons, when the data extension had six fields or fewer. The step now scrolls, so every setting stays inside the dialog. See Schedule and automate an audience.
  • When a user deleted an audience while CAB still compared its latest run with the run before, CAB could report an error. CAB now ends that comparison quietly. This affected orgs that use Track membership changes between runs.
  • After an audience run, admins could get an Apex error email when another job briefly locked the same audience while CAB cleaned up the stored results of the run. CAB now tries the cleanup again a few minutes later.

Version 1.230.0

Released on 8 November 2026.

Upgrade notes

  • If your fiscal year does not start in January, an audience with a value such as LAST 4 FISCAL QUARTERS can select different members on its next run, because it now uses fiscal periods. Fiscal relative dates take only quarters and years: an audience with a value such as LAST 3 FISCAL MONTHS now stops with a message that names the value, so change it to fiscal quarters or to a calendar unit such as LAST 3 MONTHS. See Choose the right filter operator.

Changed

  • Cabby now checks each filter value against the field's type before it saves or previews an audience or a Filter Library entry, and refuses a value that cannot run with an example of a valid one. When Cabby uses a field or object that you cannot read, its message now names both possible causes and suggests asking your Salesforce administrator for access. See Build and activate audiences with Cabby.
  • A cloned sequence now belongs to the user who clones it, as a cloned audience already did.
  • With several notifications open, the stack could grow taller than the window and cover buttons, also in the Cabby sidebar. The stack now shows every urgent card, folds the others behind a toggle such as 3 more notifications, and stays inside the window beside the Cabby sidebar. See Act on important setup and runtime conditions in CAB.
  • The links in run history windows, the record names in results tables, and the choice tiles in Add to Data Extension and in the relationship choice now work with the keyboard. Long titles in the Change approval required panel and in the Add to Data Extension tiles now wrap instead of being cut off.

Fixed

  • Add to Campaign with Campaign Cleansing turned on could fail with an error that asked you to contact support, when the audience results had expired from the Platform Cache. CAB now cleanses from the results it stored for the run, or asks you to run the audience again and changes no campaign members. See Add audience results to a Campaign.
  • In orgs that do not store audience results in the Platform Cache, audiences that ran in the background showed no Joined Members and Left Members, and actions set to Changes only sent the full audience every time. These runs now keep their results for the comparison, as in orgs that use the Platform Cache. See See audience size and membership change over time.
  • A run that failed as soon as it started, for example on a filter value that its field cannot hold, showed as running for hours without an error. Such a run now ends within seconds and shows its error, and the user who started it gets a notification.
  • Relative dates with fiscal quarters or years, such as LAST 4 FISCAL QUARTERS, ran on calendar quarters and years; they now run on your fiscal periods. Values that count back with AGO, such as 4 FISCAL QUARTERS AGO, failed when the audience ran and now work. See Choose the right filter operator.
  • A clone could lose the settings of a custom filter, some audiences could not be cloned, and a clone landed in the original's folder. If your permission sets lack access to a field that CAB copies, cloning now stops with a message that lists those fields.
  • A user with edit access to an audience, for example through sharing, could not delete a node that another user had added. Anyone who can edit the audience can now delete its nodes. See Delete Nodes.
  • A run with an outcome filter on an object you cannot read, such as Gift Transaction, failed with a technical error. The run now stops before it starts with a message that names the outcome and the object, and CAB no longer saves such an outcome filter. See Act on results.
  • The actions of a scheduled waterfall sequence could add no members because they started while CAB was still saving the run. Such an action now tries again a minute later. See Schedule combination and waterfall sequences.
  • When CAB could not reach Account Engagement or Marketing Cloud, for example after an authorization expired, some windows kept loading or showed an error over a form that could not work. They now stop loading and say what could not be reached and what to check, and Add to Data Extension shows an error message when a data extension cannot be saved. See Operate Account Engagement and Marketing Cloud integrations.
  • In run history, in Audience Details and in a sequence step's actions window, the campaign names, Open decision and the error log links did nothing when clicked. They now open the record. See See audience size and membership change over time.
  • Users with fewer permissions now get a clear message instead of a broken screen: a missing CAB permission is explained also in German, French and Japanese, and Configure Data Inclusion says when an object's fields cannot be loaded. Add to Campaign offers New Campaign only to users who can create campaigns, and the Change approval required panel shows the decision also to users without access to the Marketing Cloud integration.
  • Users who work in German, French or Japanese saw some texts in English, in Final Actions and on the Data Extensions and Campaigns tabs of the schedule window. These texts now appear in their language.
  • Security fixes.