Feature Request

Request the ability to see how many readers (and which readers) are following an article

Customer would like to access the feedback manager section from analytics shown at the article level

Below is a suggested feedback on the Eddy AI search, Algolia search, and Feedback analytics. Problem statement: At present, the Eddy AI analytics data can only be filtered on a monthly basis, which means all search queries within a month are grouped together. While this provides a high-level overview, it lacks granularity. Without visibility into the specific date and time of each search, it becomes difficult to track trends at a more detailed level, identify specific usage patterns, or conduct effective audits. Suggested improvement: To enhance our internal tracking and auditing capabilities, I suggest adding a timestamp (date and time) to each search query record, in the Conversations table or when a specific search query is opened to view the response. This addition would provide greater visibility into when searches are being performed, allowing us to: Identify queries that were performed on a specific date Better analyse patterns in failed or repeated queries over time Strengthen audit trails for compliance or internal purposes Additionally, the same enhancement could be introduced in the Search Analytics and Feedback Analytics tables—where search queries and user feedback are currently viewed. Having a date and timestamp in those views as well would further increase clarity, traceability, and allow for more targeted data exploration.

Add homepage-level analytics to track user interactions, such as where users are clicking on the Help Center homepage. This would help the team better understand user behavior and improve content placement. While not a blocker, the customer considers it a valuable enhancement.

It would be useful to be able to compare analytics from two time periods. For example, it would be useful to be able to see my analytics from the past 30 days compared to the preceding 30 days. This would make it easier to see trends over time. For reference, Google Analytics offers a feature like this.

I think renaming the "Total Articles" metric in Doc360's analytics would make a huge difference, and here's why: When I see "Total Articles," a few questions pop into my head: -Are we talking about every article ever created, even the ones still in draft? -Does it only count articles that are live and published right now? -What about articles that were published but later archived or deleted? -Is this a count of recently updated articles, or just a raw tally of unique articles? It's just a bit unclear, right? If that metric is meant to show how many articles have been changed within a specific timeframe, calling it "Articles Updated" would be much clearer. That would be super helpful for tracking how fresh and well-maintained our content is. On the other hand, if it's meant to count the number of articles that have gone live (either for the first time or after a draft period) within the selected timeframe, then "Articles Published" is a precise and unambiguous name. That helps us easily see our content creation speed. Ultimately, making this change would: Remove any confusion: I'd know exactly what the metric represents at a glance. Make it more useful: Users could better understand what aspect of their knowledge base's growth or maintenance they're tracking, leading to smarter decisions. Align with common language: "Published" and "Updated" are terms we all understand in the world of content. I get that the current naming convention might be "Total X, Total Views, Total Reads" but a little thought into the name could bring a lot of clarity. Even if it means a second line in the UI, the benefit of having a truly clear and actionable metric would be well worth it.

Currently, when viewing analytics for an article via Documentation → Article → More Settings → Analytics, the data displayed is limited to the last 7 days by default. However, this time range is not clearly indicated within the analytics dialog box, which can lead to confusion. A customer has requested the following enhancement: Add an option to select a custom time range for viewing article analytics (e.g., last 7 days, last 30 days, custom range, etc.), or at the very least, Include a clear label or note in the dialog box indicating that the data shown is for the last 7 days. This feature would help users better interpret the data and analyze article performance over different periods.

For non contributors in a team, need to know who has read or has not read a document.

We'd like to see date and timestamp data in each question and response users submit to Ask Eddy (from the widget and from the knowledge base). It would be nice to see this in the analytics UI, but if it was only available in the export spreadsheet that would be perfectly sufficient. We also would like to see the username/email with each question response (but I'm aware that's a separate feature request).

If the link analytics limit is reached, we are not validating the updated links in the article. It would be great if we could show the updated / working links as "Not validated" instead of showing the old links present in the article with the status "broken" even after updating the links and publishing the article.