Skip to main content

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

Enabling Next-Best-Action targeting on DMP-based destinations

Updated on August 3, 2022

Configure one or more paid destinations for Adobe Audience Manager and other Data Management Platforms (DMPs) under Paid Media settings in App Studio.

Pega Customer Decision Hub Paid Media Manager User Guide

DMPs provide a mechanism to update cookie-based audiences outside of a client web session. After a DMP establishes a cookie for an individual who visits an advertiser's website, subsequent updates can be made through S2S updates to the DMP. These updates can then be delivered to a separate ad platform responsible for selecting and bidding ad inventory, such as a Demand Side Platform (DSP). Each of these media buying platforms should have a separate destination to account for differences in paid action priority for an individual across different destinations.

Paid Media Manager provides out-of-the-box support for the Adobe Audience Manager DMP. Paid Media Manager generates the appropriate traits and audiences within Adobe Audience Manager through API. After a scheduled run completes, a file is also generated with the audience updates produced by Next-Best-Action Designer. This file is delivered via S3 bucket or FTP to Adobe. Adobe Audience Manager can take up to 48 hours to propagate these updates to downstream DSPs and other third-party cookie-based platforms. In addition to Adobe Audience Manager, you can also configure paid destinations for a generic DMP.

For DMPs, updates are only made in response to scheduled runs and segments.

  1. Log in to App Studio.
  2. In the navigation pane of App Studio, click SettingsChannelsPaid MediaData Management Platform (DMP).
  3. Click Add destination.
  4. Fill out the destination name and description.
  5. Select the destination type.
    • Generic DMP
    • Adobe Audience Manager
  6. For Adobe Audience Manager, fill out the following required fields:
    • Destination name
    • DP ID
    • Data source ID
    • API user name
    • API password
    • API client ID
    • API secret key
  7. In the Sync Configuration section, map the Adobe Audience Manager Sync ID property to a Pega Customer Decision Hub property that holds the value of the universally unique identifier (UUID) that identifies the individual.
    The UUID property is implemented as part of the Adobe ID synchronization and works as a synchronization key, allowing the integration to match known individuals to their accounts and target them with the right ads on the right platform.
  8. Optional: Configure the additional settings in the Sync Configuration section.
    • To send all Paid audience information to DMP destinations every time that the synchronization runs, enable Full synchronization.
    Enable this setting if you want to send all Paid audience information to DMP destinations every time that the synchronization runs. Enabling full synchronization results in larger files being uploaded into the DMP. This can slow the synchronization. This setting is not enabled by default. When full synchronization is not enabled, the synchronization only sends information which has been updated in Pega Customer Decision Hub since the last synchronization date.
  9. In the Delivery Configuration section, configure the location where Paid Media Manager sends files with synchronization data to be uploaded into the DMP.
    This location may be an FTP location or an Amazon S3 bucket for the files.
  10. Click Apply.
  • Previous topic Understanding the PaidAudiencesContainer REST service
  • Next topic Generating Next-Best-Action web audiences with Paid Media Manager

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