Skip to content

Limits and requirements

What Campaign Audience Builder needs from your Salesforce org, and every limit it applies, with its value.

Which edition includes which feature is listed in Editions and features. Which permission set a task needs is listed in Permission sets.

RequirementNeeded forDetails
Platform CacheFast results, audience sequencesThe package brings an org cache partition of 3 MB. Results stay in the cache for up to 2 days, or until the next deployment clears it.
Snapshots turned onAudience sequencesSequences can’t run while audience snapshots are turned off in the org.
Accounts as Campaign Members, or person accountsAdding Account audiences to a CampaignTurned on in Salesforce Setup. See Build and activate Account audiences.
Scheduled Apex jobsSchedulesThe audience scheduler takes scheduled Apex jobs, more at shorter intervals. Salesforce allows 100 scheduled jobs per org.
View Setup and ConfigurationOutcomes nightly processingThe user who scheduled the nightly update needs it. See Outcomes settings.
Filterable fieldsFilter conditionsLong Text Area and Rich Text Area fields can’t be filtered; Salesforce doesn’t allow them in queries. Text Area fields up to 255 characters can.
LimitValue
Folder levels below All Folders4
Fields you can filter onFields Salesforce allows in query filters; not long text areas or rich text areas
Values in one list of text values200, and at most 10,000 characters in total
Characters in custom logicNumbers, AND, OR and parentheses only; mixed AND and OR need parentheses
Audience objectCan be changed until the audience has a filter, has run, or is part of a sequence
Records a test evaluates5,000 records of the initial object
Fields in a composition profile15, from up to 3 parent relationships with up to 8 fields each
LimitValue
Run without an active jobClosed after 12 hours
Warning in the audience listNo successful run in the last 30 days
Records in a random subset50,000
Overlap Analysis in the backgroundAbove 50,000 records
Active deduplication rules per object3
Duplicate values per deduplication run50,000 by default; your org can have a different value
Records a deduplication rule removes per run100,000 by default; your org can have a different value
LimitValue
Campaign add in the backgroundFrom 3,000 records
Campaign Members created per batch200 by default; set in CAB Settings
Failed removals listed after campaign cleansing50 messages and 5,000 record IDs
Split of resultsPercentages must total 100%; fixed counts can’t exceed the results
Campaigns in a split on a schedule2 to 30
Fixed members in a split on a schedule100,000 per schedule
Scheduler interval15, 30 or 60 minutes
Ended one-time schedulesKept for 7 days
Email recipients for change approval5
Records per final action batch500
Characters in a final action description15,000
LimitValue
Parameters per entry10
Defaults per object10
Objects in a chain25, over at most 5 levels
Library references on one object node10
Chains per run10 different chains, and 50 nodes once expanded
Options of a picklist parameter2,000
Options of a lookup parameter50
Values of a list parameter200
Chains in audience sequencesNot supported

Storage, retention and the nightly processing share are settings; see Outcomes settings.

LimitValue
Window1 to 730 days
Outcomes per action8; above 4, the action’s nightly update takes longer
Audiences or campaigns in Compare6
Characters in an outcome or metric name80
Outcome folders1,000
Steps in a custom metric’s field path2
Groups of measured people one audience can read through outcome filters3
Updates on the home tabLast 30 days
LimitValue
Records per Account Engagement import file20,000
Account Engagement list cleansingSkipped when the lists to cleanse have more than 1,000,000 members
Marketing Cloud client secretExpires after 180 days; notifications start 30 days before
Waiting for a data extension add resultUp to 24 hours
Data extension for a data extension addNeeds a primary key column
Characters in Cabby’s organization instructions32,768

Set in CAB Settings; the archive job deletes older records.

RecordsKept by default
Run history365 days, at most 10,000 records
Data extension addition requests180 days, at most 100,000 records