Join us for the next Community Q&A Coffee Break on Tuesday April 23, 2024 with Eric Matisoff, Principal Evangelist, Analytics & Data Science, who will join us to discuss all the big news and announcements from Summit 2024!
It would be nice to be able to evaluate how much "damage" would be done by filtering out the bot traffic. I'm also guessing that some people may not want to exclude it from all of their traffic but would like to use the filter in specific analyses. I would like to have it be a report and/or an Omniture-endorsed segment.
Couldn't agree more. The current bot report is a great idea, but I would prefer it was done in two stages. First enabling the report would just let you identify all of the bot traffic, then we should have the option to filter out that traffic. Identifying if we want it filtered after it gets filtered is a little bit of a backwards approach. The ability to identify our bot traffic and know before hand the impact of filtering it out before we take that step would be a great addition to have.
I agree. The SiteCat 15.3 update for this was way overdue (IMHO) to manage these things myself within the interface. I might even follow on with Kevin's idea here with a predictive analytics "what if" tool for this, so that someone with less time (or less skills) can model the effects of removing the bots themselves on the fly, on a per-bot segment basis (whether it's a search bot, or a page scraping bot, or those magical in-house monitoring IT bots that tend to get applied without letting the analysts know - ugh...)
