Skip to main content

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

Configuring the Context Dictionary

Updated on August 4, 2022

You can define as many customer contexts as required, and then use them in your actions to target these different customer entities in the most relevant ways.

Pega Customer Decision Hub
To review or update the default contexts, configure a new primary context, or add a customer context, use the Context Dictionary. The Context Dictionary identifies the customer entities, the relationships between these entities, and any associated data to be used by Pega Customer Decision Hub.
  1. Log in to Pega Customer Decision Hub as an operator with access to App Studio.
  2. In the App Studio navigation pane, click Settings Context Dictionary.
  3. Review the existing customer contexts and verify that they are sufficient to cover the types of customers that you want to target.
  4. Optional: To add a new customer context, click Add context and specify the name, customer class, and optional exclusion list, as in the following figure:
    Sample context configuration
    Sample context configuration
  5. Optional: To set your new customer context as the primary context, click Change primary and select the context in the Select Primary Context dialog box.
    Tip: Changing the primary context affects the artifacts that use it, such as segments or campaigns. If you have already defined any segments or campaigns, recreate them manually after changing the primary context to ensure that they continue working.
  • Previous topic Understanding multilevel decisioning and the Context Dictionary
  • Next topic Next-Best-Action Designer taxonomy

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