Google Content Experiments integration

The instructions on this page are intended for self service accounts.Enterprise customers should contact their account managers for integration support.

ClickTale has updated the integration method for Google Content Experiments (formerly Google Website Optimizer), please make sure you choose the correct integration method based on the type of test you are running.

Contents

Google Content Experiments in Split test (A/B testing) mode, will redirect your entry page to a different page based on your configuration. While this is active you will not be able to play or do a report on your entry page in ClickTale.

How the integration Works

No special integration with ClickTale is needed.

GCE experiments contain test versions that are each on a different URL. All you need to do is filter by the URL of the version or compare the two URLs of the versions you want to compare in side-by-side heatmaps, for example.

GCE fix

The following fix prevents any errors in recording or playback for customers using both ClickTale and GCE.

Note: The ID in the code varies per test and needs to be changed to the ID you have been provided by from Google Content Experiments.
This will run Google Content Experiments A/B testing in any normal use of the page and not run it when doing ClickTale playback.

Google Website Optimizer

Website Optimizer has been integrated with Google Analytics as Content Experiments.

On August 1, 2012, Website Optimizer will no longer be available as a standalone product.

Multivariate testing feature has been removed from Google Content Experiments at the moment so the below information is deprecated as of August 1, 2012.

When using GWO Multivariate testing and ClickTale without correct code customization, the playback of the recorded pages and aggregation reports will not be accurate and will probably not display the combination that the user saw.

With the following integration, you will be able to see the correct variation for each visitor and also aggregate each variation separately in Heatmaps or Form Analytics reports.

Introduction

Let's assume we are integrating with a page that has 3 sections and 2 variations for each section.

Finding your GWO experiment ID

The experiment ID is the alphanumeric string immediately following experiment=. For example, in the URL:

Note: It’s best to keep the experiment ID in a config file along with the unique identifier for the experiment that you can see in the control script (....var k='2376510756',d=....). This way you will not need to copy paste it from page to page and so it will be convenient to use the same code for more than one multivariate experiment running at the same time on different pages.

With multiple multivariate tests on your site

If you have more than one multivariate test on your site and you are using ClickTale integration module or if you don’t want to change the tracking code each time you create another test please use the method explained below:

By using the code below you can define all the experiment IDs for all the MVT testing in your site. You will not need to change the code on the page if this is populated for example from your config file.

Add this JS code at the top part of the page (best place is to put it next to the ClickTale top script):