Integrations / Marketing Automation
WebEngage
Server-side event tracking via the WebEngage REST API (/v1/accounts/{license_code}/events). Maps Signal GA4-style events to WebEngage custom events with userId/anonymousId identity resolution, ISO 8601 eventTime, and a flat eventData attribute object. Consent and profile attributes (email/phone/opt-ins) are noted for the companion /users (Identified) path.
Datafly Signal delivers first-party events to WebEngage server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload WebEngage expects.
Why route WebEngage through Datafly Signal
Profiles update from the server, not the browser
Events reach WebEngage 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
WebEngage 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_checkoutloginpagepurchaserefundremove_from_cartsearchsign_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 WebEngage documentation.
Frequently asked questions
Does Datafly Signal integrate with WebEngage?
Yes. Datafly Signal delivers first-party events to WebEngage server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload WebEngage expects. The integration is included in every deployment at no additional cost.
How is server-side WebEngage tracking different from the WebEngage tag?
The WebEngage 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 WebEngage from your server, so delivery does not depend on browser conditions.
Which events can Signal send to WebEngage?
The blueprint ships with mappings for add_to_cart, begin_checkout, login, page, purchase, refund, remove_from_cart, search, and more. Any event in your schema can be mapped to WebEngage through pipeline configuration without a code change.
Do I need to keep the WebEngage tag on my site?
No. Signal delivers to WebEngage from the server, so no client-side WebEngage script is required on your site.
Other marketing automation integrations
Ready to move WebEngage server-side?
See how Datafly Signal delivers first-party events to WebEngage from infrastructure you control, with hashed identity and consent enforcement built in.