As explained earlier in this chapter, you can use scenario elements, specifically the Change element, to update any property in your profile repository. The profile repository, however, also contains a property called Scenario Values that your application developers can set up to store any additional information about each visitor that you gather from scenarios – perhaps information that is valuable but of only occasional importance. The property can store more than one value at a time. In this case, the values are called “keys,” and when you use the Scenario Values property in a scenario, the ATG Control Center prompts you to specify the key to change.
Example: You decide that, for a few months, you will keep track of visitors who come to your site between the hours of 2:00 AM and 5:00 AM. Your application developers set up the Scenario Values profile property so that one of its keys is latevisitor
and the possible values for this key are true
and false
. You create the following scenario:
This scenario watches for people to log into the site between the specified times, and then it changes the latevisitor
key in the Scenario Values property to true
. You can now use this value to personalize site content _in the same way that you would use any other profile property – for example, you can use it as a way to filter site visitors in another scenario or in a content targeter.
Note also that the Scenarios module includes a scenario element called Set Variable that you can use to track any type of information you want for the duration of a single scenario segment only. See Using Action Elements in Scenarios for more information.