Experience Manager gives business users the ability to choose layouts and content based on a shopper’s location within an application. To make these layout and content choices, the business user configures prioritized triggering rules that control what gets rendered. One of the criteria that can be incorporated into triggering rules is the Endeca user segment. The ATG-Endeca integration leverages this Endeca user segment functionality to enable the use of sites and site groups in Experience Manager triggers. To incorporate sites and site groups in triggers, the following happens:
An administrator or business user manually adds a set of Endeca user segments that correspond to the ATG sites and site groups to the Workbench, thereby making them available in Experience Manager. This allows the ATG sites and site groups to be used in triggers configured by business users.
Experience Manager business users configure triggering rules using the manually added user segments.
Every time the ATG Platform calls the Assembler, it passes site context information (the current site and its site groups) for the current request and shopper.
The passed information allows the Assembler to return the correct content for the request, based on the configuration set in Experience Manager.
The following sections provide more detail on these general steps.
Note: The Oracle ATG Web Commerce Platform provides functionality that allows ATG user segments that have been defined in the Business Control Center to be automatically shared with Experience Manager and used as triggers for cartridges. While it is similar, this Platform functionality is limited to ATG user segments and does not accommodate sites and site groups. Therefore, Commerce Reference Store implements the additional functionality described in this section to allow sites and sites groups to be used as triggers. For more details on how ATG user segments are automatically shared with Experience Manager, see the ATG-Endeca Integration Guide.
