I'm trying to configure a profile for a client. They are a large company spread over a number of sites, with a lot of staff, most of whom have the company website as their homepage. This traffic is massivly skewing their data and I need to know how to filter out these users.

I have the IP ranges that the company uses, but I can't figure out how to impliment a filter. I'm using WT v7.5a Enterprise.

Anyone got any ideas?

Cheers, Andy

In the Administrators console, Click Options-->Hit Filter-->New Hit Filter. Under General tab, give the filter a name, click exclude, Include/Exclude activity based upon the following Active Hit Filter Parameters, select Address. Under Address tab, select (All Addresses) from the drop down, and type in an expressiong for the IP range to exclude, and save.

Then go to edit profile, advanced, hit filters, and select your newly created filter. That should do it. If you have problems creating an expression for the IP range, let me know.

Cheers Bill,

I've set that up, and it's re-processing the data as I type. I'll let you know how it goes.

Andy

Right,

It's done re-processing all the data, and it appears to have excluded a lot of the traffic from the IPs I specified, but there are still some visits showing up from users with an IP in the range I specified for exclusion.

Any ideas on why this is, or how I can construct a better IP expression.

Cheers.

Another approach would be to remove any log file entries at time of retrieval that you don't want to show up in the WebTrends reports. The benefit to doing this is that you avoid "paying" for the page views you don't want to report on. WebTrends counts page views against your license "allotment" even if you use WebTrends to filter the hits.

We use VBScript files to preprocess our logs.

Doug

Can you exlude a range of IPs, like 4.23.170.224 - 4.23.170.239"?

From the filter examples, it looks like you can only use wildcards...

Stephen

I have create a filter like this:

Filter on: VISITOR
Match Values: Equal To _ 172.*|10.*
But I still can see in the reports IPs out of this range (like 209.85.229.132) althoug these result are few, but they shouldn't be.

Would it be better to use this expression?
Equal To _ ^172.|^10.

Or witch should be the solution?

Thanks a lot,

Hi Gabriel, You can't use regular expressions with that filter, can you? I believe the screen does not have a checkbox for regex.

Instead of | enter a space and don't use ^.
Look on the screen or the help window, I believe it gives and example that you should base your entry on.

Let us know if this doesn't solve it.

Hello Chris,

Thanks a lot for your explanation. I have tried to put * instead of ^ and without spaces and I think it works. Sometimes there appear some results that don't belong to tha range but I heva found this explanation:
If an organization has employees that use laptops, and they transport those laptops between home and work,
it can appear as if the IP addresses are not being properly filtered. If the customer is tracking by cookie,
what shows up in the visitor dimension is the value of the cookie. This cookie value will often include the IP address.
If an employee surfs the site at work, then goes home with the laptop and surfs the site there as well,
the cookie value will reflect the IP address from work, but the actual traffic will be generated from the IP address at home.
If the filtering is for internal IP addresses, the external traffic will still be included in the reports, even though the cookie reflects the internal IP address.

To filter out the IP address from this report, create another filter that filters based on the cookie value and enter the IP range with wildcard as appropriate.
Apply the filter, and from that point forward traffic from these users should be filtered as expected.

Thanks again and best wishes,ç
Gabriel.

Good one.

So the only people getting through inappropriately would be people who work at the organization in question and their first visit to your site was from home, either using their company laptop or their home computer.