Skip to main content


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

Identifying customers with identity matching

Updated on August 4, 2022

Identity matching is a feature that allows a Pega Customer Decision Hub application to identify individuals across their addressable devices. This feature also enables a seamless transition between an anonymous individual and a recognized customer.

Pega Customer Decision Hub

When an individual is anonymous (e.g. not logged in), relevant information is captured during their various interactions with the application. This information can then be utilized to determine the Next-Best-Action for this individual. When the individual authenticates themselves as a customer, their anonymous interaction data is merged with their previous interaction history. This allows the application to maintain a complete view of the customer journey.

Identity matching is incorporated in the following functional areas:

Identity matching utilizes browser cookies to store identifying information. For individuals yet to be identified, a unique id is stored in the cookie. Once an individual has been identified as a customer, their (encrypted) customer id is stored. During the individual's interactions with the application, additional data is collected and associated with the appropriate identifier (customer id or unique id). The captured associations are specific to the functional area and are listed in the corresponding section.

  • Previous topic Identifying customers who interact with a real-time container
  • Next topic Viewing how anonymous users interact with Pega Customer Decision Hub actions

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