Read receipts and analytics

Track who has read an Info Hub announcement and review read counts, read rate, and audience breakdowns on cards and the Analytics tab.

Read receipts are Fuxam’s automatic record of when a user opens a published Info Hub announcement. They power unread badges in the sidebar, view counts on cards for editors, and the detailed Analytics tab on each post. For university administrators, read receipts close the loop on official communication: instead of assuming an email was seen, you can compare how many people in the targeted audience actually opened the post — and follow up when read rates stay low on time-sensitive or policy-bearing content.

Why it matters

Institutional communications often carry compliance or safety weight: examination rules, data-protection updates, fee deadlines, or campus access changes. “We published it” is weak evidence if half the cohort never opened it. Read receipts give editors aggregate accountability without manual surveys, and give readers a personal unread state so they can catch up on what they missed.

Analytics go further for users who can create announcements: read rate against total audience, timing heatmaps, and a searchable Who viewed table support operational follow-up — for example, nudging programme administrators when a cohort-specific notice stalls below expected opens.

How it fits

Read tracking begins at Publish and applies only to Published posts in a user’s audience. It connects to:

Key concepts

How read receipts work

A read receipt is created when a user opens a published announcement:

• Opening the announcement detail page marks the post as read automatically.
• Expanding the pinned banner on Home also marks the pinned post as read.

Read state is per user. It does not mark the announcement as read for other users.

Draft and Archived posts do not generate audience read receipts in the same way as live published posts — focus analytics on Published content in active circulation.

Read and unread indicators

Every user manages their own unread state. Editors see the same unread behaviour as readers for posts in their audience, plus additional analytics described below.

View counts on cards

On the Info Hub main feed, users who can create announcements see a views count in each card footer (eye icon). This reflects the number of read receipts recorded for that announcement — how many times it has been opened, not necessarily unique users.

Use card-level views for quick comparison across posts in the feed. Open the Analytics tab on the detail page for unique readers and read rate.

Analytics tab (editors)

On the announcement detail page, users who can create announcements see an Analytics tab with:

• Total reads and unique readers
• Read rate against total audience size
• Reads over time heatmap
• Peak reading hours chart
• Read vs not read breakdown for the audience
• Who viewed table — searchable list of users who have read the post, with read timestamps

Metrics are based on read receipts for the current announcement version. If no one has opened the post yet, the analytics section shows empty states.

Audience vs reads

Total audience (from visibility rules) is shown alongside read metrics so you can compare how many users could see the post versus how many have opened it.

A low read rate on a Targeted Audience cohort post may indicate wrong targeting, poor timing, or a title that did not compel opens — not necessarily a platform failure. Cross-check audience counts on the detail sidebar before escalating.

Best practices

• Review analytics after high-priority publishes — especially Urgent or notified posts — while the deadline is still actionable.
• Use read rate, not views alone, when reporting to leadership. Views can include repeat opens; read rate is normalized against audience size.
• Export or note Who viewed when you need audit evidence that specific roles saw a policy update (search within the table on the Analytics tab).
• Give posts 24–48 hours before judging read rate on non-emergency content — not every user logs in daily.
• Combine with pinning for critical messages: banner expands count as reads and improve visibility.

Common pitfalls

FAQ

Related pages