Not a bad tool, but not for the code-shy
May 13, 2014
Not a bad tool, but not for the code-shy
Score 6 out of 10
Vetted Review
Verified User
Overall Satisfaction with Google Content Experiments
I used to train marketing and development folks on how to use Google Content Experiments. We used it primarily when we needed to tie success of the test to a non-destination URL type goal (e.g. event triggered). Given that these non-destination URL goals were already setup in GA, it was easier to configure content experiments to measure against these goals than other testing tools. Additionally, we could see how the testing groups performed against other goals on the site, including both destination URL goals, engagement goals, and event-based goals.
- 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.
- Not a great solution for people who don't have the ability to code a page from scratch, or need to implement a test without the help of IT. This tool requires implementation of a few different code snippets on different pages and the ability to code a new page. If you're looking for a WYSIWYG editor - try Optimizely.
- More insights about our visitors
- Optimizely,Visual Website Optimizer,UnBounce
GCE isn't better or worse than any of these, it's just different. When I have the time to build a new page, setup the testing scripts, and go - then I'll use GCE. If I'm doing multivariate I use VWO. If I'm testing a quick button or headline change, I use Optimizely or UnBounce.