Skip to main content

 –

Identifying customers who respond to a microsite

Suggest edit Updated on January 19, 2022

Identity matching also allows marketers to track unidentified customers and their interactions with Microsites. When an anonymous individual visits a Microsite, the system identifies the individual with a unique identifier. Later, when customer information is available to the Microsite, the system associates the anonymous user's interactions with the customer.

The following associations are captured during interactions with the Microsite:

  • CustomerID to UniqueID
  • CustomerID to Email Address
  • UniqueID to Email Address

Identity matching in Microsites is handled by the following stages in the lifecycle:

  1. Load Data - In addition to loading customer data, this stage also saves the aforementioned association data. For example, if the browser cookie contains the unique id but the Microsite is aware of the customer, this stage associates the unique id and the customer id. Additionally, the cookie is updated with customer information.
  2. Confirmation - In this stage, the Perform Identity Matching step associates available Microsite attributes. For example, if the Microsite collects email information, this information is associated with the available identifier (customer id or unique id).

Note: To perform identity matching during a different stage, include the Perform Identity Matching step in that stage.

In addition to the above stages, identity matching also occurs in the following areas in Microsites:

  • Impression capture - When the section RecordImpressionForMicrosite is included in a Microsite stage to capture impressions, it calls the IMPR service. For anonymous users, this service records the impression using the unique id.
  • Launching another Microsite - When a Microsite launches (or redirects to) another Microsite, identity matching attributes - such as customer id or unique id - are propagated to the new Microsite.

Note: If the Perform Harness rule is specialized in the new Microsite class, ensure that the IdentityMatchingConfiguration Section rule is included in this Harness. This section enables the Internet Application Composer (IAC) gadget to update the browser cookie.

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.

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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us