KnowledgeBase - Excluding visitor IP addresses from data collection

Excluding visitor IP addresses from data collection

« Go Back
Webtrends On Demand
Webtrends Analytics 9.2

Various regulators consider IP addresses to be personal data and subject them to the same protection.  This leads to complexities as routing of traffic (which constitute processing) is a technical requirement of using the Internet.  To help our clients, Webtrends makes available functionality to disable the storage and processing of complete IP addresses.

Does Webtrends On Demand support IP-less tracking?
Yes. Customers can easily configure Webtrends On Demand Data Collection functionality to anonymize visitors (using randomly generated identifiers).
Does Webtrends On Demand's IP-less solution extend to the Mobile SDKs? 
Yes. Webtrends On Demand's IP-less tracking is available both for the JavaScript tracking solution and within Webtrends Mobile SDKs.
Does Webtrends On Demand collect any other personal data? 
No. By default Webtrends On Demand doesn't collect any other personal data. It is our customers' responsibility to ensure that no personal data is included in the query parameters (both standard and custom) passed in the URL for data collection.

Next Steps

On Demand - Implement server-side IP anonymization

Webtrends On Demand has the ability to replace the last octet of IPV4, and the last 5 segments of IPV6 addresses with 0 by sending the custom parameter "DCS.dcsipa=1". This method will ensure that IP addresses logged by our data collection servers are masked.
Include the following meta tag on all pages containing the Webtrends tag: <meta name="DCS.dcsipa" content="1" />
Also modify the <noscript> portion of the tag: 
<div><img alt="DCSIMG" id="DCSIMG" width="1" height="1" src="[dcsid]/njs.gif?dcsuri=/nojavascript&WT.js=No&></div>

On Demand or On Premises - Replace the IP address with a hard-coded value

This method changes the IP address used, but retains the Webtrends cookie storage method for keeping visitor ID.  Customers can specify a fixed IP, such as, in Webtrends' DCSCIP parameter in the Javascript tag to ensure anonymity. The value of the DCSCIP parameter will be recorded in the client ip (c-ip) field in the web server log.

Use the same technique in the “Disable the third-party cookie” section with the variable “DCS.dcscip” and value ””.

Also modify the <noscript> portion of the tag: 
<div><img alt="DCSIMG" id="DCSIMG" width="1" height="1" src="[dcsid]/njs.gif?dcsuri=/nojavascript&WT.js=No&amp;;dcscfg=1&dcscip="/></div>

On Premises - Disable the cookies

Note: On Premises Smartsource Data Collectors use the IP address as part of the cookie value. On Demand Data Collectors do not use IP based cookie values.
For JavaScript tags earlier than V10: There is no way to disable ALL cookies in tags earlier than v10.

You may disable THIRD-PARTY cookies as follows.

Add this META tag to the page header: <meta name=”DCS.dcscfg” content=”1” />

If meta tags are not possible, custom JavaScript may be required.  For example:
Note: You may set dcscfg=4 if you want to only write first-party session cookies, and no third-party cookies at all.

For V10 JavaScript tags

Please refer to: for documentation on configuring all aspects of cookie acceptance and collection.

Using Webtrends On Demand SDKs

Obfuscate the last octet

As of version 3.0, all SDK's support dcsipa to anonymize IP adresses. When set to ‘true’ (enabled), the dcsipa parameter will be set to “1” on every event. The collection servers use this setting to mask the IP address. For IPv4, only the first three octets will be recorded, with the last octet set to 000. For IPv6, the last octet will also be set to 0.

In the plist XML, set wt_dc_mask_ip_enabled to True.

Replace the IP address with a hard-coded value

To prevent the recording of "client IP" in Webtrends data collection logs:

Do not use the "Automatic" method of sending events to Webtrends. Insert the manual methods (see SDK documentation) which allow you to attach custom parameters to them. Use the "custom parameters" feature of each SDK and pass the following fixed value name/value pair: DCSCIP (reserved "internal" IP address space)
Here is a simple Java example of creating a Webtrends event that passes the optional client IP overwrite parameter:
Hashtable customData = new Hashtable();
WebtrendsDataCollector.getInstance().onButtonClick("/events/custom/click","NameTheEvent", "click", customData);
Once these modifications are made, the visitor's IP address is no longer collected and logged, and customers no longer may see or use the IP address of their visitors within Webtrends Analytics.

More Information
Was this article helpful?

Please tell us how we can make this article more useful.

Characters Remaining: 255