Skip to content

CAB Settings

Every page and setting on the CAB Settings tab, in the order of the tab, with its default, its values and what it does.

The CAB Settings tab comes with the Campaign Audience Builder Admin permission set. See Permission sets. Settings on a card are saved together with its Save button; a saved change takes effect after a short deployment in the background.

Getting Started → Overview & Setup. Core setup shows how many of the two background jobs are running without a problem with their owner.

ControlDefaultValuesEffect
Start the audience scheduler: Start, later EditNot running–Opens Audience Scheduler Settings with Frequency. The scheduler starts scheduled audiences that are due.
FrequencyEvery 15 minutesEvery 15, 30 or 60 minutesEach 15-minute step takes one scheduled Apex job. A lower frequency also moves schedules that run more often to the new frequency.
Start the audience scheduler: Unschedule––Stops all scheduler jobs, without asking.
Start the archive job: Start, UnscheduleNot running–Runs every night at 01:00, cleans up old run history and data extension addition requests. See Performance & Data.

The page also links to Turn on Outcomes, which has its own nightly update.

Getting Started → Turn on Outcomes. See Turn on Outcomes.

Configure → Automation.

Configure Final Actions lists the final actions with New, Activate or Deactivate, Edit and Delete. See How final actions work.

Setting under Scheduler SettingsDefaultValuesEffect
Automatically remove recurring schedules targeted on inactive campaignsOffOn, offThe scheduler removes inactive target campaigns from schedules, and a schedule whose target campaigns are all inactive.
Automatically remove recurring schedules targeted on past campaignsOffOn, offThe same for target campaigns whose end date has passed.
Which sharing context should be used during scheduled audience runs?Job UserAudience Owner, Job UserWith Audience Owner, a scheduled run removes results the audience owner can’t access.

Configure → Changes & Approvals. Track membership changes between runs is available on request; change approval needs Professional Edition and tracking turned on. See Editions and features.

SettingDefaultValuesEffect
Track membership changes between runsOffOn, offComputes who joined and who left after each run, in an extra background job. Change approval, delta processing and run history changes need it. Only administrators can save it.
When a run’s membership change crosses the thresholdsDo nothing (off)Do nothing (off), Notify only: send an alert, actions still run, Require approval: skip this run’s actions and pause future scheduled execution until an approver decidesThe default change approval for every schedule.
Change exceeds (% of previous size)Empty0 or moreThreshold as a share of the previous size.
and is at least (members)Empty0 or moreThreshold as a number of members. The check fires only when every threshold that is set is met; with both empty, it never fires.
Send approvals toUser who scheduled the runSpecific user, Audience owner, User who scheduled the runWho decides.
Approver userEmptyA userThe approver for Specific user.
Auto-reject after (hours)Empty0 or more; empty or 0 never expiresOnly when approval is required. Rejects a pending approval after this time.
Also email the approverOffOn, offAlso sends the approval by email.
Send from (Organization-wide email address)EmptyVerified organization-wide email addresses available to all profilesSender of approval emails. Only administrators can save it.
Always CC these recipientsNoneUp to 5 email addressesCopied on every approval email.
Lock these settings for every scheduleOffOn, offSchedules can’t change these defaults.

Configure → Deduplication. Needs Professional Edition. One list each for Contact, Account and Lead. See Remove duplicate records from audience results.

ControlDefaultValuesEffect
Run limits50,000 duplicate values, 100,000 records removed by one ruleSet per org by usAbove either, the run fails instead of delivering a partly deduplicated audience.
Manage Audiences––Choose which audiences of the object are deduplicated.
New rule: Match field–Groupable fields of the objectRecords with the same value are collapsed to one; empty values never group.
New rule: Keep sort–Sortable fields of the objectDecides which record of a group is kept; records without a value are removed.
New rule: KeepsLowest value (e.g. oldest)Lowest value (e.g. oldest), Highest value (e.g. newest)Sort direction for the kept record.
New rule: ActiveOnOn, offAn active rule applies to every audience of its object, unless the audience opts out.
Reorder––Rules apply in order; each one works on what the one before left.

Configure → Permissions. Cards under Access and Delegated management, each with Select Users. See Permission sets.

Configure → Custom Filters. No settings: an example implementation with Copy code, and Custom filters found in this org. See Custom filters.

Configure → AI & Integrations. The page appears when Cabby, the Account Engagement integration or the Marketing Cloud integration is available.

Section AI Agent Setup. Set-up steps, in order: Accept Terms and Choose AI Data Processing Mode, Assign Agent Permission Set, Create Credentials, Enable Named Credential, Register with CAB Agent, Test Connection, Enable Metadata Statistics, Activate Agent. See Set up Cabby.

SettingDefaultValuesEffect
AI Data Processing ModeNone chosen; the terms dialog suggests EUEnforce EU data residency and processing, Optimize availability and performanceWhere AI requests are processed. Changing it needs the terms accepted again.
Custom Agent InstructionsEmptyUp to 32,768 charactersAdded to Cabby’s context, for example your org’s terminology.
Response ModeFastFast, ThinkingFast model or a larger model that reasons more deeply. Shown only when available for your org.
Cabby data accessAll off–See Set up Cabby.

Section Pardot Integration. Set-up steps: Assign Integration Permission Set, Authorize, Configure Pardot Integration Variables, Enable Pardot Integration, Set List Synchronization Frequency.

SettingDefaultValuesEffect
Business unit and campaign under Configure Pardot Integration VariablesEmptyPer business unit: active, Account Engagement campaign, assigned usersUsed for imports to Account Engagement.
Enable Pardot IntegrationOffOn, offTurns the integration on once business unit and campaign are set.
List Synchronization FrequencyEvery hourEvery 1, 3, 6, 12 or 24 hoursHow often synchronized lists are updated.

Section Marketing Cloud Integration. Set-up steps: Enter Marketing Cloud Integration Credentials, Assign Integration Permission Set, Set Default Integration Variables.

SettingDefaultValuesEffect
Client Id, Client SecretEmptyFrom the installed package in Marketing CloudCredentials of the integration; never shown again after saving.
Client secret expiry dateEmptyA dateSecrets expire 180 days after they are created; CAB reminds you before.
Authentication Base URLEmptyhttps://<subdomain>.auth.marketingcloudapis.comCAB stores the subdomain.
Default Business Unit, Default FolderEmptyFrom Marketing CloudDefault business unit and data extension folder.

Maintain → Performance & Data.

Setting under Advanced SettingsDefaultValuesEffect
Store audience results in the Platform Cache to improve segmentation performanceOn after installation, except in Developer Edition and Professional Edition orgsOn, offKeeps run results in the Platform Cache.
Persist cached results as audience member records. This will create audience members asynchronously after a run using platform cache finishes and delete members which are not in the results anymore.OffOn, offOnly with the Platform Cache. Also allows sorting and searching results.
Batch size of the job that persists the cache results2,0001 to 2,000Records per batch when persisting results.
Batch Size for asynchronous campaign member creation2001 to 2,000Records per batch when adding Campaign Members in the background.
Minimum audience batch size51 to 2,000When a run hits Salesforce limits, CAB retries with half the batch size, down to this value, and keeps the smaller size for later runs.
Automatically compute composition profiles after each runOffOn, offNeeds Advanced Edition. Profiles can still be computed by hand.
Setting under Data Retention SettingsDefaultEffect
Number of days to retain Audience Run records as run history365Applied by the archive job.
Maximum number of Audience Run records to retain as run history10,000Applied by the archive job.
Number of days to retain Data Extension Addition Request records180Older records are deleted.
Maximum number of Data Extension Addition Request records to retain100,000Records above this number are deleted.

These four settings only take effect while the archive job runs. See Overview & Setup.

Maintain → Outcome limits. See Outcomes settings.

Maintain → CAB Updates shows the Installed version and links to the Version history.

SettingDefaultValuesEffect
Turn off push upgradesOffOn, offWhen on, your org gets no push upgrades from us, security fixes included; an administrator installs new versions from the Version history. Saved immediately; only administrators see it.

Maintain → Audience Query Diagnostics, only when it is turned on for your org. No settings. See Diagnose an audience query.