Skip to main content

Table of Contents

Identifying customers who interact with a real-time container


Only available versions of this content are shown in the dropdown

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.

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?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us