Skip to main content

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

Implementing Paid Media Manager

Updated on August 3, 2022

Paid Media Manager extends Next-Best-Action to modern digital advertising platforms, such as Facebook Ads and Google Ads. Each individual's Next-Best-Action is communicated through audiences on ad platforms. To implement Paid Media Manager in your organization, you must start by configuring the connection to the paid destination.

Pega Customer Decision Hub Paid Media Manager User Guide
  1. Learning about paid destinations

    A paid destination holds the configuration of how an ad platform receives audiences using a specific integration mechanism. You can have multiple paid destinations for each ad platform. For example, separate Google Ads accounts may be used for Google Search and for YouTube. After a paid destination is set up, it can be configured to receive paid audiences based on Next-Best-Action Designer or intelligent segments.

  2. Configuring CRM-based connections to paid destinations

    Paid Media Manager uses the CRM-based matching APIs for Facebook Ads, Google Ads, and LinkedIn Ads to synchronize paid audiences. To set up a connection, you must configure both Paid Media Manager and the paid destination to which you want to connect.

  3. Optional: Verifying the paid synchronization by enabling segment updates on paid destinations

    After you configure the connection with a paid destination, you can test the synchronization by enabling one of your customer segment to be synchronized with the destination. Synchronizing a segment creates paid audiences based on the segment in the paid destination. Since segments can be based on multiple factors, such as traits or AI analytics, they can be a tool to build audiences in the paid destination, or simply to test whether the synchronization can connect to the paid destination.

  4. Configuring web-based and DMP connections to paid destinations

    In addition to modern, CRM-based platforms, Paid Media Manager also supports pixel-based APIs provided by advertising technology platforms, including demand-side platforms (DSPs), data management platforms (DMPs), and advertising networks. Instead of CRM-based APIs, these platforms generally rely on third-party cookies to build anonymous profiles and target individuals with ads. Paid Media Manager integrates with these mechanisms to deliver people-based Paid Audiences and Next-Best-Action decisions.

  5. Generating Next-Best-Action web audiences with Paid Media Manager

    Use Paid Media Manager to target individuals on paid channels based on your enterprise data and decisions.

  6. Enabling AI-driven advertising with paid click capture on Facebook Ads, Google Ads, and other platforms

    Pega Customer Decision Hub campaigns that target paid audiences use Next-Best-Action to select the most relevant action for each individual. Paid Media Manager communicates that decision to ad platforms, and targets the individual with relevant ads. Regardless of whether the targeted individual responds positively (by clicking the ad) or negatively (by ignoring it), their behavior should be communicated back to Pega Customer Decision Hub, so that the AI models that govern targeting can learn from the interaction. To do this, you can configure

  7. Enabling the offline conversion job scheduler for Paid Media Manager

    To enable Paid Media Manager to send data about offline conversions to CRM-based destination platforms, enable the OfflineConversionRTTrigger job scheduler.

  8. Enabling paid tactics

    To enable paid tactics, you must configure relevant settings in Pega Customer Decision Hub.

  9. Enabling learning from own-channel models for the Paid channel

    You can enable surrogate adaptive models for paid media while the Paid-specific models mature.

  10. Enabling learning from Paid-specific models for the Paid channel

    If required, you can enable channel-specific adaptive models for paid media to help optimize your advertising based on responses from the Paid channel.

  11. Configuring the PaidMediaSync queue processor to optimize performance

    The PaidMediaSync queue processor manages the synchronization queue for Paid Media Manager. To help optimize performance, configure the queue processor as described below.

  12. Defining triggers for paid media

    For consistent results across owned and paid channels, you can use Next-Best-Action to drive customer engagement on external media platforms such as Facebook Ads and Google Ads. Using Next-Best-Action with paid media ensures that each individual in an audience is targeted with the optimal offers at the right priority and maximum bid amount.

  • Previous topic Prospecting with the Conversion Lookalike and NBA Lookalike tactics
  • Next topic Learning about paid destinations

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