@jamiemccardle  It is expected to get different results in the search results compared to what you see in the search-suggestions. The intent of these two searches are different and so is the logic behind the mechanism of these searches. I suspect it comes down to the special characters and how the community posts are indexed. If I search for just awrrpt I get the expected result in both the main search results and in the search suggestions. Also, if I search for "awrrpt.sql"  with the double-quotes included, I get the same results in the main search and in search suggestions since it gets treated as an exact match. However, the moment I search for just awrrpt.sql with ".SQL" at the end, the dot gets treated as a special character here and special characters DO NOT get indexed by the community search. The moment you search for awrrpt.sql, the term gets indexed as "awrrpt" OR "sql". Even if the search suggestion shows you the post you expect to see in the result, you can see that it highlights "SQL", and not "awrrpt". Do let me know if this helps and if you have any questions. ... View more

@STARFLEET  Our engineers have already come up with a way to hide these cookies. The visibility of these cookies (__atuvc and __atuvs) was treated as a bug and the fix is available in v20.5 of the community so these cookies will not be visible in the browser's dev tools after v20.5 upgrade. ... View more

Hi @Wendy_S    Sorry about the delay here. I would highly recommend filing a Support ticket. Like I mentioned earlier, sometimes, some bots do slip by the filter if they were developed in a way to not get detected as a bot but rather get detected as actual human users. The engineers used to make a change in the dictionary of the bot filter and add the information of such bots there so the filter can detect that specific bot in the future. But it is no longer the process now.   This was discussed with Engineering and as the process of manually adding the details of the bot is not really a solution but rather a temporary relief, the team no longer manually updates it. Instead, when you create a ticket with Support and let us know about such bots that have bypassed the filter, we record the data for case studies so that we can come up with a permanent solution to this which will require some extensive development work. I hope this helps. Update ( @Wendy_S 😞 I was mistaken. I discussed this with Engineering again. We never actually made changes to the bot traffic in LSI by updating the DB to detect bots. Any metric that has been fetched by LSI once, will stay there for good. If you do come across suspicious traffic then you can file a support ticket and let us know about it. The Analytics team can provide you with details of where the bot traffic generated from (user agent details and IP address etc.) and you can block them from the community so no future traffic gets accepted from there.   Best, Rahul ... View more

This is possibly the result of a bot. LSI has bot filters that keep the metrics bot-free as much as possible but sometimes it fails and certain bots/crawlers cloaked as actual user accounts lead to search results like this. You may file a ticket with Khoros Support and get some more details on the bots, provided the details are exposed (such as their IP Address and geo-location etc.) but usually they aren't exposed. I wouldn't say this is an issue, but rather a rare case where bot/crawler metrics get mistaken as user metrics (because they are represented that way) and LSI cannot differentiate this. The bot Database does get updated so that LSI doesn't count metrics from these bots in the future but if something new comes up that's not already recorded in our Database, then it will show up in the metrics unless it gets detected and then recorded in our Database. Hope this helps. ... View more