- Integrate Adobe Analytics (Omniture SiteCatalyst) to read experiment data from Optimizely
- Set up custom conversion variables (eVars) and traffic variables (prop)
- Solve common issues with integration
Optimizely's integration with Adobe Analytics (formerly Omniture SiteCatalyst) lets you view the analytics details for visitors who have:
Seen a specific variation of your Optimizely experiment
Seen a specific experience of your Optimizely Personalization campaign
Are you using Adobe Tag Manager? Some customers have provided a third-party solution for completing this integration using Dynamic Tag Management DTM. This is not a supported use case, but some customers use it to integrate Optimizely experiments through DTM.
Enable in Optimizely
Enable the integration for your Optimizely project.
Go to an individual experiment or Personalization campaign you want to track in Adobe Analytics.
Under Manage Campaign, click Integrations.
Fill out the Adobe Analytics integration form by specifying a Conversion Variable and Traffic Variable.
Under Conversion Variable, select the custom conversion variables (eVar) you want Optimizely to use. The eVar should not be used by another part of your site or a concurrently running Optimizely experiment.
The sVariable is optional. Some sites use custom Adobe Analytics implementations with special sVariable names. The sVariable contains all of the tracking tags sent to Adobe Analytics for a given visitor. If you want to specify a custom sVariable, you can do so in the corresponding field when setting up the integration on an experiment level. If the parameter is omitted, Optimizely will use
Check the custom report for your Optimizely experiment
After you have enabled the integration, check the custom Adobe Analytics report for your experiment to ensure it works.
When you log in to your Adobe Analytics account, a dashboard appears (the example below shows SiteCatalyst 15):
To get to the Optimizely custom variable, select Custom Conversion > Custom Conversion XX-XX > Optimizely (vXX). The XX represents the eVar you selected when you enabled the Optimizely integration.
Click the Optimizely custom conversion to go to the custom report.
To check how specific custom events are performed across variations, click Add Metrics.
Drag the custom event you want to display from the Available Metrics list to the Report Data Columns Canvas list to add it to the report.
When you finish adding events to the report, click OK. You should see a modified report showing the custom event's conversion data.
If you are using Optimizely Web Personalization, filter the report for the words "holdback" to see only the data from visitors included in your Optimizely campaign.
Currently, Personalization also tracks events for visitors included in the campaign holdback. See Naming conventions for Third-party integrations.
To drill down the report by other parameters, click Broken Down by: None.
Set up a custom conversion variable
With custom conversion variables ("eVars") in Adobe Analytics, you can capture conversion events or other attributes specific to your webpage. Like custom variables in Google Analytics, you can use custom conversion variables to segment your reports for fine-grained analysis. When combined with integration in Optimizely, eVars let you segment your reports by your experiments and identify the best-performing variation.
When an Optimizely decision event fires, Optimizely will send an event to Adobe. The event contains the eVar. This allows you to create a report based on a specific eVar value.
To reserve an eVar for your Optimizely experiment:
Go to Report Suite Manager in Adobe Analytics.
Select Edit Settings > Conversions > Conversion Variables.
Click Add New eVar.
After adding your new eVar, choose a unique name, allocation type, cookie expiration, data type, and relation status. The default values are recommended:
Allocation: Most Recent (Last)
Expire After: Visit
Type: Text String
Status: Basic Subrelations
Allocation determines which eVar value should be associated with a given visitor. Suppose the visitor happens to trigger multiple events. In that case, you might want to attribute this to the last value they were assigned so that the revenue and participation metrics are attributed to this final value. Choosing "Linear" allocation divides the revenue and success goals evenly over all events. If you want to view your success events across multiple eVar values, you can do that with participation.
Troubleshoot your integration
Tools to help verify things are working correctly
Here are some tools to help debug an Adobe Analytics integration:
A Chrome Browser extension that detects when a tracking call has been made and what values have been sent along with it.
Identify the Adobe Analytics tracking call
The default implementation of Adobe Analytics uses this code to send a tracking call:
It is a tiny bit of code, but this function call sends out all Adobe Analytics tracking information for the pageview. By default, Optimizely assumes this will be
s, but this tracking call may have a different leading variable that is not
s if you are using a custom tracker name. If you can’t find a
s.t(); call on your page, search for anything resembling
.t() in case another call exists with a different leading variable name before the period.
When a decision event is made, Optimizely sends that event to Adobe Analytics as soon as possible, polling for the availability of the Adobe Analytics object. If the Adobe Analytics object is not ready when a decision is made, Optimizely checks back every 200 MS for 10 seconds to see if Optimizely can send the Adobe Analytics string. This helps with delayed activation experiments (and if they fall under delayed activation, it helps with geo-targeted experiments too).
Identify a Custom Tracker (sVariable)
This step is optional if you are using a default Adobe Analytics implementation. But if you notice a different variable name other than
s before the period for the
.t() tracking call, that will be the name of your custom sVariable. For example:
s variable name in this example is
foo, so you will need to modify your integration settings to reflect this:
Here is an example of an integration that's working for a custom tracker named
Here is an example of the
omntag when Optimizely populates eVar1 correctly:
Access to eVar/prop variables 50 through 100
Some older versions of Adobe Analytics do not work with all 100 eVar and prop variables available for assignment within Optimizely.
Access to variable slots 51 through 75 was added in Adobe Analytics Code Version H22 (pre-SiteCatalyst 15). You can find your Adobe Analytics Code Version number with the DigitalPulse Debugger tool. If you have an older version, limit your eVar and prop variables to 1 through 50 within Optimizely.
Access to variable slots 76 through 100 was added later, but if you’re having trouble populating them, try an eVar or prop in the range of 1 to 50 to see if that helps.