Skip to main content

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

Managing content in real-time channels with real-time containers

Updated on September 15, 2022

Real-Time Containers provide an easy low-code or no-code way for marketers to manage content that appears in real-time channels, such as web and mobile. As an example, a marketer may define a Container to represent a region of a web page. They can then associate the Container with a Campaign or a Next-Best-Action in the Next-Best-Action Designer. In real-time when the Container is called (say on a web page), the associated Campaign or a Next-Best-Action is executed and the Container gets populated with results.

Pega Customer Decision Hub

Pega Customer Decision Hub provides a set of APIs, which can be invoked from real-time channels, to facilitate the population of a Container and to capture customer responses.

Real-Time Containers are listed on the Containers tab of the Real-Time Artifacts landing page. This landing page is accessible in the Pega Customer Decision Hub portal via: ContentReal-Time Artifacts

The Containers landing page provides a quick overview of the Containers configured in the application.

  • Creating a real-time container

    To create a new Container, go to Content Real-Time Artifacts and in the Create menu in the Containers landing page select Container. Enter a unique name for the Container in the short description field and click Create and open to launch the Container rule form.

  • Using real-time container APIs

    This section provides information on the APIs available for use with Real-Time Containers.

  • Configuring a container invocation script

    To facilitate the invocation of Real-Time Container APIs, Pega Customer Decision Hub includes an out-of-the-box sample JavaScript file - webwb/RealTimeContainerScript.js

  • Invoking a fallback strategy

    If a Strategy execution fails due to an exception, Pega Customer Decision Hub invokes a fallback Strategy. The fallback Strategy results in a response when a service activity is executed. To configure the required action data, save the strategy FallbackStrategy into your implementation layer.

  • Identifying customers who interact with a real-time container

    Identity matching allows marketers to track anonymous individuals and their interactions with Real-Time Containers in the inbound real-time channels, such as web self-service, call center, and mobile applications. When a marketer defines a Container to present some action in the inbound channel, the container captures associations to perform identity matching.

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