Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

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 integration is partner owned. Please reach out to the partner's support for any issues.
  • This destination is in Beta
(information)

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(link takes you to an external page) 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.

(information)

Info

The events and attributes that are transferred from Segment to your VWO account will appear under Unregistered Events(link takes you to an external page) and Unregistered Attributes(link takes you to an external page) sections, respectively. You need to save these events and attributes to VWO for further use.


Benefits of VWO Web Mode(Actions) vs VWO Classic

benefits-of-vwo-web-modeactions-vs-vwo-classic page anchor

VWO Web Mode (Actions) provides the following benefits over the classic VWO destination:


  1. From the Segment web app dashboard, navigate to Connections > Catalog.
  2. Under the Destinations tab, search for "VWO Web Mode (Actions)", and select the destination.
  3. Click Configure VWO Web Mode (Actions).
  4. Select the source that will send data to VWO Web Mode (Actions), click Next to enter the name of your destination, and click Save.
  5. 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
  6. 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.
  7. 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.
  8. Finally, enable the destination using the Enable Destination toggle switch and click Save Changes.

Property nameTypeRequiredDescription
Add Asynchronous SmartCodeboolean

Optional

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 Tolerancenumber

Optional

The maximum amount of time (in milliseconds) to wait for VWO’s full library to be downloaded before simply displaying your original page.


Settings Tolerancenumber

Optional

The maximum amount of time (in milliseconds) to wait for test settings before VWO will simply display your original page.


Use Existing JQueryboolean

Optional

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 IDnumber
required

Your VWO account ID, used for fetching your VWO async smart code.


VWO Web Mode (Actions) has the following presets

Preset NameTriggerDefault Action
Track EventEvent type = "track"Track Event
Identify UserEvent type = "identify"Identify User

Build your own Mappings. Combine supported triggers with the following VWO Web Mode-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Track Event

track-event page anchor

Sends Segment's track event to VWO

Track Event is a Web action. The default Trigger is type = "track"

Property nameTypeRequiredDescription
NameSTRING
required

Name of the event.


PropertiesOBJECT

Optional

JSON object containing additional properties that will be associated with the event.

Sends Segment's user traits to VWO

Identify User is a Web action. The default Trigger is type = "identify"

Property nameTypeRequiredDescription
AttributesOBJECT
required

JSON object containing additional attributes that will be associated with the user.