Skip to content

How CAB works

After reading, you know how an audience, a run, its results, an action and an outcome fit together, and where to read more about each.

Campaign Audience Builder (CAB) is a Salesforce app that finds the people you want to reach and acts on them inside Salesforce. You describe an audience once, for example lapsed donors in Germany. Every time it runs, CAB reads your current data, returns the people who match, and adds them to a campaign or hands them to another destination. Later, CAB can measure what those people did next.

An audience is not a list you export. It is a definition: one object, such as Contact, Lead or Account, and conditions on that object and on related records. Because the definition is saved, the audience stays current: run it again tomorrow and it finds whoever matches tomorrow. See How audiences work.

Conditions can reach far: related records with or without a match, totals over related records, and sequences that combine or rank several audiences. You build them on a canvas or let Cabby, CAB’s assistant, suggest them. See How sequences work.

A run reads your data with your own access and stores the matching records as the results. You can search and sort them, show related values and see why a record matched. See How results work and How related data works.

An action is what CAB does with the results: add them to a campaign, to an Account Engagement list or a Marketing Cloud data extension, or hand them to a flow or Apex class. You run an action once from the results, or a schedule runs the audience and its actions again and again, optionally with only the people who joined since the last run. See How actions work, How delta processing works and How integrations work.

An outcome measures what the people an action reached did afterwards, for example whether they gave within 30 days. A control group shows how many extra conversions a campaign brought. Outcomes can in turn become conditions of the next audience. See How Outcomes works.

Curators save proven conditions in the Filter Library once, and builders use them in every audience, as a copy, a live reference or an enforced rule. See How the Filter Library works.

Some features depend on your CAB edition, the integrations your org uses and the permissions you have. CAB shows a feature your edition doesn’t include, with a note, instead of hiding it. See Editions and features.

  • Audience. A saved definition of the records you want.
  • Run. One execution of an audience and its actions.
  • Results. The records the last run returned.
  • Action. What CAB does with the results, once or on a schedule.
  • Outcome. What people did after an action, and the measuring of it.