By default, the system initializes slots every time their corresponding scenario is triggered. For example, assume you have a scenario that watches for a visitor to log into the site, and then displays a “Welcome back!” image. Every time the visitor logs in during the period for which the scenario is active, the slot is initialized and the content is displayed.

In some circumstances, however, you might have a scenario that is triggered once only. For example, you might have a scenario that watches for a visitor to register and then populates a slot with an image containing a link to a promotion. The scenario is intended to wait for the visitor to click the link and then remove the link from the slot. Registration happens only once, so, in this case, the slot is only initialized once. However, the visitor may not click on the link during the first session after he or she registers. Unfortunately the link is displayed during the first session only because the scenario itself is not triggered for each session.

To change this behavior, check the Store Slot Persistently in Repository option. The system stores information about the slot in the profile repository (specifically, in the slotInstances property) so that its contents can be displayed to a visitor across multiple sessions.

This option corresponds to the persistent property in the slot component .properties file.

Important: As described above, persistent slots are particularly useful when you want to display content from session to session until a specific event occurs. However, persistent slots can have a negative effect on performance because their contents must be maintained by interfacing to the profile repository. For this reason, use them very sparingly and only when persistence is absolutely required.

loading table of contents...