Skip to content
Sign inRequest access

Announcements & changelog

This is the “tell users what’s new” side of uMarker. It has three surfaces, all driven from the same project:

  • Announcements: timed pop-ups delivered through the widget, with an optional image and call-to-action. They live in the space navigation under Announcements.
  • Changelog: a running list of entries (title, body, tag, date, optional hero image) that powers a hosted public page. It lives on the project itself, under the Changelog tab.
  • What’s new: an in-widget feed of the recent changelog entries and live announcements, with an unread count on its own button.

Everything a visitor sees is delivered without blocking or breaking the host page, even if the backend is slow or unavailable.

An announcement is a publishable pop-up for one project: a title, a rich body, an optional image, an optional call-to-action, a live window, and a frequency cap. The widget shows it to matching visitors and records who saw it and who clicked.

  1. Go to Announcements → Create, pick the project, give it a title (up to 200 characters), and pick its kind: news, feature, improvement, or fix, which sets the icon and tone of the pop-up. It starts as a draft.

  2. Write the body in safe markdown (up to 20,000 characters). The editor is a small WYSIWYG (bold, italic, lists, links), so nobody has to type markdown syntax.

  3. Optionally add an image: png, jpg, jpeg, webp, or gif, up to 1,024 KB. SVG is not accepted.

  4. Optionally add a call-to-action: a button label (up to 60 characters) and a URL (up to 2,048 characters). The two are paired: a CTA needs both a label and a URL, or neither.

  5. Set the live window and the frequency cap. Both ends of the window are optional: leave starts_at empty and the announcement goes live the moment it is published, leave ends_at empty and it runs until you unpublish it. An ends_at must be strictly after a starts_at you have set. Optionally narrow the audience, and set the pop-up’s corner and theme (auto, light, or dark).

  6. Publish. The announcement goes live to matching visitors as soon as it is published and inside its window.

An announcement is shown only while it is published and inside its live window. Two frequency caps govern repeat views:

Frequency Behavior
once A given visitor is shown it at most once, across sessions.
every It may show again on every visit.

An end time equal to or earlier than the start is refused: a window that cannot contain a moment would be published and shown to nobody, with nothing on screen to say so.

That check needs a start to compare against. With starts_at left empty, an ends_at already in the past is accepted — and leaves the announcement published, inside no window, and shown to nobody, which is the state the check exists to prevent. If you leave the start empty, leave the end empty too.

Dismissing an announcement marks it seen for cap purposes. Because the cap is enforced with per-visitor browser storage, tracking is best-effort: a visitor with cleared or blocked storage may see a once announcement again, but delivery never errors or blocks the page. Editing a live announcement’s content does not reset a visitor’s seen state.

Beyond the live window, the same lightweight targeting available to surveys applies:

  • Audience: everyone, or only identified visitors.
  • URL contains: a substring the page URL must contain (up to 300 characters).

Where no rule is set, the announcement targets every matching visitor. When several announcements are live at once, two limits apply and the order matters: the widget is sent the ten most recently created live ones — targeting plays no part in that cut — and then shows the first of those that matches this visitor, one pop-up at a time. An eleventh live announcement is never offered to the visitor, however well it targets them.

Two beacons from the widget feed the announcement’s dashboard detail:

  • a seen count, sent the first time the pop-up is shown to a visitor, and
  • a click count, sent the first time that visitor activates the CTA.

Both beacons are deduplicated per visitor, per announcement, in the same browser storage the frequency cap uses. So these are reach, not impressions: an announcement set to every that one visitor sees fifty times counts one seen, and a second click by the same person counts nothing. The same best-effort caveat applies — a visitor who clears or blocks storage is counted again.

Beacons only count for an announcement the feed would actually serve. A draft, unpublished, or out-of-window announcement never pollutes these numbers.

Both counts sit on the announcements list and on the announcement itself, on every plan that includes announcements. They also roll up, across every announcement, on the Insights page — but that page is a separate Professional capability, so a Starter account reads its totals one announcement at a time.

A changelog entry is a durable, linkable note of a change. Unlike an announcement, it does not need the snippet: the hosted page below serves with nothing pasted on your site, and with the Snippet switch off. It does need the project to be published, which in turn needs at least one allowed domain — see Install the website widget.

Open a project and choose its Changelog tab. Each entry has a title (up to 200 characters), a body in safe markdown (up to 20,000 characters), a tag, an entry date, and an optional hero image (same formats and 1,024 KB cap as an announcement image). A live preview beside the composer shows the entry as the public page will render it. Entries are draft until you publish them; unpublish moves an entry back to draft.

The tag is one of:

  • new
  • improved
  • fixed

The date field is pre-filled with your own day in the timezone on your profile — never in UTC, which would date an entry written at 01:00 in Riyadh to the day before. One caveat: a profile with no timezone saved falls back to your browser’s day. The profile form shows Asia/Riyadh already selected, but nothing is stored until you press Save, so set it once under Profile → Timezone. Either way the field is an ordinary date picker you can overwrite before saving.

Every published project, on a plan that includes announcements, has a public changelog page at a stable URL keyed by its public widget key:

Public changelog URL
https://api.umarker.com/changelog/<public_key>

It is unauthenticated: anyone with the link can read it. It lists only that project’s published entries, newest first by entry date, twenty to a page, and never exposes drafts or any other tenant’s data. A project with no published entries shows a designed empty state rather than an error.

The URL returns a clean not-found — never someone else’s changelog — when the key is unknown, when the project is back in Draft, when the account is suspended, or when the plan no longer includes announcements.

The page is served in your brand’s language (the language the entries were written in) rather than in the reader’s browser language, because English furniture wrapped around Arabic text reads as a half-finished product. A Powered by uMarker footer appears unless your plan removes uMarker branding.

Find the <public_key> on the project’s Widget → Snippet tab. It is the same key the widget snippet uses. Rotating or revoking that key changes or disables this URL too. uMarker does not print the assembled link anywhere in the dashboard — copy the key and put it after /changelog/ yourself.

The widget also carries a What’s new view: the recent published changelog entries for the project, read in-context. It has its own button, separate from the feedback launcher: pinned to the bottom-left of the page rather than to the corner you chose for the launcher, and drawn only once the project has at least one published entry.

That button carries a red unread badge counting the feed entries created after the newest one this visitor has already seen. Opening it clears the badge and marks everything seen. The comparison is by creation order rather than by publish time, so an entry you drafted before the visitor’s last visit and published after it does not move the badge. The count is the whole of the distinction — inside the open panel every entry is drawn identically, so a visitor cannot tell which of them are the new ones.

The widget feed serves the live announcements (newest first, up to 10) and the recent published changelog entries (up to 20). This is the surface that closes the loop for a returning visitor when you announce a fix.

Both announcement and changelog bodies are written in a deliberately small markdown subset, chosen so authored content can never inject script or styles into the host page or the public page. The body is HTML-escaped first: any raw HTML, <script>, style, or event handler you type is neutralized before any markdown is interpreted.

  • Paragraphs, separated by a blank line
  • Bulleted lists with -
  • **bold**
  • *italic*
  • `code`
  • [link text](https://example.com) (http/https only)

Links are rendered with rel="noopener nofollow" and open in a new tab. There is no raw-HTML passthrough and no attribute support. The escape-first allowlist is the whole rendering surface.

Titles and bodies on both surfaces have an Arabic tab and an English tab. The visitor reads the language of the page they are on; the hosted changelog page follows your brand’s language. Fill in one language only and that is what every reader gets.

Both surfaces share one set of permissions, and a per-project role can override the space role:

Action Permission
See the list, open an entry or announcement content.view
Create one content.create
Edit it content.update
Publish or unpublish content.publish
Delete it content.delete