Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Understanding the PaidAudiencesContainer REST service

Suggest edit Updated on October 7, 2021
Note: This article describes Paid Media Manager as implemented with Pega Customer Decision Hub™ 8.5 or earlier. For Pega Customer Decision Hub 8.6, see Understanding the PaidAudiencesContainer REST service.

PaidAudiencesContainer is a REST service that allows callers to retrieve the list of paid media audiences for a customer in one or more paid media destinations.

The service supports the GET HTTP method.

The URL pattern for this service is:


For the GET request, the service expects a JSON Object with the following attributes:

  • CustomerID - Customer identifier
  • DestinationKey - Destination key of the paid media destination. For multiple destinations, comma-separated lists of paid media destination keys are allowed.
  • Refresh - (Optional) This parameter is available starting in Pega Customer Decision Hub 8.5. 

    If set to true, this parameter triggers the Next-Best-Action strategy at the top level for the customer. The results of the strategy execution are sent back to the caller. This process also takes into account any paid strategy that is configured at the top-level Paid Media configuration in the Channels tab of Next-Best-Action Designer. The response will contain all the base audiences returned by the Next-Best-Action strategy and paid strategy (if configured).

    If set to false, or not included in the request, the response will contain all the audiences in the paid media master records which include base audiences, negative audiences, lookalike audiences, device-based audiences, and all customer next-best-action audiences.

Sample invocation request and response




         "pxSubscript":" DKa93e1234"

The audience data in the response includes a list of audience IDs. You can use the audience ID to fire Facebook Ads pixels or Google Ads events for each audience. Because the audience name is the same as the name of a corresponding action in Pega Marketing or Pega Customer Decision Hub, you may want to avoid exposing the name at the client-side. Because of that, you can use the audience ID instead of the audience name in a browser cookie to keep track of pixels and events which have already been fired for a particular individual. In the network, while creating Audiences out of the pixel, get the relevant audience name for the audience ID from the Paid Media landing page and use the same.

Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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