Skip to main content

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

Configuring a microsite to be aware of customer and action context

Updated on August 4, 2022

The following Microsite serves as a basic example of utilizing the customer and action context.

Pega Customer Decision Hub

This Microsite first loads relevant action and customer data. At runtime, the action context is determined from the URL used to launch the Microsite. This context is then used to load the action and customer data. The Microsite then uses this data to display a personalized page to the customer with pertinent customer and action information.

In the above section, customer data is referenced via the .Customer page property, while action data is referenced via the .Offer.OfferData page property.

On the next page, the customer is prompted for their priority code (an action data field).

Once the customer enters this information, the Save Site Data step saves the action data value (since the Microsite is action-aware). The Progress Offer step resumes the action along the ResponseReceived path with an Accepted response. The action can utilize the saved action data value (Priority Code, in this example) and use it to branch the flow, as shown below:

In the above action, the initial email shape sends out a link to the Microsite. If the customer responds to this action (e.g. via the Microsite), the flow uses the priority code (entered via the Microsite) to branch flow execution.

At runtime, when the above action is initiated, the customer gets an email with a link for the Microsite.

Upon clicking the email link, the Microsite is launched with an action and customer context. The Microsite loads the necessary data from these contexts and displays the first page.

Upon clicking Next, the customer enters their priority code on the next screen.

Upon clicking Next again, the priority code is saved (as action data) and the action is progressed. The action uses the entered code value to branch flow execution. Finally, the confirmation page is displayed to the customer.

  • Previous topic Configuring a microsite to display and save custom site data
  • Next topic Configuring a microsite to launch a different microsite

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