Visual Website Optimizer Destination

VWO is an all-in-one platform that helps you conduct visitor research, build an optimization roadmap, and run continuous experimentation. Their platform enables you to create a process-driven optimization, get benefits of a connected, unified view of the individual visitor and run A/B tests at scale without reducing performance.

The VWO Destination is open-source and you can browse the code on GitHub.

This document was last updated on July 26th, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, please let us know!

Getting Started

The first step is to make sure Visual Website Optimizer supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

WebMobileServer
📱 Device-based
☁️ Cloud-based

Because the VWO destination needs to be on the page right away, there are two ways for the VWO Javascript snippet to be loaded on your page. You can either:

  1. Add the Javascript snippet directly on your codebase by following the instructions in these docs from the VWO documentation. Make sure to paste the snippet inside yourtag above your Segment snippet!
  2. Have Segment include the Javascript snippet for you by toggling on the “Use Async Smart Code” setting and then including your Account ID in the “Account ID” setting. When both these settings are correctly set, you will not need to include VWO’s native snippet on your page as Segment will do this on your behalf.

Additionaly, to enable the destination please follow these instructions:

  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Visual Web Optimizer” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Toggle the destination on!

Send Experiment Data from VWO

When you enable the VWO destination, we set the option for “Send experiment data to other tools (as a track call)” to true by default and we will automatically collect the Experiment Viewed event as a track call.

Turn on VWO

This event supports the following semantic properties:

PropertyTypeDescription
experimentIdStringThe experiment’s ID.
variationNameStringThe variation’s human-readable name.

Example

analytics.track('Experiment Viewed', {
  experiment_id: 'home-page-title-2819',
  variation_name: 'Enterprise Solutions Synergy'
});

However, you can also send the Experiment data as traits of an identify call that can be routed to all other destinations you have enabled. You’ll just need to toggle on the “Send experiment data to other tools (as an identify call)” setting and we will send those experiment values as traits of the user. An example would look like this:

'Experiment: Home CTA': 'Create free account now'

Recording Variations

By default, we will take the variation data that is available in VWO and send that data to the other user-tracking destinations you have enabled in Segment automatically. That way, you can segment your analytics reports by the variations a user has seen.

For example, if you have an experiment called Home CTA and a visitor sees a variation called Create free account now, we will send the Create free account now value as the variation_name property of the Experiment Viewed event and/or as a trait of the user in an identify call (depending on your delivery settings).

Track Revenue Goals

The Track Revenue goal allows you to track revenue from purchases and other transactions on your website by attributing the revenue amount for every valid and successful transaction. In other to track these transactions, you’ll need to use our Order Completed ecommerce track event and include the revenue data as total. An example call would look like this:

analytics.track('Order Completed', {
  total: 25
});

Additional settings

Make Experiment Viewed Non-interactive

If you are using VWO together with Google Analytics, you can enable this setting to add the nonInteraction flag to your Experiment Viewed track events. This can help with low bounce rates.

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. This setting is only effective if “Use Async Smart Code” is set to “true”.

Settings Tolerance

The maximum amount of time (in milliseconds) to wait for test settings before VWO will simply display your original page. This setting is only effective if “Use Async Smart Code” is set to “true”.

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. This setting is only effective if “Use Async Smart Code” is enabled.


If you have any questions, or see anywhere we can improve our documentation, please let us know!