Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Specifying Multi-Channel Campaign Details

Updated on August 4, 2022

Users can utilize the Plan tab to specify various details about the Campaign. These details are organized into the following sections:

Pega Customer Decision Hub
  • Campaign details
  • Financials

Campaign details

This section includes basic details about the Campaign and includes the following:

  • Name
  • Issue
  • Group
  • Business objective
  • Context - Type of audience to target via this Campaign. The value selected for this field determines the items presented in the Audience and Marketing strategy sections in the Build tab. By default, the available contexts are Customer or Prospect. You can define additional Customer populations, for example, Accounts, to better target your campaigns. For more information, see "Setting the context for your customer class" in the Pega Customer Decision Hub Implementation Guide on the Pega Customer Decision Hub product page.
  • Campaign type
  • Key code
  • Campaign image - Image associated with the Campaign. This image is displayed in the right overview pane and in the card for the Campaign on the Campaigns landing page.
  • Priority
  • Anticipated planning and launch dates
  • Ignore global exclusion list - Authorized users can enable this option to have outbound processing of actions for this Campaign ignore the global exclusion list. Refer to the Exclusion List chapter for details.
Note: The Campaign's Name, Issue, and Group values cannot be changed once it is created.


This section includes fields to specify financial metrics for the Campaign. These values typically play an important role in the approval of the Campaign.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us