Integrations / Analytics
Webtrends
Server-side delivery to the Webtrends Analytics Data Collection API. Posts flat WT.*/dcs* form-encoded parameters to your data source's /events.svc endpoint — page views (WT.dl=0), custom events, and commerce transactions (WT.tx_*/WT.pn_*) with the Signal anonymous_id carried as the first-party visitor ID (WT.co_f).
Datafly Signal delivers first-party events to Webtrends server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Webtrends expects.
Why route Webtrends through Datafly Signal
Your numbers stop depending on what the browser allows
Client-side analytics loses every visit where the tag is blocked or the page unloads early. Signal delivers from the server, so Webtrends receives the complete event stream.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Webtrends needs to attribute the event to the right session.
One consent decision governs every destination
Webtrends 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_checkoutpagepurchaseremove_from_cartsearchview_itemVertical presets
Retail. 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 Webtrends documentation.
Frequently asked questions
Does Datafly Signal integrate with Webtrends?
Yes. Datafly Signal delivers first-party events to Webtrends server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Webtrends expects. The integration is included in every deployment at no additional cost.
How is server-side Webtrends tracking different from the Webtrends tag?
The Webtrends 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 Webtrends from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Webtrends?
The blueprint ships with mappings for add_to_cart, begin_checkout, page, purchase, remove_from_cart, search, view_item. Any event in your schema can be mapped to Webtrends through pipeline configuration without a code change.
Do I need to keep the Webtrends tag on my site?
No. Signal delivers to Webtrends from the server, so no client-side Webtrends script is required on your site.
Other analytics integrations
Ready to move Webtrends server-side?
See how Datafly Signal delivers first-party events to Webtrends from infrastructure you control, with hashed identity and consent enforcement built in.