Commerce Reference Store uses a common approach to personalizing its content that involves a combination of targeters, slots, and scenarios. Targeters determine which content to show to individual customers. Slots function as placeholders in pages where customized content can be stored. Scenarios create the link between slots and targeters in the following way:
When a customer accesses a page that has a slot, the slot requests content.
Note: Commerce Reference Store has two types of pages that may contain slots, ATG-driven pages and Experience Manager-driven pages. ATG-driven pages have ATG slots implemented directly within them. Experience Manager-driven pages use cartridges that get their content from ATG slots. For more information on how ATG-driven pages use ATG slots, see the Personalization Programming Guide and the Personalization Guide for Business Users. For more information on how Experience Manager-driven pages use ATG slot cartridges, see the Using Cartridges in Commerce Reference Store chapter in this guide.
The slot’s content request initiates a scenario.
The scenario contains rules that tell it which targeter to run.
The targeter determines the appropriate content for the customer and returns it to the scenario.
The scenario returns the content to the JSP page and the slot is populated. Note that slots only store content. Other logic must exist on the JSP page to render the content:
The following section describes the targeters, slots, and scenarios implemented for Commerce Reference Store.