Webtrends Analytics

⚠️

Deprecated. Webtrends’ hosted collection (dc.webtrends.com) no longer resolves; only an on-premises SmartSource Data Collector can receive these requests. This integration is hidden from new installs; an integration already installed on it keeps its revision and keeps delivering. Nothing is removed.

Datafly Signal delivers events to Webtrends Analytics server-to-server using the Data Collection API — the REST interface that backs the standard dcs.gif pixel. Events are sent as form-encoded WT.* parameters straight to your data source, so reporting keeps working without a client-side tag and is immune to ad blockers and browser tracking prevention.

⚠️

Hosted collection is no longer reachable. Webtrends’ hosted collection host dc.webtrends.com no longer resolves (checked 22 September 2026), so this integration cannot deliver to Webtrends On Demand. It can only deliver to an on-premises SmartSource Data Collector that serves the Data Collection API; set dc_url to that collector. The integration is under review for deprecation.

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.

Prerequisites

Before configuring Webtrends in Signal you need:

A Webtrends Analytics account (Webtrends On Demand or a self-hosted SmartSource Data Collector install).
A data source configured for the profile you want to populate.
The Data Source ID (DCSID) for that data source.
Your collection server URL (the host that receives data).

Step 1: Find your Data Source ID (DCSID)

Sign in to Webtrends Administration.
Go to Data Sources and open the data source for your profile.
Copy the DCSID — a 30-character identifier that starts with dcs, followed by 22 alphanumeric characters, an underscore, and 4 more characters (for example dcsab12cd34ef56gh78ij90kl_1m2n).

Step 2: Confirm your collection server URL

Webtrends On Demand (https://dc.webtrends.com) no longer resolves; see the warning above.
Self-hosted SmartSource Data Collector installs use your own collector host (for example https://sdc.example.com). Ask your Webtrends administrator for the exact host if you are unsure.

The DCSID is the only credential the Data Collection API needs. It is carried in the request URL and scopes the data to your profile, so there is no separate API key or token to manage.

Configure in Signal

Configuration Fields

Field	Required	Description
`dcsid`	Yes	Your 30-character Webtrends Data Source ID.
`dc_url`	No	Base URL of your collection server (scheme + host). Defaults to `https://dc.webtrends.com`. Set this for self-hosted SmartSource Data Collector installs.

Management UI Setup

Add the integration

Go to Integrations > Add Integration > Webtrends.

Choose a variant

Select Retail (page views and the commerce funnel).

Enter your credentials

Paste your dcsid and, if you are self-hosted, your dc_url.

Save

Click Save. Signal begins forwarding events on the next page load.

API Endpoint

POST {dc_url}/v1/{dcsid}/events.svc
Content-Type: application/x-www-form-urlencoded

The request body is ampersand-delimited key=value pairs (form encoding). A successful submission returns HTTP 200 with an empty body. Both https://dc.webtrends.com (On Demand) and a self-hosted collector host are supported via dc_url.

Identity Signals

Webtrends matches activity to a visitor using a first-party visitor identifier. Signal supplies this server-side so reporting stays accurate without a browser cookie.

Signal	Parameter	Description
Visitor ID	`WT.co_f`	The Datafly `anonymous_id`, sent as the first-party visitor identifier. Stable across the session.
IP address	`dcsip`	The visitor’s IP, forwarded from the original request so geo reports resolve correctly.
User-Agent	`dcsua`	The visitor’s User-Agent, forwarded from the original request so device/browser reports resolve correctly.

Webtrends does not require hashed PII for this integration — visitor matching is done with the first-party anonymous_id (WT.co_f). No email or phone hashing is involved.

Event Mapping

Page views are sent with WT.dl=0; other events with WT.dl=1. Every event sets dcsuri and WT.ti (both required for effective collection with WT.co_f), plus dcsip, dcsua, WT.ul (locale), WT.es (page URL) and dcsdat (event time, epoch milliseconds). Only the parameters the preset maps are sent: Webtrends stores any extra form field as a custom parameter.

Retail preset

Signal event	`dcsuri` / `WT.ti`	Extra parameters
`page`	page path / page title	`WT.dl=0`
`search`	`/search` / Search	`WT.oss` (search term)
`view_item`	`/product/view` / Product Viewed	`WT.pn_ac=v`, product lists
`add_to_cart`	`/cart/add` / Add to Cart	`WT.tx_e=a`, product lists
`remove_from_cart`	`/cart/remove` / Remove from Cart	`WT.tx_e=r`, product lists
`begin_checkout`	`/checkout` / Checkout Started	product lists
`purchase`	`/checkout/complete` / Order Completed	`WT.tx_e=p`, `WT.tx_i`, `WT.tx_cur` (upper-cased), product lists

Product lists are built from items[], semicolon-delimited in item order: WT.pn_sku (item ID), WT.pn_gr (category), WT.tx_u (quantity) and WT.tx_s (line total, price times quantity).

Example: purchase

dcsuri=%2Fcheckout%2Fcomplete&WT.ti=Order+Completed&WT.dl=1
&WT.co_f=df_anon_1234&WT.tx_e=p&WT.tx_i=ORD-001&WT.tx_cur=USD
&WT.pn_sku=SKU-A%3BSKU-B&WT.pn_gr=Shoes%3BHats&WT.tx_u=2%3B1&WT.tx_s=99.98%3B30.01
&dcsip=203.0.113.50&dcsua=Mozilla%2F5.0+...&dcsdat=1749200000000&dcsverbose=false

Testing

Trigger an event

Load a tracked page or fire a datafly.track() call on your site.

Check the Signal event debugger

Open the integration in the Management UI and view the outbound request. Confirm the form body contains your WT.co_f, the correct dcsuri/WT.ti, and (for purchases) WT.tx_e=p with WT.tx_i and WT.tx_s.

Verify in Webtrends

In Webtrends Analytics, check the real-time report or run a report for the profile. Page views, events, and transactions from Signal appear alongside any existing pixel data within the profile’s processing window.

Append dcsverbose=true (or set it in the integration config temporarily) to have the collection server return detailed validation feedback in the response body — useful while confirming parameter formatting.

Troubleshooting

Problem	Solution
No data in Webtrends	Confirm the `dcsid` matches the data source for your profile and `dc_url` points at the correct collection host (On Demand vs self-hosted SmartSource Data Collector).
`404` responses	The DCSID is unknown to that collection host, or `dc_url` is wrong. Re-check both.
`400` responses	The form body is malformed — usually a parameter value that needs encoding. Inspect the request in the Signal event debugger.
Transactions not counted as revenue	Ensure the `purchase` event carries `transaction_id` and `items[]` (with price and quantity) so `WT.tx_i` and `WT.tx_s` are set.
Wrong geo / device in reports	Confirm `dcsip` and `dcsua` are being forwarded; older self-hosted collectors may read IP/User-Agent from request headers instead of the body.
Visitors all look new	Check that `WT.co_f` carries a stable `anonymous_id`; without it Webtrends cannot stitch the session.

June (deprecated)etracker