Exclude IP addresses/ranges | Community
Skip to main content
kate_rosser
kate_rosser
Level 2
February 17, 2010
Delivered

Exclude IP addresses/ranges

  • February 17, 2010
  • 8 replies
  • 10280 views

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 replies

    hans52830
    hans52830
    March 8, 2010

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

    lindat15
    lindat15
    Level 2
    March 29, 2010

    Agree

    guru84944
    guru84944
    June 14, 2010

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

    apostrophalypse
    apostrophalypse
    June 15, 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.

    mitchell_teixei
    mitchell_teixei
    Level 3
    March 5, 2011

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

    cisco_webteam
    cisco_webteam
    Level 3
    March 6, 2011

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

    dbnelson75
    dbnelson75
    Level 2
    July 27, 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.

    alysonmurphy
    alysonmurphy
    Level 3
    December 4, 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.

    Terms & ConditionsAccessibility statement

    Loading footer...