Skip to main content


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

Campaign schedule

Updated on September 15, 2022

This engagement type represents scheduled Campaign execution. Users can configure desired scheduling options and the system will automatically run the Campaign based on the configured schedule.

Pega Customer Decision Hub

To begin with, the user must select between single or recurring execution.

The following additional configuration is available for the One-time only option:

  • Start on – Specify the start date and time for the Campaign execution.

The following additional configurations are available for the Recurring option:

  • Frequency – Select the recurrence frequency. Options available are:

    • Minutes - Specify the number of minutes in which to recur. Additionally, the user can also choose to specify the hours of operation which are applicable to this mode of recurrence.

    • Hourly - Specify the number of hours in which to recur. Additionally, the user can also choose to specify the hours of operation which are applicable to this mode of recurrence.

    • Daily - The user can choose between the following three options:

      • Every day
      • Every weekday - leave days field empty (shown below)
      • Every X days – specify X in days field

    • Weekly - The following modes are supported:

      • Recur every X weeks based off a start date – specify X in weeks field, do not select any week days
      • Recur every X weeks on selected days – specify X in weeks field, select week days (as shown below)

    • Monthly - Specify the day of the month and the number of months in which to recur. The following shows a quarterly configuration:

    • Yearly - Specify the day of the year and the number of years in which to recur.

  • Start campaign – Select the start date and time for Campaign execution.

  • End campaign – Determines when scheduled Campaign execution should end. Select from the following three options:

    • No end date
    • Set number of occurrences - Specify the number of occurrences.
    • End by a date - Specify the end date and time.

Refreshing Campaign audience

In addition to configuring scheduling options, the user can also determine whether to refresh the audience for the Campaign as part of the scheduled execution. The user can further opt between refreshing the population for each run or just for the first run.

Note: The refresh audience option is only available when the Campaign audience is a criteria Segment.

Direct output to template

For Multi-Channel Campaigns, Pega Customer Decision Hub provides support for directly outputting the results of a scheduled run to a configured Database Template rule. In this mode, action processing is bypassed and, as a result, the interaction history is not updated.

Note: New deployments of Pega Customer Decision Hub on Pega Cloud services are configured to use the Decision Data Store for action state storage. Option to write Campaign results using a database template is disabled in this mode. If you want to enable the option to write Campaign results using a database template, see Disabling the Decision Data Store as action state storage on Pega Cloud.

To utilize this feature, the marketer can enable the Write Campaign results using a database template check box and specify the desired Database Template rule in the Template field.

Note: This feature requires the Database Template rule to utilize the Append writing mode. The smart-prompt for the Template field only lists templates that utilize this mode.

After configuring the schedule, marketers can utilize the template link in the Engagement section or the right overview pane to open the Database Template rule.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us