Traffic filtering/labeling.

By this we mean edge traffic filters based on IP, UA, ISP, etc. that will take subsequent actions when the initial redirect/tracking occurs:

* Mark as filtered (so it can be filtered out of reporting by default) but save -- will count against user quota

* Ignore -- will process as usual but will drop the events from the edge, not sending them to the database, not counting against user quota

* Block -- will serve a static block page with generic message, no data logged, no quota usage

* Redirect -- will bounce user to specific URL, no data logged, no quota usage