Exclude IP addresses/ranges

Avatar

Avatar

kate_rosser

Avatar

kate_rosser

kate_rosser

17-02-2010

Currently you can only exclude 5 IP addresses/ranges in Admin, to exclude more you have to pay for a VISTA rule to exclude this traffic from specified IPs.

We have more than 5 IP address/ranges we need to exclude from all our Report Suites as we have Webmasters and Developers all over Europe.  If it is possible to exclude these via Admin then it wouldn’t require much resource to increase this to as many as you need. We shouldn’t have to pay for a VISTA rule to get our data correct - this should be as standard.

8 Comments (8 New)
8 Comments

Avatar

Avatar

hans52830

Avatar

hans52830

hans52830

08-03-2010

This is crucial, and seems obvious.  5 ip ranges, without any ability to do anything more complex than an asterisk, is pretty ridiculous.

Avatar

Avatar

lindat15

Avatar

lindat15

lindat15

29-03-2010

Agree

Avatar

Avatar

guru84944

Avatar

guru84944

guru84944

13-06-2010

If you could atleast allow to exclude IP using regular expressions that would be great. Most of the competitors have such features.

Avatar

Avatar

apostrophalypse

Avatar

apostrophalypse

apostrophalypse

15-06-2010

And it'd be nice to select which report suites the IP-exclusion should apply to. We have report suites for our release candidate site versions, and development versions; we want to include our internal traffic for those, but exclude it from Live/production reports.

Avatar

Avatar

mitchell_teixei

Avatar

mitchell_teixei

mitchell_teixei

05-03-2011

Regular Expressions support in SiteCatalyst is needed in many areas!  Please!

Avatar

Avatar

cisco_webteam

Avatar

cisco_webteam

cisco_webteam

05-03-2011

I remember it was a standard feature in HBX to exclude IP by range.  In SiteCatalyst, you have to pay for it.

Avatar

Avatar

dbnelson75

Avatar

dbnelson75

dbnelson75

27-07-2012

It is nice that you can now add 50 IP addresses but the core of this issue is that you can not exclude IP address ranges. Adding this ability and being able to apply these additions to multiple or all report suites is what we really need.

Avatar

Avatar

alysonmurphy

Avatar

alysonmurphy

alysonmurphy

04-12-2012

We really need the ranges so I can exclude 1.1.1.1-15. Right now I have to blow 15 of the slots to take care of that and it is painfully tedious.