Webtrends Optimize Leaves Much to be Desired
Overall Satisfaction with Webtrends Optimize
Webtrends Optimize is being used across the organization primarily for A/B testing, but is also being leveraged for it's targeting capabilities.
Pros
- Intuitive test set-up makes for a low learning curve.
- Ability to create custom data tables which enable exporting of visitor level data for more in-depth analysis outside of the Webtrends Optimize platform.
- Visual Editor WYSIWYG interface enables non-technical users to easily execute basic tests.
Cons
- Inability to configure multiple segments or targets within a single test - a separate test must be set up for each individual segment - which leads to significant inefficiencies in both test set-up and reporting. This makes segmentation discovery difficult, and hinders an effective targeting strategy.
- There are no pre-configured integrations with other data source - integrations must be done client-side.
- We've experienced high timeout rates compared to other tools that we've used, which results in a relatively high number of visitors that are served the default content and are not included in the test. This presents several issues, but one being that it can take significantly longer to reach sufficient sample size for a test.
- More extensive documentation and support content pertaining to some of more advanced topics (e.g. data tables, integrations) would be helpful.
- It has helped to inform content strategy and increase content consumption.
- It has helped to create a data-driven culture within the organization.
Evaluating Webtrends Optimize and Competitors
- Price
- Product Usability
- Existing Relationship with the Vendor
Using Webtrends Optimize
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Technical support not required Consistent Quick to learn Convenient Feel confident using Familiar | None |
- Creation of new projects and tests
- Management of test state and lifecycle
- Quality assurance features
- Set up of multiple segments and/or targets for an individual test
- Navigation and consumption of the reporting interface
Comments
Please log in to join the conversation