Manage CAB Settings

Administer the app from one place

Open the CAB Settings tab to start required jobs and manage organization-wide CAB behavior. The interface is organized by administrative goal: Getting Started, Configure, and Maintain.

CAB Settings on Overview & Setup, with the Core setup progress panel at 0 percent, the three core background jobs, and the review cards for Changes & Approvals, Automation, Performance & Data, Permissions, and AI & Integrations

Find a setting

Navigation group	Page	What it controls
Getting Started	Overview & Setup	Required background jobs and setup progress.
Configure	Automation	Final Actions and scheduler behavior.
Configure	Changes & Approvals	Run-to-run change tracking and change-approval policy. The page header is Auditability & Governance.
Configure	Deduplication	Per-object rules that remove duplicate records from audience results.
Configure	Permissions	Who can use CAB, and who may manage shared assets.
Configure	AI & Integrations	Cabby, Account Engagement, and Marketing Cloud setup when those features are available.
Maintain	Performance & Data	Cache, result persistence, batch sizes, composition profiles, and retention.
Maintain	Outcome storage	Whether outcomes are measured at all, how much storage that uses, and the limit at which it stops.
Maintain	Audience Query Diagnostics	Generated SOQL and large-data-volume filter risks when diagnostics are included in the edition.

Only pages relevant to the enabled CAB edition and integrations are shown.

Start the core services

On Overview & Setup, the Core setup panel tracks how many of the available background jobs are running:

Enqueue Audience Scheduler launches scheduled audiences as they come due. Use Enqueue Job to start it and Unschedule to stop it.
Enqueue Archive Batch Job cleans up old audience run logs and applies the configured retention limits.
Schedule the outcome measurement job appears when Outcome Tracking is available and measures due checkpoints.

Choose how CAB should work

Below the core services, Choose how CAB should work links to the areas worth deciding before the first audience run. Each card opens its page with Review settings:

Changes & Approvals — track differences between runs and require approval before large changes activate.
Automation — choose what happens after an audience run and how scheduled audiences are managed.
Performance & Data — tune batch and cache behavior, automatic profiles, and how long CAB keeps operational data.
Permissions — control who can use CAB and delegate management of shared assets.
AI & Integrations — connect and maintain the AI Agent and the marketing destinations enabled for this org.

Configure automation

CAB Settings → Automation

The upper part of the page manages Final Actions. Under Scheduler Settings, administrators can:

turn on Automatically remove recurring schedules targeted on inactive campaigns;
turn on Automatically remove recurring schedules targeted on past campaigns;
choose Which sharing context should be used during scheduled audience runs?: Audience Owner or Job User.

Remove duplicate records

CAB Settings → Deduplication

Define ordered match-field rules per audience object so that runs collapse duplicate records before they are counted or activated.

Participating is the default, so activating a rule changes every audience built on that object at once — except the audiences where deduplication was turned off. A new or changed rule applies from each audience’s next run; a run already under way keeps the rules it started with. The page states this above the rules.

Deduplication also adds a little to how long a run takes. For most audiences the difference is small; audiences with many duplicates spend more time on it.

See Deduplication for the rules, the per-audience setting, and the removal details on a run.

Manage access and delegation

CAB Settings → Permissions

Under Access, assign the permission set groups that grant CAB itself: Administrators, Users, and Users without automations.

Under Delegated management, grant curation of a shared asset without full administrator access: Outcome Management and Filter Library Management. Assign these in addition to a user’s regular CAB access.

Deduplication rules are not delegable. A rule decides which records leave a segmentation result, so only CAB administrators can create, reorder, or delete them. Everyone with regular CAB access can read the rules, which is what the per-audience summary needs.

Configure performance and retention

CAB Settings → Performance & Data

Under Advanced Settings, CAB can expose these controls depending on the edition:

Store audience results in the Platform Cache to improve segmentation performance and the related result-persistence options;
Batch Size for asynchronous campaign member creation;
Automatically compute composition profiles after each run.

Under Data Retention Settings, set both age and record-count limits:

Number of days to retain Audience Run records as run history;
Maximum number of Audience Run records to retain as run history;
Number of days to retain Data Extension Addition Request records;
Maximum number of Data Extension Addition Request records to retain.

CAB keeps a record only while it is inside both applicable limits. Review these values against your audit requirements before reducing them.

Control what outcome measurement stores

CAB Settings → Outcome storage

Measuring an outcome means keeping the activations being measured and the records that later showed a conversion. This page reports how much of your org’s data storage that uses, and caps it.

Outcome storage with measuring switched on, 7 MB in use against a 16 MB limit, the limit drawn inside the org’s 500 MB allocation, and the space split between Activation snapshots and Conversion matches across four campaigns

Switch measuring on or off

The card at the top right states whether measuring is on. Switching it on opens the limit first, so the number is set before anything is stored; switching it off confirms, then stops the nightly checkpoint job.

While measuring is off, nothing new is stored. Activations still go out — they simply report no conversion rate.

Set the limit

The reading is a measurement with a timestamp, taken whenever this page opens. Under The limit, inside your org’s storage, the limit is drawn inside the org’s own data allocation so you can see what share of it you are reserving.

Set Limit (MB) and Warn at (%), then select Save. The default limit is a fifth of the org’s allocation. Saving deploys a setting, so it takes a minute to come into force.

Only two kinds of record grow with how much you measure, and only those two count towards the limit: Activation snapshots and Conversion matches.

Stop tracking or delete what one activation holds

Where the weight sits lists the outcomes and the campaigns or lists holding the most. Select Manage to act on one.

Manage snapshots listing four campaigns heaviest first with their outcome counts and stored size, three tracking and one stopped, each offering Stop tracking and Delete

Each row shows what one campaign or list is holding, how many outcomes rest on it, and whether it is still being measured. Both actions confirm first:

Stop tracking removes the outcomes from the actions that capture into that campaign or list. Nothing new is stored for it, and what is already stored stays until its checkpoints pass. You can start tracking it again at any time.
Delete removes what it has stored. The conversion rates that rest on that data can no longer be shown. Deletion runs in the background and frees the space as it goes; it cannot be undone.

A row that is no longer tracked offers Delete only. A campaign or list captured without a standing outcome assignment — a Pardot list, for example — also offers Delete only, because there is no assignment to remove.

See Outcome measurement for defining outcomes and reading their results.