Skip to main content

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

Implementing segmentation

Updated on August 27, 2020

Segmentation is dependent on Associated Customer Data defined in the Application Settings of your Pega Customer Decision Hub portal. The Associated Customer Data has to be stored in relational databases. It is recommended to use the source relational database tables that you mapped to for your data flow pulls as the associated databases.

Integrate your associated customer tables by repeating the following steps for each associated table:

  1. Create a new class.

  2. Ensure that your tables contain a foreign key to match and join the contents of this table with your customer data.

    This typically is represented by CustomerID.
  3. Create a Database Table rule that maps your class to the associated database table.

    The database operator used on this database table rule only needs to have read access.
  4. Define properties in this class.

    While these properties do not need to have the same name as the database columns from which they are sourced, they should represent the properties on the tables from which you plan to use for marketing decisions.
  5. Update the external mappings tab of your class so that the class properties map to the columns in your database table.

    While many databases are not case-sensitive, some such as MS SQL are and so it is safer to be case-sensitive.
  6. Create a page list property in your customer class that applies to the class that you created in step 1.

    This will be used as the Entity Name when defining your Associated Customer Data. Entity Names cannot be inherited. They must be on your top most customer class.
  7. Add the associations to your context dictionary.

  8. Save and regenerate your context dictionary after updating the dictionary with the new associations.

  9. Optional:

    For customers who are also using these classes to source their Decision Data Store, create a report definition in this new class to pull from all the columns, and then use this report definition in a data flow to pull and store the data into the Decision Data Store.

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