Webtrends Analytics

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.

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 accounts post to https://dc.webtrends.com.
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 for the standard page-view + commerce funnel, or Default for page views and core events.

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.
User ID	`WT.vtid`	The authenticated user ID, when the visitor is identified via `datafly.identify()`.
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

Signal uses GA4-style event names and maps them to Webtrends parameters. Page views are sent with WT.dl=0; other events are sent as custom events. Commerce events add the transaction (WT.tx_*) and product (WT.pn_*) parameters.

Retail preset

Signal event	Webtrends representation
`page`	Page view (`WT.dl=0`, `dcsuri`, `WT.ti`)
`Products Searched`	Custom event with on-site search term (`WT.oss`)
`Product Viewed`	Product event (`WT.pn_sku`, `WT.pn_id`, `WT.pn_gr`)
`Product Added`	Product event with quantity (`WT.tx_u`)
`Product Removed`	Product event
`Checkout Started`	Custom event
`Order Completed`	Transaction (`WT.tx_e=p`, `WT.tx_i`, `WT.tx_s`, `WT.pn_sku`)

To customise, edit the integration’s Field Mappings in the Management UI.

Example: Purchase event

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "USD",
  product_ids: ["SKU-A", "SKU-B"],
  quantities: [2, 1]
});

Webtrends form body sent by Signal:

dcsuri=%2Fcheckout%2Fcomplete
&WT.ti=Order%20Completed
&WT.dl=1
&WT.co_f=a1b2c3d4e5f6
&WT.tx_e=p
&WT.tx_i=ORD-001
&WT.tx_s=129.99
&WT.pn_sku=SKU-A%3BSKU-B
&WT.pn_id=SKU-A%3BSKU-B
&WT.tx_u=2%3B1
&dcsip=203.0.113.50
&dcsua=Mozilla%2F5.0%20...
&dcsdat=1749200000000
&dcsverbose=false

Multiple products in WT.pn_sku and the matching units in WT.tx_u are semicolon-delimited and positionally correlated — the first SKU corresponds to the first quantity, and so on.

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 `WT.tx_e=p`, a unique `WT.tx_i`, and `WT.tx_s` (a number with no currency symbol, matching your Reporting Center currency) are all present on `Order Completed`.
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 etracker