Skip to main content

Identifying customers who interact with a real-time container

Suggest edit
Updated on January 19, 2022

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.

Pega Customer Decision Hub

For example, when a marketer defines a Container to represent a portion of a web page, the Container uses browser cookies to perform identity matching.

The following associations are captured during interactions with the Real-Time Container:

  • CustomerID to UniqueID
  • CustomerID to IP Address

Additionally, identity matching is implicitly performed by the following Real-Time Container services:

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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