Integrations / Personalisation
VWO
Server-side custom-event delivery to VWO Data360 (/events/t). Attributes events to visitors by their VWO UUID (_vwo_uuid cookie collected by Datafly.js), carries page context and arbitrary event properties, and respects marketing consent. Events arrive as Data360 custom events that you turn into Metrics for experimentation and personalisation reports.
Datafly Signal delivers first-party events to VWO server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload VWO expects.
Why route VWO through Datafly Signal
Profiles update from the server, not the browser
Events reach VWO even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
One consent decision governs every destination
VWO is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartbegin_checkoutcontent_viewedgenerate_leadpagepurchasesearchsign_upview_itemVertical presets
Default. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the VWO documentation.
Frequently asked questions
Does Datafly Signal integrate with VWO?
Yes. Datafly Signal delivers first-party events to VWO server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload VWO expects. The integration is included in every deployment at no additional cost.
How is server-side VWO tracking different from the VWO tag?
The VWO tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to VWO from your server, so delivery does not depend on browser conditions.
Which events can Signal send to VWO?
The blueprint ships with mappings for add_to_cart, begin_checkout, content_viewed, generate_lead, page, purchase, search, sign_up, and more. Any event in your schema can be mapped to VWO through pipeline configuration without a code change.
Do I need to keep the VWO tag on my site?
No. Signal delivers to VWO from the server, so no client-side VWO script is required on your site.
Other personalisation integrations
Ready to move VWO server-side?
See how Datafly Signal delivers first-party events to VWO from infrastructure you control, with hashed identity and consent enforcement built in.