Experience Optimization legacy features
Experience Optimization legacy features are still supported for existing users, but are not recommended for new users.
- Configuring a Publication Target for targeting (deprecated)
If you are still using the old SDL Tridion-type publishing framework that was deprecated in SDL Tridion Sites, you manage Promotions and Triggers between SDL Tridion Sites and Fredhopper by configuring properties in the Targeting tab of a Publication Target. A Publication Target defines the information required to publish content in the deprecated publishing framework. - Setting Manage Promotions and Manage Experiments rights when using the deprecated publishing framework
Users only have access to Promotions or Experiments for which they have rights: you set these rights (a Manage Promotions right and a Manage Experiments right) for Users and User Groups on a Target Type. If you use the old publishing framework that was deprecated in SDL Tridion Sites 8, a Target Type specifies a user-friendly name for one or more Publication Targets. - Adding Experience Optimization to the deprecated Java/JSP API (in-process) Server Role
You need to install Experience Optimization presentation server-side components (JAR files and config files) in the Java/JSP Web application that contains API (in-process). - Adding Experience Optimization to the deprecated .NET API (in-process) Server Role
You need to install Experience Optimization presentation server-side components (DLL files, JAR files and config files) in the .NET Web application that contains API (in-process). - Adding Experience Optimization to the Content Service in an in-process setup
If your Experience Optimization implementation still uses the API (in-process) (a deprecated setup), copy different resources than when you use the API (RESTful). Also copy Google Analytics resources (if using) and Cartridges.