Designing Interaction Management

Use the following list of scenarios to help you determine which type of interaction management you want to develop. Use the guidance in the "do this" column to help you identify the steps to take in the next phases of the interaction management development process: Creating Personalization Conditions, and Personalizing Portal Applications.

Note: Campaigns and behavior tracking are not currently supported for anonymous, non-trackable users.

If you want to... do this:

Display a binary property from a single content node from the Virtual Content Repository that can change each time a user visits your portal or clicks the browser refresh button.

For example, each time an employee visits the Intranet portal, display a different picture from the company picnic.

For creating a generic rotation of content for all users, create a Placeholder and add a default query for the Placeholder that displays the range of content you want.

For creating a targeted rotation of content for each user based on each user's characteristics, create a Placeholder and a campaign. Set up the campaign with content actions that put different types of content in the Placeholder for different types of users. Define the necessary conditions and rules to be used in the campaign.

You can also use the <ad:adTarget> JSP tag as an alternative to a Placeholder to manually embed a content query in a JSP.

Display a binary property from a single content node from the Virtual Content Repository that shows the same content node for each type of user.

For example, if a user of type "manager" views the portal, always show the manager the "performance review reminder" graphic. If a user of type "regular employee" views the portal, always show the employee the "benefits open enrollment" graphic.

As in the previous scenario, you can create a Placeholder with a default query for all users or a Placeholder used by a campaign to target specific users differently. There are two keys to showing the same content node without content rotation:

  • Set up your content with properties and values that can uniquely identify each piece of content.
  • Create highly focused content queries in the Placeholder or the campaign to retrieve those single unique content nodes.

Display multiple content nodes and properties from the Virtual Content Repository simultaneously.

For example, show each user a unique list of recommended books based on the user's characteristics.

To show multiple content nodes from the Virtual Content Repository simultaneously, create content selectors and add them to your JSPs.

Display personalized content from an inline section of a JSP.

For example, provide three different sections of HTML content in a JSP but show users only the sections that match their characteristics.

To display personalized inline JSP content, create user segments and use the <pz:div> JSP tag to wrap personalized content.

You can also use the following JSP tags to display inline JSP content based on the device that is viewing the content (for example, a handheld device or a PC): <cscm:default>, <cscm:not-default>, <cscm:recognized>, <cscm:not-recognized>, <cscm:when>, and <cscm:when-not>.

Send users automatic e-mails. Create and store e-mail message files (see Preparing to Use Campaigns) and create a campaign that uses an e-mail action.
Give users automatic discounts.

Perform the following tasks:

  • Add commerce services to your portal application.
  • Set up a shopping cart using the WebLogic Portal commerce API.
  • Create a catalog in the Virtual Content Repository.
  • Use the WebLogic Portal catalog classes in the commerce API to surface catalog items from the Virtual Content Repository and identify them with "categories" and "SKU" numbers.
  • Create discounts and use the commerce API to surface the discounts in your shopping cart. If desired, use the API to surface the discount's description next to the discount amount displayed in the shopping cart.

Related Topics

Developing Personalized Applications

Overview of Content Management

Setting up Users and User Properties

Creating Personalization Conditions

Personalizing Portal Applications