VWO Web Mode (Actions) Destination
Destination Info
- Accepts Page, Alias, Group, Identify, and Track calls
- Refer to it as VWO Web Mode (Actions) in the Integrations object
- This destination is not compatible with Destination Insert Functions.
- This destination is in Beta
Partner Owned
- This integration is partner owned. Please reach out to the partner's support for any issues.
Additional versions of this destination are available
This page is about the VWO Web Mode (Actions) Destination. See below for information about other versions of the VWO destination:
VWO is an optimization platform that allows websites to run experiments on their platforms to derive insights from visitor behavior and harness the results to amp up the conversion rate. Apart from experimentation, it also provides for personalization of the platform for different cohorts, full stack implementation, and direct deployment of the changes determined through experimentation.
The events and attributes that are transferred from Segment to your VWO account will appear under Unregistered Events and Unregistered Attributes sections, respectively. You need to save these events and attributes to VWO for further use.
Benefits of VWO Web Mode(Actions) vs VWO Classic
VWO Web Mode (Actions) provides the following benefits over the classic VWO destination:
- Support for Customer Data Platform (Data360). With the Web mode destination enabled, you will be able to transfer all the events and attributes into your VWO account through the Data360 module. You can use these events and attributes to create segments and metrics in your VWO campaigns.
Getting started
- From the Segment web app dashboard, navigate to Connections > Catalog.
- Under the Destinations tab, search for “VWO Web Mode (Actions)”, and select the destination.
- Click Configure VWO Web Mode (Actions).
- Select the source that will send data to VWO Web Mode (Actions), click Next to enter the name of your destination, and click Save.
- On the Basic Settings page that appears, configure the following details in the respective fields:
- Name of the destination
- Your VWO Account ID
- Settings Tolerance
- Library Tolerance
- In order for VWO to function properly, it needs jQuery to be loaded on your web page. If jQuery already exists, then turn ON the Use Existing JQuery toggle switch. Else, VWO will load a jQuery on your web page.
- To customize the mapping of actions, follow the steps in the Destinations Actions documentation on Customizing mappings. Mappings in Segment allow you to control the events and attributes that are sent to VWO.
- Finally, enable the destination using the Enable Destination toggle switch and click Save Changes.
Destination Settings
| Setting | Description |
|---|---|
| Add Asynchronous SmartCode | When enabled, Segment will load the VWO SmartCode onto the webpage. When disabled, you will have to manually add SmartCode to your webpage. The setting is enabled by default, however we recommended manually adding SmartCode to the webpage to avoid flicker issues. |
| 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. |
| Settings Tolerance | The maximum amount of time (in milliseconds) to wait for test settings before VWO will simply display your original page. |
| 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. |
| VWO Account ID | Required. Your VWO account ID, used for fetching your VWO async smart code. |
Available Presets
VWO Web Mode (Actions) has the following presets:
| Preset Name | Trigger | Default Action |
|---|---|---|
| Track Event | Event type = "track" |
Track Event |
| Identify User | Event type = "identify" |
Identify User |
Available Actions
Build your own Mappings. Combine supported triggers with the following VWO Web Mode-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Track Event
Sends Segment’s track event to VWO
Track Event is a Web action. The default Trigger is: type = "track"
| Field | Description |
|---|---|
| Name* | Type: STRINGName of the event. |
| Properties | Type: OBJECTJSON object containing additional properties that will be associated with the event. |
Identify User
Sends Segment’s user traits to VWO
Identify User is a Web action. The default Trigger is: type = "identify"
| Field | Description |
|---|---|
| Attributes* | Type: OBJECTJSON object containing additional attributes that will be associated with the user. |
This page was last modified: 30 Aug 2023
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!