Employee Newsletter Software That Knows Its Audience

Per recipient: whether the newsletter was sent to them, whether it was opened, and whether a tracked link was clicked, each with a timestamp. Per send: open rate, click rate, and poll results, with a recipient list you can filter. External addresses appear as a separate list without engagement data, since tracking depends on the intranet.

Treat it as a ceiling rather than a headcount, and it will serve you well. An open is registered when the tracking image loads, and corporate mail scanners load images too — so opens read high across every email platform, not just this one. Axero also counts a recipient reading the newsletter in their in-app archive as an open, which is usually what you want but does mean the number blends two behaviors. Where it's genuinely useful is comparison: this month's announcement against last month's, or one audience against another, measured the same way both times.

Button blocks and linked image blocks. Links typed inside a text block, and the "read more" links on embedded content cards, are delivered normally but don't register as tracked clicks. The practical implication for comms: if you want to measure whether people acted on an update, make the action a button. Click reporting tells you which recipients clicked, at the send level — it isn't a per-link breakdown.

Yes — embed a poll and recipients vote with a single click from the email, then see live results. Voting requires an intranet sign-in, so responses are attributable and each person votes once; polls can also run in anonymous mode, where the vote is recorded without being tied back to the voter. Results are visible in the send detail and export to CSV. External email recipients can't vote, since voting depends on the intranet login.

A short reminder to the people who haven't opened yet, pointing them at the newsletter in their archive — not a second copy of the full email. Set how long to wait (anything from a day to a year, commonly two or three days) and the subject prefix, which defaults to "Reminder:". It fires once per newsletter by design; this isn't a drip sequence, and there's no way to nag someone repeatedly.

Yes, once the option is enabled for your site — it ships off. Add external addresses per newsletter as a simple list. Be aware of what they get: the ungated public version of the newsletter, with no personalized sections, no open or click tracking, and no poll voting. It's built for the board member or contractor who needs to receive the update, not as a substitute for a marketing email platform with managed contact lists.

Three ways, and comms teams end up using all of them. In the editor, preview as a chosen employee to see their version and a count of how many sections are hidden from them. Before sending, send a test to any address, rendered as that employee. And after a send, open any recipient's row to see the exact version that was delivered to them — which settles "did she actually get the leadership section?" without guesswork.

Each employee gets a My Newsletters page listing the newsletters that were sent to them, searchable by keyword, showing their own personalized version of each one. It's a personal archive rather than a company-wide back-issue library, which is the right default when sends are targeted — people see what was meant for them, not an index of everything ever published. Admins can browse every sent newsletter from the manager.

Worth understanding precisely, because two different things are going on. Section gating is enforced per recipient at send time — restrict a section to a persona, site role, or space and only qualifying recipients receive it in their copy. Embedded content cards work differently. By default a card carries the headline, summary, image, and a link, and the link enforces access when it's clicked: someone without permission can't open the article. But the card's headline and summary go to everyone in that section, and if you switch a card to full-body, the entire article text is inlined into the email with no per-reader check. So: use section gating to control who receives sensitive material, and keep full-body embeds for content the whole audience can already see. If you're mapping this against a specific confidentiality requirement, walk it through with us before you design the send.