As mentioned in the previous section, profile groups created in the ACC are of class atg.targeting.DynamicContentGroup. If your system includes ATG Content Administration, you can also create profile groups through the ATG Business Control Center, as described in the ATG Business Control Center User’s Guide. Profile groups created in the ATG Business Control Center are called user segments, and are of class atg.targeting.html.UserSegment, which is subclass of a subclass of atg.targeting.DynamicContentGroup. Note that user segments created in the ATG Business Control Center cannot be edited in the ACC.
Some sites may define a large number of user segments. To help manage these segments, the ATG platform uses segment lists, which are specific subsets of the set of segments defined on the site. For example, if a site uses the ATG Commerce Affinity Selling feature, there is an AffinitySelling segment list that specifies the set of user segments to take into account in affinity calculations.
Segment lists are predefined for specific features and applications, but you need to specify the actual segments to include in these lists through the ATG Business Control Center. For more information, see the ATG Business Control Center Administration and Development Guide.
Segment lists are stored in the Personalization Repository, located at /atg/userprofiling/PersonalizationRepository. Each segment list is represented by a single repository item of type userSegmentList, which has these properties:
displayName– The name used in the ATG Business Control Center for the segment list; e.g., thedisplayNamefor theCommerceReportinglist is Commerce Reports.description– The description of the segment list displayed in the ATG Business Control Centergroups– A comma-separated list of the names of the segments; e.g.,YoungMen,Audiophiles,EarlyAdopters
Segment lists are versioned assets, and the Personalization Repository (on a system that includes ATG Content Administration) is a versioned repository that is included in the DPS.Versioned module. Therefore, when you build the application for your ATG Content Administration environment, you must be sure to include this module. Note that when you build the application for your production environment, you should not include the DPS.Versioned module; the Personalization Repository on the production site is a non-versioned repository that can be queried at runtime.
