VWO (Visual Website Optimizer)
Send supplemental track events to VWO Data360 with HIPAA-compliant privacy controls, enabling experimentation insights while protecting patient data.
Overview
The Ours Privacy VWO integration allows you to send supplemental track events to VWO's Data360 platform while maintaining strict privacy controls over PII and PHI. Events are routed through Ours Privacy servers, giving you the ability to redact, hash, or modify sensitive data before it reaches VWO.
Supplemental Events Only: This destination sends supplemental server-side events to VWO. You must continue loading the VWO JavaScript snippet on your website for A/B testing, feature flags, and visitor identification to work. This integration does not replace the VWO client-side SDK.
Adding VWO as a Destination
To add a destination:
- Navigate to the Destinations page in your Ours Privacy platform.
- Click Add destination and select VWO as the destination type.
Configuration
You will need the following credentials from your VWO account:
| Field | Where to Find It |
|---|---|
| Account ID | VWO Dashboard > Settings |
| Region | Select the data center region matching your VWO account (US, EU, or India) |
Finding Your VWO Account ID
- Log into your VWO account
- Navigate to Settings to find your Account ID
How It Works
When an event is dispatched to VWO through Ours Privacy:
- The event is mapped according to your configured field mappings
- Privacy modifications (hashing, redaction, IP anonymization) are applied
- The event is sent to VWO's server-side events API (
dev.visualwebsiteoptimizer.com/events/t) - VWO associates the event with the visitor using the VWO Visitor UUID (the
_vwo_uuidcookie value)
VWO Visitor UUID
For server-side events to be correctly associated with visitors in VWO, you must pass the VWO Visitor UUID. This is the value of the _vwo_uuid cookie set by the VWO client-side snippet. It is not the _vwo_uuid_v2 cookie.
You can capture this value using the Ours Privacy Web SDK or Tag Manager and pass it as a visitor property.
Pre-registering Events in VWO
Events sent via this integration must be pre-defined in VWO's Data360 module. Unregistered events will be silently dropped by VWO.
To register events:
- Go to Data360 > Events in your VWO dashboard
- Create the events you plan to send
- Define metrics using those events for your campaigns
For more details, see VWO's guide on tracking offline conversions.
Event Mapping
The VWO destination supports the following field mappings:
| Field | Description | Required |
|---|---|---|
| Event Name | The name of the event to track in VWO (max 40 chars, alphanumeric with hyphens/underscores) | Yes |
| VWO Visitor UUID | The visitor's _vwo_uuid cookie value for visitor association | Yes |
| Session ID | A session identifier (Unix timestamp in seconds). Defaults to event time if not provided | No |
| Event Time | When the event occurred. Converted to milliseconds for VWO | No |
| URL | The page URL where the event occurred | No |
| Page Title | The title of the page where the event occurred | No |
| Referrer URL | The referring page URL | No |
| Custom Event Properties | Additional key-value pairs sent as event properties. Property names must match those defined in VWO Data360 | No |
Regional Endpoints
VWO supports multiple data center regions. Select the region matching your VWO account:
| Region | Endpoint |
|---|---|
| US (default) | dev.visualwebsiteoptimizer.com/events/t |
| EU | dev.visualwebsiteoptimizer.com/eu01/events/t |
| India | dev.visualwebsiteoptimizer.com/as01/events/t |
Get Started Today
Implement Ours Privacy effortlessly with our simple copy-and-paste installation script. Begin sending privacy-compliant events to VWO without compromising patient data security.
How is this guide?