Installing Experience Optimization (deprecated in-process setup)
Although we strongly recommend using the current RESTful, service-based setup, you can still install Experience Optimization on Content Delivery under the deprecated in-process setup. This section covers steps that are different for an in-process setup and you may need to refer to the main product documentation for additional steps.
- 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. - Experience Optimization with Audience Manager (deprecated in-process setup)
Audience Manager enables marketing departments to gather information about audiences, such as interests, preferences, and characteristics and use this information to target audiences. With Audience Manager installed, you can use Contact details and Segments as triggers for Experience Optimization promotions. - Adding Experience Optimization to your Java website
Copy and merge resources for Experience Optimization to your Java API (RESTful) role. Implementing Experience Optimization on a website requires a few of modifications of the website configuration files. - Adding Experience Optimization to your .NET website
Copy and merge resources for Experience Optimization to your .NET API (RESTful) Server Role, and then reference the Content Interaction Libraries (CIL). Implementing Experience Optimization on a website requires a few of modifications of the website configuration files. - Configuring Experience Optimization with the smarttarget_conf file (deprecated in-process setup)
Edit the smarttarget_conf.xml file in the configuration location of your website to configure Elasticsearch and Experience Optimization. - Configuring Claim forwarding for Experiments
When using the Experiments feature of Experience Optimization, you need to configure Claim forwarding and make sure that your list of Claims includes a Claim with the URI taf:request:cookies. - Configuring additional search engines for Experience Optimization
If you need to add additional search engines for Experience Optimization, you can do so by editing the smarttarget.referrers.xml. - Registering custom tags in Java-based Page Templates (deprecated in-process setup)
If you have a Java/JSP website, to use the Experience Optimization JSP Custom Tags, change all relevant Page Templates to add an instruction to register the Custom Tags to the top of every published webpage that uses these controls.