VWO Destination Config Reference

VWO (Visual Website Optimizer) is an A/B testing destination that runs only in web device mode. RudderStack’s JavaScript SDK passes identify traits and track events to VWO in the browser, prefixing each trait and event name with rudder., and can report the variations VWO applies back to RudderStack as events.

In a VWO destination spec:

• type: vwo
• definition_version: 1

Sample configuration

version: rudder/v1
kind: destination
metadata:
  name: vwo-prod
spec:
  id: vwo-prod
  display_name: VWO Production
  type: vwo
  definition_version: 1
  enabled: true
  config:
    account_id: "{{ .VWO_ACCOUNT_ID }}"

    send_experiment_track: true
    send_experiment_identify: true

    is_spa: true
    library_tolerance: "2500"
    settings_tolerance: "2000"
    use_existing_jquery: false

    event_filtering:
      whitelist:
        - Order Completed
        - Signed Up

    connection_mode:
      web: device
    consent_management:
      web:
        - provider: oneTrust
          consents:
            - analytics

The above example sets the SmartCode keys, which take effect only when the page has the SDK load VWO’s SmartCode — see SmartCode settings.

Config keys

config accepts only the keys listed below. The shared config key rules cover unknown keys, defaults, and immutability.

VWO runs only in web device mode. The SDK forwards identify and track calls to VWO, and also records an Order Completed event’s total — or revenue, when total is absent — as a VWO revenue conversion. See Tracking revenue goals.

Connection

Experiment reporting

These keys have the SDK report each variation VWO applies to a visitor back to RudderStack, so the other destinations connected to the source can analyze experiment results.

send_experiment_identify takes effect only when send_experiment_track is also true — the SDK listens for applied variations only when send_experiment_track is on. Set both to get the identify traits.

SmartCode settings

These keys configure VWO’s SmartCode snippet. The SDK adds SmartCode to the page — with account_id and these settings — only when the page’s load call opts in through its integration options:

rudderanalytics.load(WRITE_KEY, DATA_PLANE_URL, {
  integrations: {
    VWO: {
      loadIntegration: true
    }
  }
});

Without that option, the SDK expects VWO’s SmartCode to be on the page already, and neither account_id nor the four keys below have any effect. See Loading the VWO SDK.

Event filtering

Every source connects to VWO in device mode, where the SDK applies the filter, so the filter applies to track events from every source you connect.

event_filtering:
  whitelist:
    - Order Completed

Per-source keys

Both keys are objects keyed by the local source type — the tokens listed under Source types. A key naming a source type this destination doesn’t support fails validation.

connection_mode:
  web: device

Source types

VWO accepts events from these source types in the mentioned connection modes:

VWO accepts only web sources, and only in device mode — the SDK runs VWO in the browser, and no events pass through RudderStack’s servers. See RudderStack Connection Modes.

Connect a source

An event stream connection to this destination is checked against two rules at validate time.

The source’s type must be supported. VWO accepts only web, the type a JavaScript source resolves to. Every other source resolves to a type it doesn’t accept — an iOS source to ios, an Android source to android, and webhook and server-side SDK sources to cloud — and reports, for example:

destination 'vwo-prod' (type 'vwo') does not support source 'my-ios-app':
source type 'ios' is not among supported source types: web

The destination config must carry a connection_mode entry for that source type. This lives on the destination spec, not on the connection spec. Without it:

destination 'vwo-prod' config has no 'connection_mode' entry for source type 'web'

VWO needs no additional config keys to connect a web source.

Secrets

account_id is the only secret key. Write it as a {{ .VAR }} reference and supply the value at apply time:

config:
  account_id: "{{ .VWO_ACCOUNT_ID }}"

export RUDDER_VWO_ACCOUNT_ID="..."
rudder-cli apply

# or
rudder-cli apply --var-file secrets.vars.yaml

Note that:

• rudder-cli import writes only the secrets the API returns, as {{ .VAR }} references, and leaves the others out. Add any secret key it leaves out, then supply the variables before you apply — see Secrets.
• The account ID is embedded in the page’s JavaScript, so masking it protects your YAML, not the value itself.

See How to Use Variable Substitution in Rudder CLI.

Changes by release

No changes since this type became available.

For changes across every destination type, see Destination Type Changes by Release.

See more

• VWO Destination for loading SmartCode, experiment reporting, and revenue tracking
• Destination Type Reference for Rudder CLI for the rules shared across destination types
• Destination YAML Reference for the spec envelope