Skip to main content

Resources analytics: unique readers and time spent

May we please request to have performance analysis in Heartbeat where we can see the number of people who utilizes our resources (each article). We want to see the overall performance and the value of the resources we are creating.

6 comments

Log in to comment and vote

Comments6

  • HeartBEat Admin

    •

    Nov 5

    •

    Merged request

    •

    4 votes

    In-App Doc Analytics

    More specific analytics around Docs would be a major upgrade. We would benefit greatly from being able to see which pieces of content are the most viewed, when they're viewed, and how long someone keeps the page open.

  • Celine ✨

    •

    Nov 5

    •

    Merged request

    •

    6 votes

    Analytics to measure value creation

    I hope you’re doing well. We are actively scaling our learning and support ecosystem and would love deeper analytics to measure actual value creation. Specifically, we’re looking to track:

    Resource adoption and usage (e.g., which specific resources are viewed, & opened/read and the count and %).

    Resource discovery → Are members finding the resource?

    Resource relevance → Are they engaging with it beyond a click?

    Resource effectiveness → Are members returning, applying, or sharing it?

    Ideal Data Signals We’d Like to Track:

    View & open rates / count per resource: How many members accessed it at least once?

    Completion or “read” indication: Did they finish or consume the full content?

    Repeat visits or saved items: Which resources are valuable enough to return to?

    % usage based on total eligible audience

    Example:

    "32 out of 80 members viewed (40%)"

    "18 of those revisited at least once (22%)"

    Drop-off behavior (if trackable): Where are users stopping?

    1. Peer-to-peer support signals (e.g., replies, help interactions, mentorship threads, message reactions). Specifically, we are looking to track measurable engagement patterns such as:

    Support replies & helpful responses: To understand how often members are solving each other’s questions

    Mentorship & knowledge-sharing threads: To identify recurring experts, emerging leaders, and common topics where the community supports itself.

    Help signals (asks & assists): To track how often members request help and receive a response within an acceptable time frame.

    Message reactions, endorsements, or “helpful” markers: To quantify sentiment, agreement, or perceived value from other members.

    Community sentiment or NPS-style feedback (e.g., quick rating system or periodic pulse check)

    • Dave Jackson

      •

      Nov 18, 2025

      Nothing against Google Analytics, but I would love a box for Fathom stats.

  • Akilah Kamaria

    •

    Jan 25

    this would be awesome to have