User Management Guide
When a user visits your portal without logging in, that user is called "anonymous." While working with anonymous users is inherently limiting in some ways (because there are few things you know for sure about them).
WebLogic Portal takes advantage of that information and provides many features that make working with anonymous users more useful and meaningful in your portals, such as letting you set up visitor entitlements, delegated administration, and some types of personalization based on that information.
WebLogic Portal provides even more power in working with anonymous users with a feature called anonymous user tracking. When you use anonymous user tracking, anonymous users are given records in a database, where you can store meaningful information about them such as personal preferences.
WebLogic Portal lets you identify and retain information about non-authenticated visitors to your portals. When you enable anonymous user tracking, non-authenticated users receive a cookie after a predetermined time (30 seconds by default), and preference information is persisted in a database rather than in memory.
Each time an anonymous tracked user returns to the portal, the ID in their cookie matches the primary key in the tracked anonymous user database, their previous user properties are maintained, and your personalization and campaign rules will work for those users. When anonymous tracked users register in your portal, their user profile is moved from the anonymous tracked user database to the user database.
If users do not have cookies enabled or if they delete cookies frequently, there is no way to match the users with their existing records in the anonymous tracked user database, and on subsequent returns to the portal these users are treated as new anonymous users.
This feature enables you to track users before they register with your site, meaning you can present personalized content to an anonymous user over multiple sessions. You can also persist information about a user's behavior, provided cookies are enabled on the user's browser. This feature can be parameterized to exclude those who spend less than a designated period of time on your site, avoiding the expense of storing data on irrelevant users. Finally, should a tracked anonymous user choose to register with your site, the data collected on that user is persisted in the account of the newly-registered user.
If a TRACKABLE anonymous user remains at a site longer than the specified duration, the user is converted automatically into a TRACKED anonymous user, and a cookie with the tracking id is given to the user. That id is used as the primary key of the tracking EJBs associated with that user, so that when the session ends, the user's properties are persisted and available for the next visit.
If this TRACKED anonymous user returns, the tracking id in the user's cookie is used to retrieve the user properties from the database, and those properties may be used to enable campaigns to be run against the user.
Because users don't always remain at a site long enough to demonstrate interest, the duration of the initial visit is used as a configurable trigger. If this value is set to 30 seconds, a user that leaves after 25 seconds would not be remembered on the next visit to the same site. A 30-second or more user would be remembered, even without having registered.
You can target anonymous (non-tracked) users with personalized content using any personalization tool besides campaigns and behavior tracking--tools such as default (non-campaign) placeholders and content selectors. Campaigns and behavior tracking are not currently supported for anonymous, non-tracked users.
For example, if an anonymous user visits a portal and sets her preferences to "favorite color=purple" and "favorite hobby=reading," those values are persisted in memory and can be used to display personalized content and trigger campaigns while the browser session lasts. However, if the user closes the browser and revisits the portal, she has to re-enter her user preferences. Registered and anonymous tracked users have their preferences saved in a database.
While anonymous users do not retain a consistent store of user preferences from session to session, you can still provide a fair amount of interaction management functionality. For example, many personalization conditions are based on such things as generic HTTP session and request properties you define, dates and times, and personal session preferences that have no relationship to registered users and their profile properties. For example, you could display personalized content for anonymous users accessing your portal with a specific type of browser during a specific time frame.