Skip to main content


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

Deployment options for the Pega Customer Decision Hub for Communications data model

Updated on December 23, 2020

Use the Pega Customer Decision Hub for Communications data model deployment with a Pega-provided relational database. By using this standard, SQL-based technology you maximize reuse and reduce implementation effort, particularly if you are deploying applications for outbound or audience-driven marketing campaigns, or multilevel decisioning (for example, strategies targeting households).

Optionally, you can use either the Decision Data Store (DDS), or combined relational and DDS databases, depending on your scenario. For more information, see Configuring the Decision Data Store service.

Pega Customer Decision Hub for Communications Application Data Model Guide

Decision Data Store as the default database for decision records

Your customer analytic data store is contained in Pega Platform using NoSQL technology. Use this option if you want to deploy your application for customer engagement activities on inbound channels.

Note: The Decision Data Store does not support multilevel decisioning.

Combined relational and Decision Data Store databases for decision records

Your customer analytic data store is contained in both SQL and NoSQL data stores. Pega Platform automatically replicates and maintains the data stores for maximum flexibility. Use this option if you want to deploy your application for customer engagement activities on both inbound and outbound channels.

Note: This approach does not support multilevel decisioning.
  • Previous topic System integration in Pega Customer Decision Hub for Communications
  • Next topic Pega Customer Decision Hub for Communications data objects

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us