Home > FAQs > API Integration Related FAQs > How to Display User Stats in Discussions (Comments & Reactions Count and Points)

How to Display User Stats in Discussions (Comments & Reactions Count and Points)

You can easily display discussion statistics including total comments & reactions count and points both to individual users (for their own profile insights) and publicly to other users (to highlight top contributors or active community members). The visual design and presentation of these statistics is completely flexible and up to your front-end team to implement. In this article, you'll learn useful ways to display these discussion statistics through our APIs and SDKs.


📖 Q: Can we show how many comments or reactions users have in discussions? Is it possible to display this both to users themselves and publicly to others?

Absolutely! Many clients want to gamify their discussion sections by showing user engagement statistics - think of it as a place where, apart from commenting and reacting to others' posts, users can see their own and other users' activity stats (comments made, reactions received) and thus have a chance to publicly showcase their participation achievements to the community.

But it's not just about that - some clients also want to display these stats on profile pages, user cards, or alongside discussion badges to give a complete picture of users' activity and achievements. This creates a more engaging environment where active contributors are recognized for their discussions participation.


⚙️ How It Works

Our platform provides pre-calculated statistics covering all-time discussion activity through a simple API call, so you don't have to worry about counting everything manually through multiple calls. If you want users to view their own discussion stats and also display them publicly to others - we have API endpoints for both scenarios:

Or if you're using our SDKs:

  • You can use this method sdk.profile.getOwn().getStats()

SDK Documentation: https://docs.fansunitedmedia.com/docs/profile-operations#/get-profile-stats


📈 What You Get

When you make this API call, you'll receive the key discussion engagement metrics in one clean response. Here's what the discussions part of the response looks like:

 "discussions": {
     "totalPoints": 73268,
     "post_points": 71000,
     "posts_made": 39,
     "reaction_points": 2268,
     "reaction_count": 13
   }

What each field means:

  • totalPoints: All points this user has earned from discussions
  • post_points: Points earned specifically from creating posts
  • posts_made: How many posts/comments the user has made
  • reaction_points: Points earned when others react to their content
  • reaction_count: Total reactions (likes, loves, etc.) they've received

Things to Keep in Mind

  • These are totals across all discussions: The stats you get represent the user's activity across your entire platform. If you want to show separate statistics for individual discussion threads, you'd need to build some additional logic using other endpoints.

  • Want more detailed breakdowns? If you want to create and display even more detailed all-time discussion stats breakdowns - like total likes received, dislikes received, love reactions, etc. - you can access individual posts or discussion threads and see specific reaction types through our other discussion endpoints. However, this approach requires more processing since you'd need to calculate stats from individual posts each time. For most use cases, the pre-calculated totals in profile stats work perfectly and perform much better.

💡 Our Recommendation

Start with the Profile Statistics API endpoint - it's fast, reliable, and gives you everything most clients need to create engaging discussion statistics displays. Whether you want to show a simple "Posts: 39, Reactions Count: 59" summary or create user achievement showcases, this endpoint provides the foundation you need.

📖 For more detailed API documentation and additional endpoints, please refer to our complete API reference documentation.

 

Further Reading