Integrate Google Universal Analytics

🚧

Important

Google Analytics 4 (GA4) replaced Google Universal Analytics (UA) in 2023. To set up an integration between GA4 and Optimizely Web Experimentation, see Integrate Google Analytics 4

This topic describes how to:

• Integrate Google Universal Analytics to read data from Optimizely Web Experimentation.
• Add Google Universal Analytics integration code to your page.
• Track Google Universal Analytics metrics as experiment goals.
• Create custom dimensions and reports in Google Universal Analytics to track and report on Optimizely Web Experimentation data.

Here are a few reasons to integrate:

• Get a direct view of how Optimizely Web Experimentation experiments affect the metrics you track in Google Analytics
• See Google Analytics data for each variation in your experiment (or experience in a campaign)
• Filter your Google Analytics reporting by visitors who were successfully included in an Optimizely Web Experimentation experiment and exclude those who weren't

Looking for a different Google Analytics integration? See Google Tag Manager. To learn more, you can also check out these great write-ups by Geoff Kenyon, Trevor Fox and our Solutions Partner, Vertical Nerve.

You can also download a checklist to help you manage this procedure.

Prerequisites

First, enable Google Analytics in your Optimizely Web Experimentation project if you haven't already.

Here are a few other details to keep in mind:

• To integrate Optimizely Web Experimentation with Google UA, you'll need an available custom dimension in Google Analytics to populate with Optimizely Web Experimentation experiment data.
• Use the number (or index) of the custom dimension to configure and send data to your Optimizely Web Experimentation experiment. To access your Google UA custom dimensions and create one for Optimizely Web Experimentation, scroll down to the Create a Google UA custom dimension section below.
• Use one custom dimension per concurrently running experiment or campaign to keep experiment names and variations from overwriting each other.
• If your page's Google UA setting has the setDomainName function call on your page, make sure that it doesn't use a leading period or "www".
• Your Optimizely Web Experimentation experiment or campaign must be running for Google UA integration to work.

📘

Note

• Your Optimizely Web Experimentation and Google UA snippets can be placed in any order.
• You do not need to make theactivateUniversalAnalyticsAPI call.
• Optimizely Web Experimentation does not send data with the 'pageview'. It sends a separate 'non-interaction event', independent of the 'pageview'.

The reason for having one custom dimension per concurrently running experiment is data attribution.

For example, suppose Experiment A and Experiment B both use Custom Dimension 1. If a visitor lands on Experiment A within page 1 and lands on Experiment B on page 2 within the same session, the visitor's actions are attributed only to Experiment B from that point on.

In the same scenario, if Experiment A and Experiment B have their own unique custom dimensions, Experiment A will continue to collect data for the visitor even after they're bucketed into Experiment B.

Enable Google UA integration

Optimizely Web Experimentation uses Google UA's custom dimensions to tag your visitors with the experiments and variations to which they've been added. Here are the steps in configuring Optimizely Web Experimentation to start sending this information to Google UA:

1. Choose an experiment.

2. In the Manage Experiment menu, click Integrations.

3. In the Google Universal Analytics section, click to select the Tracked checkbox.

4. Select the custom dimension that you want Optimizely Web Experimentation to use. Remember, this is a Google UA custom dimension, not the Optimizely Web Experimentation feature. Make sure that this custom dimension isn't already in use for another part of your site or a concurrently running Optimizely Web Experimentation experiment.

   🚧

   Important

   After you create your custom dimension in Google UA, Google will prompt you with example JavaScript for your page. However, enabling the Google UA integration means that you don't need to include the UA setDimension code on your page. If you include the ga('set', 'dimension1', dimensionValue); code on your site, you might overwrite the Optimizely Web Experimentation-Google UA integration.

5. If you use a custom event tracker other than the default (usually named t0 by Google UA), specify it in the Custom Tracker (optional) field. This changes Optimizely Web Experimentation's integration call to use the custom event tracker instead of the default. For example, if your website uses this call:

   ga('tracker2.send', 'pageview');
   

   ...you'll enter tracker2 in the Custom Tracker (optional) field, and Optimizely Web Experimentation will integrate with tracker2 instead of the default tracker.

📘

Note

If you are using Google's global site tag gtag.js tracking code, read the additional step section about the necessary custom tracker naming convention.

Additionally, if you have input a tracker name into Optimizely Web Experimentation's integration and are unable to see the event send successfully, use Google's Analytics Debugger extension to determine the trackers created on the page. Check if the non-interaction event is being ignored as this would indicate the tracker was never created by Google and is usually the reason the event fails.

Create a Google UA custom dimension

To integrate Optimizely Web Experimentation with Google UA and view reports based on the integration data, you need a Google UA custom dimension. This custom dimension and the name you give it are used to create reports that leverage your Optimizely Web Experimentation integration data for filtering.

Here's how to create a Google UA custom dimension:

1. Log into your Google UA account as an Admin and click the Admin tab.

2. Click Custom Definitions and select the Custom Dimensions sub-item.

   If you see the custom dimension you want to integrate your Optimizely Web Experimentation experiment with, note its name and index number--no need to add a new one.
   If you want to integrate with a custom dimension that is not listed, you do need to create a new one. Click New Custom Dimension, and give the new dimension a name and a scope.

3. Click Create.

Your custom dimension is now available for integrating with Optimizely Web Experimentation experiments.

Although you should integration scope at the session level, you can configure your integration scope at the user level. Optimizely Web Experimentation's default integration uses session-level scope to minimize the possibility of overwriting your experiment data sent to Google UA. But if you track complex conversions that span multiple sessions, you might prefer a user-level scope. Choose the scope that is better for the types of conversions you want to track.

For example, you might want a session-level scope if the experiment is running site-wide or if a visitor will always go back through the experiment pages before converting. But you want a user-level scope if it is possible for a user to leave the site, then come back and convert without seeing the experiment again.

If you do this, be cautious of reusing custom dimensions in Google UA. For consistency between Google UA and Optimizely Web Experimentation's Results page, set the Google UA reporting range to the same duration as your experiment.

See Google's documentation on scoping for details.

Create a custom report

To see reports on your experiments within Google UA, you need a custom report for each experiment. 

1. Log into your Google UA account and click the Customization tab.

2. Set up a custom report for each experiment with which you have integrated Google UA: click New Custom Report, give the report a title, and add the metric groups you want to view in the report.

3. To filter the report for only your Optimizely Web Experimentation experiment, choose the custom dimension you set up as one of the Dimension Drilldowns.

4. Add the custom dimension in the Filters section.

5. Enter the regular expression ("regex") match for the experiment ID or campaign ID you want to filter for. Use Experiment IDs for Optimizely Web Experimentation Experiments and Campaign IDs for Optimizely Web Personalization Campaigns. This will ensure that your report shows only the Google UA data for that particular experiment.

   

   🚧

   Important

   Leave the fields in the Filters section empty when you're creating a custom report for an iOS experiment.

6. Click Save.

Now you can access your report and update the date filter as needed!

Confirm your integration

Google UA's custom dimensions contain visitor-specific information that can be sent along with events and pageviews. It can take up to 24 hours to populate that data into Google UA, but the custom dimension is set immediately when you integrate Google UA and Optimizely Web Experimentation. This means you can confirm that the custom dimension is set correctly with the Google Analytics’ debugger tool.

Using the debugger tool, look for the variable cd[x], where x is the slot that corresponds to the Optimizely Web Experimentation experiment. The variable is set with the Optimizely Web Experimentation experiment, followed by the variation you were bucketed into. Here's an example:

dimension7 (&cd7) Optimizely_Onboarding (1645002506): Variant#1

Troubleshooting your Google UA integration or seeing discrepancies in your reports? See GA troubleshooting article.

📘

Note

When a decision event is made, Optimizely Web Experimentation sends that event to Google UA as soon as possible, polling for availability of the Google UA object.

If the Google UA object isn't ready when a decision is made, Optimizely Web Experimentation checks back every 200 ms for 10 seconds see if Optimizely Web Experimentation can send the UA string. This helps with delayed activation experiments (and if they fall under delayed activation, it helps with geo-targeted experiments too).

Additional step for gtag.js tracking code

Google Analytics offers two different tracking code blocks: the traditional analytics.js and the global site tag gtag.js. If you are using gtag.js you will need to specify a custom tracker name (per step 1-5 above). This tracker is generated by Google and follows the naming convention of gtag_UA_XXXX_X where UA_XXXX_X is the tracking id. For example if your tracking id is UA-12345-1 , your custom tracker should be gtag_UA_12345_1 :

If sent successfully, you should use the Google Debugger extension to confirm that the GA command with the analytics string was sent to Google Analytics. That command may look like the following:

 Running command: ga("gtag\_UA\_12345\_1.send", "event", "Optimizely",  
  "Assigned To Campaign", {nonInteraction: true, dimension1:  
  "experimentName(experimentId):variationName(variationId)"})