Experience Optimization architecture (deprecated in-process setup)
We recommend that you set up Experience Optimization to use REST API and microservices; however, you can still set it up in according to the deprecated, in-process architecture with most logic occurring in-process on the website. This is possible whether implementing Experience Optimization alone or implementing it in conjunction with Audience Manager.
The following diagram shows an example implementation of Experience Optimization where logic on the website, or "in process":
Content Manager-side extensions
- The Targeting Dashboard
- Experience Optimization Template Building Blocks for Templating
- Publisher extension DLL — adds information on Structure Groups, Folders, and Categories and Keywords (hierarchical information) into the transport package
Content Delivery-side extensions
The Content Deployer Extension for Experience Optimization sends content, published from the Content Manager using the Add to Experience Optimization Template Building Block, to the Elasticsearch database.
- Ambient Data Framework
-
The Ambient Data Framework is a Content Delivery module that provides a flexible and configurable framework for gathering and transforming all kinds of information about users visiting a website.
- Experience Optimization cartridges
-
Experience Optimization provides the Session cartridge for the Ambient Data Framework. This cartridge processes raw session data and adds the data to the Claim Store so that you can use session and visitor data as triggers for Promotions.
Additionally, if you have Audience Manager installed you can use the Audience Manager cartridge for the Ambient Data Framework to put Segments, Contact details and Contact extended details from Audience Manager into the Claim Store. You can then use these as triggers for Promotions.
- Management Service
-
The Experience Optimization Management Service enables the creation and editing of Promotions and Experiments in Content Manager.
Website requirement for Experience Optimization Page Regions
An Experience Optimization Page Region represents a physical region on a webpage that displays promotional content. You implement Experience OptimizationPage Regions and Promotions in your Page Templates using the Template Building Blocks provided. These generate custom tags or Server Controls, depending on whether you are running a Java or .NET website, respectively, that define a query for retrieving content. When the query is executed, Experience Optimization returns promotions matching the query and then gets the content items which it needs to display in the Promotion from the Storage Layer.