Skip to main content

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

Triggering paid updates through Next-Best-Action

Updated on August 3, 2022

After you configure the connection to a paid destination and specify how individuals are matched to their accounts on that destination, use the Next-Best-Action Designer to enable Next-Best-Action decisions for paid channels.

Pega Customer Decision Hub Paid Media Manager User Guide

The Next-Best-Action Designer allows you to define the Next-Best-Action decisions and requirements which apply to the whole organization, or to specific business issues or groups. You can use it to select the channels on which actions, such as product offers, are communicated to individuals. In addition, you can specify the triggers which cause the actions to be communicated to individuals, for example, scheduled outbound runs or real-time container updates.

To extend your Next-Best-Action to paid channels:

  1. Log in to the Pega Customer Decision Hub portal as an administrator.
  2. Click Next-Best-ActionDesignerChannels.
  3. In the Paid Media > Paid Destinations section, click Configure to select one or more paid destinations.
  4. Specify the trigger or triggers for the audience update.
    Tip: In Pega Customer Decision Hub 8.5, you can define triggers for both positive and negative audiences, that is, the individuals who should or should not receive a specific action. Keep the following considerations in mind when defining triggers for each audience type:
    • Positive audiences - As a best practice, always define the trigger at the top level of your business hierarchy. Real-time events calls at lower levels of the hierarchy can produce undesired results, for example, removing an individual from all eligible audiences other than those at the same hierarchy level as the event.
    • Negative audiences - You can define the container or event at any level of the hierarchy. When the container or event is triggered, Paid Media Manager updates negative audiences only for the actions on that level of the hierarchy. For example, if you define a real-time container at the Sales-Cards level, only audiences for actions from the Cards group of the Sales issue will be updated.
    For more examples on how to configure and implement this capability, see Enabling channels and triggers.
  5. Optional: For Google Ads and Facebook Ads destinations, in the Paid destinations section, click ConfigureNegative audience to increase the accuracy of your targeting by excluding individuals who are ineligible for an action. For more information, see
  6. Optional: For Google Ads and Facebook Ads destinations, in the Paid destinations section, click ConfigureLookalike audience. This creates an audience of customers who share the traits of your existing customers. For more information, see Configuring Facebook Lookalike Audiences and Generating Google Similar Audiences.
  7. Optional: As a best practice, you should use a single, primary paid configuration to manage all paid actions. However, if required, you can define additional paid configurations, for example, to use different paid strategies for different levels of your business hierarchy:
    1. In the Channels tab of the Next-Best-Action Designer, click ActionsAdd paid configuration.
    2. In the new Additional paid configuration section, in the Issue / Group list, select the issue and group or groups to which the schedule applies.
    3. Select the paid strategy, triggers and destinations for this hierarchy level, as described in steps 1-3.
  8. Click Save.
  • Previous topic Reducing wasted ad spend with the NBA Known Targeting tactic
  • Next topic Enabling actions for paid channels

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