# Visual Website Optimizer (VWO) Destination

## About this integration

VWO is an optimization platform that helps you run experiments on your web platforms to derive insights from visitor behavior and harness the results to amp up your conversion rates. It lets you run experiments and personalize your platform for different cohorts, includes a full stack implementation, and lets you directly deploy changes based on your experiments.

[Mode How we forward source data to the destination: through Customer.io's servers or directly from our JavaScript client.](/cdp/destinations/getting-started/#connection-mode)

[Web sources Indicates whether or not this integration supports our the JavaScript client.](/cdp/sources/getting-started/#types-of-sources)

[API sources Indicates whether or not this integration supports our server libraries (Go, NodeJS, Python), API, Mobile SDK, and other data sources.](/cdp/sources/getting-started/#types-of-sources)

[Supported calls The API methods this integration supports.](/cdp/sources/source-spec/source-events/)

[Integration name The name of this integration if you want to enable or disable it in the `integrations` object.](/cdp/sources/source-spec/common-fields/#the-integrations-object)

Standard

[track](/api/cdp/#operation/track), [identify](/api/cdp/#operation/identify), and [page](/api/cdp/#operation/page)

VWO Cloud Mode (Actions)

Web

[track](/api/cdp/#operation/track) and [identify](/api/cdp/#operation/identify)

vwo-web

## There are two versions of this integration[](#there-are-two-versions-of-this-integration)

You’ll see two entries for Visual Website Optimizer (VWO) in our [integration catalog](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory), with one labeled *Web*. We typically recommend that you use the standard integration, the one *not* labeled “Web” when possible. The *web* version of this integration only works with our JavaScript client and does not pass data through Customer.io’s servers, which can make it hard to debug your integration, capture a history of events sent to the integration, and so on. Learn more about [Web integrations](/integrations/data-out/getting-started/#connection-modes).

## Getting started[](#getting-started)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Visual Website Optimizer (VWO)** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Vwo Account Id**: Enter your VWO Account ID
        
    2.  **Apikey**: VWO Fullstack SDK Key. It is mandatory when using the VWO Fullstack suite.
        
4.  Click **Enable Destination**.
    

### Actions[](#actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

Action

Default Trigger

Description

Track Event

`type = “track”`

Sends a track event to VWO

Identify User

`type = “identify”`

Maps visitor traits to the visitor attributes in VWO

Page Visit

`type = “page”`

Sends a page event to VWO

## Getting started: web integration[](#getting-started-web-integration)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Visual Website Optimizer (VWO)** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Vwo Account Id**: Your VWO account ID, used for fetching your VWO async smart code.
        
    2.  **Settings Tolerance**: The maximum amount of time (in milliseconds) to wait for test settings before VWO will simply display your original page.
        
    3.  **Library Tolerance**: The maximum amount of time (in milliseconds) to wait for VWO’s full library to be downloaded before simply displaying your original page.
        
    4.  **Use Existing Jquery**: If your page already includes JQuery, you can set this to “true”. Otherwise, VWO will include JQuery onto the page for you. VWO needs JQuery on the page to function correctly.
        
4.  Click **Enable Destination**.
    

### Web integration actions[](#web-integration-actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

Action

Default Trigger

Description

Track Event

`type = “track”`

Sends Segment's track event to VWO

Identify User

`type = “identify”`

Sends Segment's page event to VWO