VWO Cloud Mode (Actions) Destination

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

• Support for Customer Data Platform (Data360). With the cloud mode enabled, you will be able to transfer all the events and attributes into your VWO account through the Data360 module.
• Support for FullStack. While the classic destination was serving only websites, the cloud mode can provide for server sources, as well.

1. From the Segment web app dashboard, navigate to Connections > Catalog.
2. Under the Destinations tab, search for "VWO Cloud Mode (Actions)", and select the destination.
3. Click Configure VWO Cloud Mode (Actions).
4. Select the source that will send data to VWO Cloud Mode (Actions), click Next to enter the name of your destination, and click Save.
5. On the Settings tab, under Other Settings, click on Account ID, enter your VWO account ID, and click Save.
6. 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.
7. Enable the destination using the toggle switch.

1. Install the VWO SmartCode on your website following VWO's guide Configuring SmartCode for Your Website
2. Create a VWO campaign on your website.
3. When a visitor lands on your website VWO generates a _vwo_uuid cookie that acts as a unique identifier for the visitor. To learn more about the VWO UUID, see VWO's article How to locate your VWO UUID.
4. Pass the value of the _vwo_uuid cookie with every call to Segment in the vwo_uuid key. Track and Page calls require the vwo_uuid in the properties object. For Identify calls, you can place vwo_uuid in the traits object.
   
   To automate this step, you can use Segment Analytics.js middleware and use the following script on your website. This script fetches the VWO UUID from the cookie and adds it to the segment payload so that you don't have to do the same manually.

1
<script>
2
  analytics.addSourceMiddleware(({ payload, next, integrations }) => {
3
    const getCookie = function (name) {
4
      const value = `; ${document.cookie}`;
5
      const parts = value.split(`; ${name}=`);
6
      if (parts.length === 2) return parts.pop().split(";").shift();
7
    };
8
    const event = payload.obj;
9
    const vwoUuid = getCookie("_vwo_uuid");
10
    switch (event.type) {
11
      case "track":
12
      case "page":
13
        payload.obj.properties.vwo_uuid = vwoUuid;
14
        break;
15
      case "identify":
16
        payload.obj.traits.vwo_uuid = vwoUuid;
17
        break;
18
    }
19
    next();
20
  });
21
</script>

All the events triggered in Segment will be available under UNREGISTERED EVENTS in the Data360 > Events section in VWO. For more information about Events in VWO Data360, see VWO's article Working with Events in VWO.

To use the VWO Cloud mode destination with the VWO FullStack suite, link your VWO FullStack environment with Segment using the environment's SDK key. After that's done, integrate your VWO account with Segment.

To link your VWO FullStack environment with Segment:

1. From your VWO dashboard, navigate to the nav bar on the left > FullStack > Projects and select the appropriate project.
2. Under the Environments section, click the Copy button corresponding to the environment that you want to link to Segment.
3. In the VWO SDK Key field in the destination settings in Segment, paste the copied SDK key from the previous step.
4. Click Save Changes.

To integrate Segment with VWO FullStack:

1. Initialize VWO FullStack SDK. Follow the steps for your server in VWO's Quick Start Guide.
2. To track visitors in VWO, provide the user IDs of the visitors, which were used to track them in the VWO FullStack campaign. Pass that same User ID as vwo_uuid with all calls to Segment. Track and Page calls require the vwo_uuid in the properties object. For Identify calls, you can place vwo_uuid in the traits object..
3. All the events triggered in Segment will be available under UNREGISTERED EVENTS section which can be accessed by navigating from the left navbar > Data360 > Events.

By adding the VWO Cloud mode destination to your Segment audiences, you can export audiences to your VWO account to target your campaigns in VWO. To achieve this, perform the following steps:

1. Navigate to Engage > Engage Settings, and click Destinations.
   • Ensure that you're in the Engage space you plan to use for VWO.
2. Click Add Destination.
3. Search for "VWO Cloud Mode (Actions)" and select the destination. Click Add Destination.
4. On the Select Source screen, you'll see your Engage space selected as the source. Click Confirm Source.
5. Select the VWO Cloud mode destination that you've created and navigate to the Settings tab. Name your destination and enter your VWO Account ID. Toggle Enable Destination on and click Save Changes.
   • You'll find your VWO account ID at the top of the VWO dashboard.
6. Navigate to the Mappings tab and click New Mapping. Under PRE-BUILT MAPPINGS, select Sync Audience, then click Save.
7. The STATUS of the mapping displays as disabled by default. Enable the mapping using the toggle.
8. Navigate to Engage > Audiences. Choose an existing Engage audience or create a new one to export to VWO.
9. Click Add Destination and select the VWO Cloud Mode destination you created. From the Connection Settings screen, toggle the Send Track option on. Be sure you don't change the Audience Entered/Audience Exited event names. Click Save.

Visit Using Data From Segment for more on how to configure audiences in VWO.

VWO Supports the following calls, as specified in the Segment Spec.

The Track call records any actions your visitors perform, along with any properties that describe the action. Each action is known as an event.

The destination forwards these events to VWO Data360 where they can be seen under the UNREGISTERED EVENTS section in Data360 > Events in VWO. These events can be registered and used as Metrics in VWO.

Sample payload for Track Call to the destination

1
analytics.track("Segment Test Event", {
2
	"vwo_uuid": "<VWO UUID or User ID>",
3
	"property1": "value1"
4
});

Corresponding JavaScript event that would generate the above payload

1
{
2
  "type": "track",
3
  "event": "<Event Name>",
4
  "properties": {
5
    "vwo_uuid": "<VWO UUID or User ID>",
6
    "property1": "value1"
7
  }
8
}

The Identify call associates a visitor with their actions and captures their traits.

The destination forwards these traits to VWO Data360 where they can be seen under the UNREGISTERED ATTRIBUTES section in the Data360 > Attributes in VWO. These attributes can be registered and used to create segments in VWO. For more information about Attributes in VWO Data360, see Working with Attributes in VWO.

Sample payload for Identify call to the destination

1
{
2
  "type": "identify",
3
  "traits": {
4
    "vwo_uuid": "<VWO UUID or User ID>",
5
    "trait1": "value1"
6
  }
7
}

Corresponding JavaScript event that would generate the above payload

1
analytics.identify({
2
	"vwo_uuid": "<VWO UUID or User ID>",
3
	"trait1": "value1"
4
});

The Page call records when a visitor arrives at a page of your website, along with any optional properties about the page. When received, the destination triggers VWO's Page Visit event.

Sample payload for Page Call to the destination

1
{
2
  "type": "page",
3
  "properties": {
4
    "vwo_uuid": "<VWO UUID or User ID>"
5
  }
6
}
7

Corresponding JavaScript event that would generate the above payload

1
analytics.page({
2
	"vwo_uuid": "<VWO UUID or UserID>",
3
});

VWO Cloud Mode (Actions) has the following presets

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

• Identify User
• Page Visit
• Track Event
• Sync Audience

Maps Segment's visitor traits to the visitor attributes in VWO

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

Sends Segment's page event to VWO

Page Visit is a Cloud action. The default Trigger is type = "page"

Sends Segment's track event to VWO

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

Syncs Segment audiences to VWO

Sync Audience is a Cloud action. The default Trigger is event = "Audience Entered" or event = "Audience Exited"