Apps maintained by third-parties

Several useful apps have been developed by other companies to enable their products to work seamlessly with Optimizely Web Experimentation. In most cases, the documentation for those integrations is maintained by the developers. This article provides you with a list of these integrations and links to the relevant documentation and support resources.

If you use Amplitude and Web Experimentation or Optimizely Personalization, you can enable the Amplitude integration to merge your Optimizely experiment and variation data into Amplitude with your other dimensions and metrics from your web analytics. The integration between Amplitude and Optimizely helps you understand your visitors' visit duration, bounce rate, and more.

This integration uses Optimizely's custom analytics extensions and is built and managed by Amplitude. To get the Amplitude integration started, see Amplitude's Knowledge Base article.

For further support with this integration, contact Amplitude.

If you use ContentSquare and Optimizely, you can enable the ContentSquare integration to better understand how and why users are interacting with your digital platforms, based on experiments and visitors.

The integration between ContentSquare and Optimizely lets you analyze user interactions for each variation, helping you understand why your experiments win and enabling you to see and quantify the change in user behavior.

To get the ContentSquare integration running, follow ContentSquare's integration guide.

If you use Decibel Insight and Optimizely, you can enable the Decibel Insight integration (redirects to Medallia; login required) to collect variation information on pages where you are using both Optimizely and Decibel Insight.

With this integration, you can use Decibel Insight features to uncover variation-specific visitor behavior information. This helps you understand exactly how visitors behave for different Optimizely variations.

Before you integrate Decibel Insight, ensure that you disable the Mask descriptive names in the project and third-party integrations option in your Optimizely project Privacy Settings.

To get the integration started, follow the Decibel Insight integration guide.

Since Decibel Insight built this integration, contact them for support.

If you use Econda and Optimizely, you can view the Econda documentation to find out how to enable the Econda with Optimizely to merge your experiment and variation data in Econda Analytics with your other dimensions and metrics from your web analytics.

The integration between Econda and Optimizely helps you understand your visitors' visit duration, bounce rate, etc.

To get the Econda integration started, follow Econda's integration guide on their documentation. Optimizely provides the integration code and the steps for setting this integration up. You can also reach out to your Optimizely support or Customer Success Manager for assistance on getting this integration running.

Since Econda built this integration, contact them for further support, through their website.

You can turn on your Fivetran and Optimizely integration in minutes. Fivetran’s zero-maintenance connector then ETL's all of your raw Optimizely data into your Data Warehouse, enabling Optimizely users to blend their Optimizely data with data from their other business applications to gain deep insights.

To get the Fivetran integration started, follow Fivetran's setup guide.

Since Fivetran built this integration, reach out to them for support. Find their contact information on their support website..

If you use Mouseflow and Optimizely, you can enable the Mouseflow integration to filter recording lists, heatmap lists, funnels, and form analytics reports based on your experiments and variations.

The integration between Mouseflow and Optimizely helps you understand how visitors to your site click, move, scroll, and browse in different experiments and variations.

To get the Mouseflow integration started, follow Mouseflow's integration guide. Since Mouseflow built this integration, contact them for support on their contact website.

If you use SessionCam and Optimizely, you can enable the SessionCam integration to see replays of visitors to your site in Optimizely experiments and variations.

The integration between SessionCam and Optimizely helps you understand how visitors to your site click, move, scroll, and browse in different experiments and variations, as well as automatic machine-learning powered suggestions for areas on your site where visitors struggle the most.

To get the SessionCam integration started, follow SessionCam's integration guide.

Since SessionCam built this integration, reach out to them for support.

To integrate Optimizely with Segment, see their documentation.

Analytics strings are tags that identify the experiment and variation IDs are associated with data you are tracking within a third-party integration like Google Analytics or Adobe Analytics. When you create a custom report within the integrated tool, the experiments and variations that you are tracking are listed by their assigned analytics strings.

For example, if you integrate Google Analytics (GA) with Optimizely, GA places a custom dimension on your website to track the data you specify for visitors. You can target this GA custom dimension in Optimizely to track the actions you have set up in GA for visitors in your Optimizely experiment. To define these visitors,

Optimizely automatically tags the GA custom dimension with the experiment and variation ID (in the form of analytics string). When you filter your data or create custom reports in GA, you see the analytics string so you can identify which Optimizely experiment and variation the visitor was allocated to.

Optimizely uses a consistent format for analytics strings, so understanding the format helps you identify experiments and variations when you are reading reports in third-party integrations. Experiments and campaigns created after 3:00 p.m. Pacific Time (PT) on May 23, 2017, use the updated analytics string format described below.

Experiments and campaigns created before 3:00 p.m. PT on May 23, 2017, use the old analytics string format, but they can be converted to use the new string format. For more information, contact your Customer Success Manager.

The general analytics string format for A/B test experiments is: experiment_name(experimentID):variation_name(variationID)

The general analytics string format for Personalization campaigns is: campaign_name(campaignID):experiment_audience_string(experimentID):variation_name(variationID)

In both cases, all IDs are integers.

Experimentation analytics strings when your project settings are not set tomask descriptive names

Scenario: the visitor is bucketed in a variation.

Scenario: the visitor is not bucketed in a variation because the visitor is excluded by traffic allocation.

Experimentation analytics strings when your project settings are set tomask descriptive names

Scenario: the visitor is bucketed in a variation.

Personalization analytics strings when your project settings are not set tomask descriptive names

Scenario: The visitor is bucketed in a variation in an experiment with no audience.

Scenario: The visitor is bucketed in a variation in an unnamed experiment with audiences.

Scenario: The visitor is bucketed in a variation in a named experiment.

Scenario: The visitor is placed in the campaign holdback.

Personalization analytics strings when your project settings are set tomask descriptive names

Scenario: The visitor is bucketed in a variation in an experiment with no audience.

Scenario: The visitor is bucketed in a variation in an experiment with audiences.

Scenario: The visitor is placed in the campaign holdback.