Running a Web site on the Personalization module creates any number of events that the system can recognize and act upon. You can use events to change component properties and to implement logging and reporting on the performance of your site. For example, you could trigger an event each time a user logs into your site. You could use this event to log and report on the number of people logging in to your site. You could also have a profile attribute named lastActivity, and use the login event to reset the value of the lastActivity property in all users’ profiles each time they log in.

The ACC’s Targeting >Tracking Sensors window provides an interface for creating actions that are implemented in response to specific events. This chapter describes the Personalization module components that exist in the ACC’s Tracking area. It includes the following sections:

Note:The tracking mechanisms described in this chapter are disabled by default, because scenarios and scenario recorders provide a more comprehensive means for performing event tracking (see Using Scenario Recorders). However, if you have existing ATG applications that use tracking sensors, you can enable tracking sensors by setting the Nucleus property sendD4StyleEvents to true. For more information, see Implementing Events in the Converting DPS Code chapter of the Dynamo 4.5-5.0 Migration Guide.

Correspondingly, the Tracking Sensors window does not appear by default in the ACC. To display the Targeting > Tracking Sensors window, go to the People and Organizations > Control Center Groups window and enable the Targeting: Tracking Sensors Group UI Access Privilege for the appropriate group of users. If you do not have administrator privileges in the ACC you may not be able to modify this setting.

loading table of contents...