Skip to content

Commit 76364bb

Browse files
prathamesh-88markzegarelli
andauthored
Documentation for VWO Web Destination (#4187)
* Documentation PR for VWO Web Destinaton * Add ID * Add metadata --------- Co-authored-by: markzegarelli <[email protected]>
1 parent 3a99490 commit 76364bb

File tree

2 files changed

+175
-0
lines changed

2 files changed

+175
-0
lines changed

src/_data/catalog/destinations_private.yml

Lines changed: 137 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -352,6 +352,143 @@ items:
352352
dynamic: false
353353
allowNull: false
354354
presets: []
355+
- id: 637c192eba61b944e08ee158
356+
display_name: VWO Web Mode (Actions)
357+
name: VWO Web Mode (Actions)
358+
slug: actions-vwo-web
359+
previous_names:
360+
- VWO Web Mode (Actions)
361+
website: https://vwo.com
362+
status: PRIVATE_BETA
363+
logo:
364+
url: https://cdn.filepicker.io/api/file/o9X4IJO1RDegnGVmfje0
365+
mark:
366+
url: https://cdn.filepicker.io/api/file/L6U6f3KrRoScOQbUDMKj
367+
methods:
368+
track: true
369+
pageview: true
370+
identify: true
371+
group: true
372+
alias: true
373+
platforms:
374+
browser: true
375+
mobile: false
376+
server: false
377+
warehouse: false
378+
components: []
379+
browserUnbundlingSupported: false
380+
browserUnbundlingPublic: false
381+
replay: false
382+
settings:
383+
- name: libraryTolerance
384+
type: number
385+
defaultValue: 2500
386+
description: >-
387+
The maximum amount of time (in milliseconds) to wait for VWO’s full
388+
library to be downloaded before simply displaying your original page.
389+
required: true
390+
label: Library Tolerance
391+
- name: settingsTolerance
392+
type: number
393+
defaultValue: 2000
394+
description: >-
395+
The maximum amount of time (in milliseconds) to wait for test settings
396+
before VWO will simply display your original page.
397+
required: true
398+
label: Settings Tolerance
399+
- name: useExistingJquery
400+
type: boolean
401+
defaultValue: false
402+
description: >-
403+
If your page already includes JQuery, you can set this to “true”.
404+
Otherwise, VWO will include JQuery onto the page for you. VWO needs
405+
JQuery on the page to function correctly.
406+
required: true
407+
label: Use Existing JQuery
408+
- name: vwoAccountId
409+
type: number
410+
defaultValue: 0
411+
description: Your VWO account ID, used for fetching your VWO async smart code.
412+
required: true
413+
label: VWO Account ID
414+
actions:
415+
- id: 6uTbf9uHvZBJ3YnMmFHWtZ
416+
name: Track Event
417+
slug: trackEvent
418+
description: Forwards track events to VWO Data360
419+
platform: WEB
420+
hidden: false
421+
defaultTrigger: type = "track"
422+
fields:
423+
- id: aqLRikaffjfa3QFcEkPAfF
424+
sortOrder: 0
425+
fieldKey: eventName
426+
label: Name
427+
type: STRING
428+
description: The name of the event.
429+
placeholder: ''
430+
defaultValue:
431+
'@path': $.event
432+
required: true
433+
multiple: false
434+
choices: null
435+
dynamic: false
436+
allowNull: false
437+
- id: ivqt15sfJcDBKXYWs754XT
438+
sortOrder: 1
439+
fieldKey: properties
440+
label: Properties
441+
type: OBJECT
442+
description: >-
443+
A JSON object containing additional properties that will be
444+
associated with the event.
445+
placeholder: ''
446+
defaultValue:
447+
'@path': $.properties
448+
required: false
449+
multiple: false
450+
choices: null
451+
dynamic: false
452+
allowNull: false
453+
- id: tR1J9N9e3vk4XtqGjUfTSm
454+
name: Identify User
455+
slug: identifyUser
456+
description: Forwards user traits to VWO Data360 attributes
457+
platform: WEB
458+
hidden: false
459+
defaultTrigger: type = "identify"
460+
fields:
461+
- id: vviFo14bLhdFZcUucddRMV
462+
sortOrder: 0
463+
fieldKey: attributes
464+
label: Attributes
465+
type: OBJECT
466+
description: >-
467+
A JSON object containing additional attributes that will be
468+
associated with the user.
469+
placeholder: ''
470+
defaultValue:
471+
'@path': $.traits
472+
required: true
473+
multiple: false
474+
choices: null
475+
dynamic: false
476+
allowNull: false
477+
presets:
478+
- actionId: 6uTbf9uHvZBJ3YnMmFHWtZ
479+
name: Track Event
480+
fields:
481+
eventName:
482+
'@path': $.event
483+
properties:
484+
'@path': $.properties
485+
trigger: type = "track"
486+
- actionId: tR1J9N9e3vk4XtqGjUfTSm
487+
name: Identify User
488+
fields:
489+
attributes:
490+
'@path': $.traits
491+
trigger: type = "identify"
355492
- id: 63bedc136a8484a53739e013
356493
display_name: VWO Cloud Mode (Actions)
357494
name: VWO Cloud Mode (Actions)
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
title: VWO Web Mode (Actions) Destination
3+
hide-boilerplate: true
4+
hide-dossier: false
5+
id: 637c192eba61b944e08ee158
6+
private: true
7+
---
8+
9+
{% include content/plan-grid.md name="actions" %}
10+
11+
[VWO](https://vwo.com/){:target="_blank"} 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.
12+
13+
> info ""
14+
> The events and attributes that are transferred from Segment to your VWO account will appear under [Unregistered Events](https://help.vwo.com/hc/en-us/articles/8676443712537-Working-with-Events-in-VWO#:~:text=UNREGISTERED%20EVENTS%3A%20These%20are%20the,UNREGISTERED%20EVENTS.){:target="_blank"} and [Unregistered Attributes](https://help.vwo.com/hc/en-us/articles/8681465703705-Working-with-Attributes-in-VWO#:~:text=UNREGISTERED%20ATTRIBUTES%3A%20These%20are%20the,UNREGISTERED%20ATTRIBUTES.){:target="_blank"} sections, respectively. You need to save these events and attributes to VWO for further use.
15+
16+
## Benefits of VWO Web Mode(Actions) vs VWO Classic
17+
18+
VWO Web Mode (Actions) provides the following benefits over the classic VWO destination:
19+
20+
- **Support for event architecture (Data360)**. With the Web mode destination enabled, you will be able to transfer all the events and attributes into your VWO account through the [Data360 module](https://help.vwo.com/hc/en-us/articles/8679651827737-About-VWO-Data360). You can use these events and attributes to [create segments](https://help.vwo.com/hc/en-us/articles/360020418454-Using-Segmentation-in-VWO) and [metrics](https://help.vwo.com/hc/en-us/articles/8675547113625) in your VWO campaigns.
21+
22+
## Getting started
23+
24+
1. From the Segment web app dashboard, navigate to Connections > Catalog.
25+
2. Under the Destinations tab, search for “VWO Web Mode (Actions)”, and select the destination.
26+
3. Click Configure VWO Web Mode (Actions).
27+
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.
28+
5. On the Basic Settings page that appears, configure the following details in the respective fields:
29+
- Name of the destination
30+
- Your VWO Account ID
31+
- Settings Tolerance
32+
- Library Tolerance
33+
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.
34+
7. To customize the mapping of actions, follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings). Mappings in Segment allow you to control the events and attributes that are sent to VWO.
35+
8. Finally, enable the destination using the Enable Destination toggle switch and click Save Changes.
36+
37+
38+
{% include components/actions-fields.html %}

0 commit comments

Comments
 (0)