After you create all necessary personalization conditions, you can create interaction management functionality
and surface it in your portals. For example, after you create a user segment
to trigger personalization, you can create a content selector that defines
the content that is shown to users who are members of the user segment.
Note: Many interaction management
development tasks are dependent on other tasks. For example, if you
are creating a user segment based on user profile properties, you must
first create the user profile properties you want; and if you are creating
a campaign and you want to trigger campaign actions based on user segments,
you must first create the user segments you want. The following tasks
highlight any applicable dependencies.
Creating Placeholders
Dependencies: Placeholders rely on no other file types
for creation. However, to set up a placeholder query, the types and content
you want to display in the placeholder must be set up in the Virtual Content
Repository.
Creating Content Selectors
Dependencies: Content selectors can use user segments,
user profile properties, and session and request properties.
Creating Discounts
Dependencies: Discounts can be triggerd by and applied
to product categories and items. Categories and items are defined in the
Virtual Content Repository.
Preparing to Use
Campaigns
Dependencies: Campaigns can use user segments, placeholders,
and properties from property sets (user profile, HTTP session and request,
catalog structure, and events).
Creating Campaigns
Dependencies: Campaigns can use user segments, placeholders,
and properties from property sets (user profile, HTTP session and request,
catalog structure, and events).
Using
the <pz:div> JSP Tag
Dependencies: The <pz:div> tag requires the use
of user segments.
After you create interaction management resources, such as placeholders,
content selectors, and campaigns, those resources are available to portal
administrators for modification in the WebLogic Administration Portal.