Profilers

Profilers are typically used to categorize an individual (usually the current site visitor) according to his or her user properties.

Besides a user's properties, profilers can be used to define other conditions based on such factors such as the current date and time, the type of browser the visitor uses, or other implicit and explicit application object properties. Profilers can also make decisions based on the current user's session attributes and request attributes and parameters, along with category and action counts.

Profilers can be constructed to define the conditions of arbitrarily named profiles, or can be defined in terms of other profilers.

For example, we can create a profile that will evaluate as true if a profile is in any, all, or none of a group of other profiles.

• Example: Simple profiler
  View an example of a simple profile that determines whether confidential company news articles will be shown to the current Web site visitor.
• Example: Nested profiler
  View an example of a nested profiler.
• Example: Category Count (implicit profiling)
  Get an overview of implementing category counts from a profile that will contain profile definitions for movies, cooking, and sports; this overview sets the profile for the category with the highest count.
• Example: Browser capability
  The browser capability stock object allows us to profile the browser the current Web visitor is using to view the site. View an example profile that checks the browser version to determine whether it is supported.
• Example: "Count of" (quantifiable condition)
  View an example demonstrating the use of "Count of".
• Example: Request attributes and session attributes
  Request values passed to the JSP or stored in the HTTP session can be referred to from rules. To refer to them in a rule, you must know the variables and their possible values.
• Example: Arithmetic operation
  View an example of a profile that uses arithmetic operations.

Parent: Rules