We recently worked with one our customers looking to implement personalization within their SDL Tridion environment. The client was looking to use either SDLâ€™s Experience Optimization (XO)* Â or Adobeâ€™s Target product.
Both tools are feature packed for creating personalized experiences. In the end the customer chose SDLâ€™s solution, the reasons for doing so were of a technical nature. This is unusual as itâ€™s normally the functionality of the tool that sways the decision for this type of tool. Given the technical nature, I thought Iâ€™d share them.
Why SDL XO was chosen over Adobe Target.
- Adobe Target is a cloud-based tool. The customer preference was to install and maintain the software on-premise.
- The client also wasnâ€™t comfortable in sending user data over to Adobeâ€™s servers.
- XO already integrates into the SDL Tridion CMS, this also includes the Experience Manager inline editing interface. The cost of creating such integration was a major factor.
- The XO interface is also unified with the SDL interface so thereâ€™s little in the way of training and familiarization required for the clientâ€™s internal teams.
- Target also required that some semantic structure be stored into their system. The client was wary that future redesign and new layouts would require greater overhead for teams managing data and layout across both systems.
* The software formerly known Smart Target