--- title: Integrate Adobe Analytics slug: web-experimentation/docs/integrate-adobe-analytics docTags: createdAt: 2026-07-23T11:40:26.754Z --- :::hint{type="info"} This is a third-party integration and is not an Optimizely subprocessor. See Optimizely's [Third-Party Add-Ons & Platform Integration Terms](https://www.optimizely.com/legal/third-party-add-ons-platform-integration-terms/). ::: Optimizely Web Experimentation's integration with Adobe Analytics lets you view the analytics details for visitors who have seen a specific variation of your Optimizely experiment or a specific experience of your Optimizely Web Personalization campaign. ## Enable in Optimizely Web Experimentation 1. [Enable the integration](docId\:tTE08Ac7s-Gt6YpHJlVQn) for your Web Experimentation project. 2. Go to an individual experiment or Personalization campaign you want to track in Adobe Analytics. 3. Click **Integrations**. 4. Select the custom conversion variables (`eVar`) you want Optimizely to use under **Conversion Variables**. The `eVar` should not be used by another part of your site or a concurrently running Optimizely experiment. 5. (Optional) Add an `sVariable`. Some sites use custom Adobe Analytics implementations with special `sVariable` names. The `sVariable` contains all tracking tags sent to Adobe Analytics for a given visitor. You can also specify a custom `sVariable`. If no parameter, Optimizely uses `s` by default. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/9aDr20gBfPDssnzxWy-NP_24eb289-adobeanalyticsenable.png) ## Check the custom report for your experiment After enabling the integration, check the custom Adobe Analytics report for your experiment to ensure it works. You can find the custom variable with the following steps: 1. Select **Custom Conversion > Custom Conversion XX-XX > Optimizely (vXX)**. The **XX** represents the `eVar` you selected when you enabled the Optimizely integration. 2. Click the Optimizely custom conversion to go to the custom report. 3. Click **Add Metrics** to check how specific custom events perform across variations. 4. 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. 5. Click **OK** when finished. You should see a modified report showing the custom event's conversion data. If you are using Personalization, filter the report for the words **holdback** to see only the data from visitors included in your campaign. Personalization also tracks events for visitors included in the campaign holdback. See [Naming conventions for Third-party integrations](docId\:aboSXIz13IEnvRbNKnuX9). ## Configure a custom conversion variable Custom conversion variables (`eVars`) let you capture conversion events or other attributes specific to your webpage. When combined with integration in Web Experimentation or Personalization, `eVars` let you segment your reports by your experiments and identify the best-performing variation. When an Optimizely decision event fires, Optimizely sends an event to Adobe with the `eVar`. This lets you create a report based on a specific `eVar` value. To reserve an `eVar` for your Optimizely experiment, complete the following: 1. Go to **Report Suite Manager** in Adobe Analytics. 2. Select **Edit Settings > Conversions > Conversion Variables**. 3. Click **Add New eVar**. After adding your `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 is associated with a given visitor. If the visitor triggers multiple events, for example, you might want to use the last value they were assigned for revenue and participation metrics. 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 You can use a [Chrome Browser extension](https://chrome.google.com/webstore/detail/adobe-experience-platform/bfnnokhpnncpkdmbokanobigaccjkpob/related) that detects when a tracking call was made and what values were sent. ### Identify the Adobe Analytics tracking call By default, Adobe Analytics uses `s.t();` to send a tracking call. This function call sends out all Adobe Analytics tracking information for the pageview. By default, Optimizely assumes this is `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 cannot find `s.t();` on your page, search for `.t()` to see if there is a call with a different leading variable name before the period. When a decision event is made, Optimizely sends that event to Adobe Analytics when possible, looking for the availability of the Adobe Analytics object. If the Adobe Analytics object is not ready when a decision is made, Optimizely checks every **200 MS** for **10 seconds** to send the Adobe Analytics string. This helps with delayed activation experiments and geo-targeted experiments. ### Identify a Custom Tracker (`sVariable`) This step is optional if you use a default Adobe Analytics implementation. If you notice a different variable name other than `s` before the period for the `.t()` tracking call, that is the name of your custom sVariable, such as `foo.t();`. You must modify your integration settings to reflect the custom variable name. ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/sxJrGjeM7ZS1_TnRphTP5_4a05a9a-image.png) The following is an example of a working integration for a custom tracker named `omntag`: ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/P-_37Z-7Km4W85P8QgoNz_08f1aa5-image.png) The following is an example of the `s` object `omntag` when Optimizely populates `eVar1` correctly: ![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/mpT2CWYzk8f2OIdYOl2lk_2fca802-image.png)