---
title: Read receipts and analytics
description: >-
  Track who has read an Info Hub announcement and review read counts, read rate,
  and audience breakdowns on cards and the Analytics tab.
sidebar:
  order: 10
---

**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](/docs/fuxam-web/base/info-hub/target-your-audience) actually opened the post — and follow up when read rates stay low on time-sensitive or policy-bearing content.

:::info
**Editors** who can create announcements see the **Analytics** tab and card view counts. **Readers** only see their own unread state — not who else has read a post.
:::

## 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.

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

| Feature | Connection |
|---------|------------|
| [Audience targeting](/docs/fuxam-web/base/info-hub/target-your-audience) | **Total audience** size is the denominator for read rate |
| [Pinning](/docs/fuxam-web/base/info-hub/pin-an-announcement) | Expanding the Home pinned banner counts as a read |
| [Priority and notifications](/docs/fuxam-web/base/info-hub/set-priority-and-tags) | Notifications drive opens; analytics show whether they did |
| [View an announcement](/docs/fuxam-web/base/info-hub/view-an-announcement) | Detail page open is the primary read event |

:::note
Read receipts reflect opens, not time spent reading or comprehension. A user who opens and closes quickly still counts as having read the post for badge and analytics purposes.
:::

## Key concepts

| Term | Meaning |
|------|---------|
| **Read receipt** | Per-user record created when that user opens a published announcement. |
| **Unread** | The user has not yet opened the post; shown as a badge on cards and in the sidebar. |
| **Views count** | On cards for editors: number of read receipts recorded (opens, not necessarily unique users). |
| **Read rate** | Percentage of the targeted audience that has opened the post — shown on the Analytics tab. |
| **Unique readers** | Distinct users with a read receipt — may differ from total reads if the metric counts repeat opens differently. |

## 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

| Location | What you see |
|----------|----------------|
| Info Hub cards | **Unread** badge on posts you have not opened yet |
| Sidebar **Info Hub** item | Badge count of your unread announcements |
| After reading | **Unread** badge disappears; sidebar count decreases |

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.

:::tip
Check **Peak reading hours** before sending follow-up reminders — if opens cluster right after publish, a second nudge the next morning may reach users who have not yet logged in.
:::

## 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.

| Metric | Question it answers |
|--------|---------------------|
| Total audience | How many users match [visibility rules](/docs/fuxam-web/base/info-hub/target-your-audience)? |
| Unique readers | How many of those users opened the post? |
| Read rate | What percentage of the audience has opened it? |
| Read vs not read | Who still has not 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](/docs/fuxam-web/base/info-hub/set-priority-and-tags) 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](/docs/fuxam-web/base/info-hub/pin-an-announcement)** for critical messages: banner expands count as reads and improve visibility.

## Common pitfalls

| Pitfall | Misinterpretation | Reality |
|---------|-------------------|---------|
| Equating views with unique users | "500 views means 500 people" | Card views count opens; use **unique readers** on Analytics |
| Expecting reads on **Draft** | Analytics empty for unpublished work | Only **Published** audience opens count |
| Ignoring audience size | Low reads look like failure | A post to five users with four opens is 80% read rate |
| Editing after publish | Metrics may reflect current version | Analytics note: based on current announcement version |
| Assuming mobile opens differ | Separate mobile metric | Opens on Fuxam Web detail and pinned banner follow same receipt rules documented here |

## FAQ

**Can readers see who else has read a post?**

No. Read lists and aggregate analytics are for editors who can create announcements. Readers only see their own unread state.

**If I edit a published post, do read receipts reset?**

Metrics are based on read receipts for the current announcement version. Treat major content changes as a reason to re-check read rate or consider a follow-up post.

**Does opening from search count as a read?**

Opening the published detail page marks the post as read. The path to the detail page — feed, search, or direct link — does not change receipt behaviour.

**Do notifications guarantee reads?**

Notifications increase visibility, but delivery depends on user preferences and opens still require the user to view the post. See [Set priority and tags](/docs/fuxam-web/base/info-hub/set-priority-and-tags).

## Related pages

**[View an announcement](/docs/fuxam-web/base/info-hub/view-an-announcement)**

Detail page with Analytics tab for editors.

**[Target your audience](/docs/fuxam-web/base/info-hub/target-your-audience)**

Audience size drives read rate calculations.

**[Pin an announcement](/docs/fuxam-web/base/info-hub/pin-an-announcement)**

Banner expands register as reads on Home.

**[Set priority and tags](/docs/fuxam-web/base/info-hub/set-priority-and-tags)**

Priority and notifications influence open timing.

**[Info Hub overview](/docs/fuxam-web/base/info-hub)**

Unread badges and feed behaviour in context.
