Allow unlimited filtered/blocked IP addresses

[#1]

The current filter limit of 5 IP addresses in Site Catalyst simply isn't enough. Our stats are constantly skewed and we're paying for the additional server calls.

It seems bizarre that we have to spend so much to get more blocks. Either way we're paying for something we shouldn't be. Are Omniture all about the money and not our needs?

Every other analytics package seems to offer unlimited blocks, why can't Omniture do the same?!?!?!?!?!

[#2]

Possible solution: Couldn't the ability to block IP addresses be added to the Processing Rules interface somehow?

[#3]

Quick response:

I'm using Processing Rules to segment traffic, but unfortunately they can't be used to block traffic due to a major flaw in their abilities.

Could we also use the new Bot Filtering to exclude sets of IP addresses? I haven't tried this yet, but it seems like a good option.

- Eric

[#4]

We have increased the limit of filterable/blockable IP addresses to 50. I recognize that this isn't truly "unlimited" but hopefully it gives you enough room to exclude all of your IP addresses and ranges. Please let us know via this thread if 50 isn't enough in your particular case.

[#5]

If you allowed for regex matching instead of a single * wildcard, 50 might be enough.  But usually there are a list of ranges that need to be exluded like 1.2.3.[1-9] and currently I have to either burn 9 slots or else exclude 1.2.3.* and filter out more than I want.  

[#6]

I agree with _josh. 50 could be enough if the input method was more flexible. The method for doing it in the DBVISTA is great too. Can this be replicated in the UI?