Google Content Experiments (discontinued)

Google Content Experiments is suited for large and small organizations, no matter your organizational goals. It is not recommended for organizations that are only interested in qualitative data, as there are other tools for receiving specific user experience feedback. It is also not recommended that you implement tests without some sort of goal in mind.

Incentivized

• When you need to measure against event-based goals
• If you need to see how the test variations performed against secondary goals
• Given that the the platform requires you actually code a new page with a unique URL, this tool can be good for radical redesigns.
• Great insights into other information about your testing groups, like whether or not they're mobile, screen size, browser, or really any dimension available in GA.

• You can only optimise for one goal, so if you have several conversions, like phone call and email you need to do it manually.
• It seems not to work that well for pages with lower amounts of traffic - not great for new or niche sites.

Incentivized

Content Experiments just makes it is simple and easy to implement A|B tests. We will be evaluating other tools in search of a more robust system for multivariate and cross-page testing, such as Optimizely or Visual Website Optimizer. However, for basic testing, you can't really beat it.

Using the free tool, overall "live support" is limited. However, there are plenty of online resources to get started. If you need handheld support, it is best to upgrade the service or hire a developer through one of Google's partner agencies. There could be more support for understanding what makes a test useful or not.

Incentivized

Google Website Optimizer was a better product but has been discontinued. We have also used Test and Target , which has more features but we have been doing fine with Google Content Experiments. Most testing situations can be handled with Google Content Experiments.

Incentivized

• Doing good experiments/Optimize has helped to take out the guesswork of the things we want to implement.
• We have done fairly complex changes such as changing navigation and managed to see improvements outcomes immediately before we have to request developer.
• Our teams have become more data centric in how they approach changes.

Incentivized