Support Content Experiments

This is indeed something that would be very useful. Now, you have to add some custom code on your html.tpl.php file in order to accomlish this. I have posted an article on Drupal Planet regarding this: http://www.netstudio.gr/en/blog/how-use-new-google-content-experiments-a...

Should be great, please also make this available for 6.x

The old API is supported via the Google Website Optimiser module. There should be basis for keeping the functionality over there, or?

The old website optimizer is not available anymore. Google experiments is the new and only available testing tool by google.

Anyone working on a module for Google Content Experiments? I may be interested in collaborating.

subscribing

This would be awesome. Subscribing.

I've created a very rudimentary pass at this in just a few hours. It basically works in a very minimalistic way, with some bugs, and would love for those who are interested to help take some steps toward making this into a respectable module. I'm a little rusty in Drupal, myself, having done a lot more work in Wordpress, Rails, Sencha, and other frameworks as of late, but I needed this functionality in a Drupal project. http://drupal.org/project/content_experiments.

A note: pasting content experiments code into the node form creates a security issue because to make use of that, you'd have to run tainted code in the header of your website's pages. So, I set up the module to accept an experiment ID from Google. You paste that, and the module generates the JS.

Tricky issue. The problem is that the original page to experiment with may not be a node page...

Ideally this could be configured purely via paths (or path aliases). e.g.:

Enter Experiment ID: ______________________________

Choose original page path: "node/5" (or "articles/that-one-article" or "<front>")

And then this module would take care of inserting the proper script on the proper page.

@JordanMagnuson I've created an issue with Morris Singers project #2049895: more useful with paths

You can also achieve this using Context - https://drupal.org/project/content_experiments_context

@lsolesen Thanks for your patch. Your solution is working very good, it has solved my problem. Hope to get it merged soon in module.

I think we can implement this with context module integration at it's best.

Someone willing to sponsor this?

Closing in favor of the referenced case.