Integrations / Marketing Automation

Vero

Server-side behavioural event tracking via the Vero v2 Track REST API (events/track). Maps Signal events to Vero event_name with the user's id and raw email as identity, custom properties under data, and source/timestamp under extras. Vero does not accept anonymous events.

Datafly Signal delivers first-party events to Vero server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Vero expects.

Why route Vero through Datafly Signal

Profiles update from the server, not the browser

Events reach Vero 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

Vero 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_checkoutpagepurchasesearchsign_upview_item

Vertical 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 Vero documentation.

Frequently asked questions

Does Datafly Signal integrate with Vero?

Yes. Datafly Signal delivers first-party events to Vero server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Vero expects. The integration is included in every deployment at no additional cost.

How is server-side Vero tracking different from the Vero tag?

The Vero 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 Vero from your server, so delivery does not depend on browser conditions.

Which events can Signal send to Vero?

The blueprint ships with mappings for add_to_cart, begin_checkout, page, purchase, search, sign_up, view_item. Any event in your schema can be mapped to Vero through pipeline configuration without a code change.

Do I need to keep the Vero tag on my site?

No. Signal delivers to Vero from the server, so no client-side Vero script is required on your site.

Ready to move Vero server-side?

See how Datafly Signal delivers first-party events to Vero from infrastructure you control, with hashed identity and consent enforcement built in.