Currently, we go to the configure portal page, export the users and organize the data how we please in an Excel document. This process, while not a large headache, would be much more efficient if it could be easily done in Aha, so all the data stays in Aha. Some of the data that would be valuable that isn't currently available includes, a list of all portal users, a count of their voting, idea creation and commenting, in a way that the data can be manipulated and turned into reports to understand who is/isn't using our Ideas Portal actively.
Thank you for your idea. As you mentioned, the idea count, comment count, and vote count for each user is currently available for export from the Users tab in portal settings. With Ideas Advanced, you can also create custom reports of contacts including their ideas, votes, and the portals they belong to.
We will consider enhancing the reporting options in the future, including the first date they logged in to the portal.
Current Challenge
At present, there is no reliable way to determine whether a user has successfully authenticated into the portal. This creates a major gap in understanding user engagement and behavior. It’s similar to sending out a survey but having no visibility into whether the recipient received the email, opened it, or started the survey which are critical touchpoints for understanding where users drop off in the funnel.
Why This Matters
Without knowing if a user has logged in, we can’t accurately measure engagement or identify where friction occurs in the experience. For example, if users authenticate but don’t search, navigate, or vote on ideas, that signals potential usability or value perception issues. But if they never authenticate in the first place, we’re misinterpreting the problem entirely.
In many modern products, tracking view and navigation activities is standard practice. These insights help assess whether users find value in the product and where they may encounter obstacles.
Specific Issues Noted
The “green checkmark” indicator for verified email addresses currently suggests successful authentication, but it loses meaning when using the import function, which automatically marks users as verified. Consequently, that indicator is of no value.
Proposed Enhancement
Implement reliable tracking that captures when a user:
Successfully authenticates into the system.
Performs basic engagement actions such as searching or navigating within the portal.
Even capturing and reporting verified email status accurately (without being overwritten by imports) would provide valuable baseline data for measuring engagement and troubleshooting access or adoption issues.
Impact
This data would enable better reporting, clearer visibility into user behavior, and more informed analysis of user engagement funnels, all that ultimately helping to improve the portal experience and identify where users encounter barriers.
Agree and support all comments to date on this idea. Last login date, number of logins / sessions ever, number of logins / sessions in last x days, time in session, and ideas viewed would be useful attributes to track.
Potentially some type of engagement algorithm could be created to define high, medium, low engagement. I
Once established, we could adjust the variables according to local preference.
Eg - Engagement-Score = (LxLM)+(V*VM)+(A*AM)+(C*CM) in P
L = number of logins
V = number of ideas viewed
A = ideas added
C = comments made
Variables: P = Period of time (number of historical days from today)
LM = Logins multiplier - eg 5
VM = Views multiplier - eg 1.5
AM = Added Ideas multiplier - eg 10
CM = Comments multiplier - eg 3
We would like to be able to report on when a user logs into a portal so that we can show whether they engage with ideas by voting and creating ideas once they are logged in. We want more detail. Aggregate votes is something, but showing which accounts or people engage over time would also help us to see who is not engaging.
reportability /visibility of portal engagement is also a means of helping our customers maintain data privacy. Being able to query inactive users for x-time could help us to identify where individuals have left an organization and may need to be removed from portal/contacts
Really looking to provide this as a graph like report to mgt and product managers across business units to see adoption of idea votes, portals and creation on a per customer basis. Also looking to break that down into which users in the customer domain are engaging.