We’ve updated how view counts are measured on Noticeable Newspages.

Previously, each page load counted as a view, including traffic from bots and crawlers. Starting on May 3, 2025, at 11:00 AM UTC+2, traffic from most bots and spiders should no longer contribute to page or publication views.

If your Newspage displays full publication content on the home page, every publication shown will register a view when the page loads. If only excerpts are displayed, a publication view is counted only when a user opens the full publication.

Newspages and Widgets user interfaces now automatically use your project’s configured language if it is one of the supported locales, or fall back to English.

Here are supported locales:

• Arabic (ar-SA)

• Chinese (Simplified) (zh-CN)

• Dutch (nl-NL)

• English (en-US)

• French (fr-FR)

• German (de-DE)

• Italian (it-IT)

• Japanese (ja-JP)

• Korean (ko-KR)

• Portuguese (pt-BR)

• Russian (ru-RU)

• Spanish (es-ES)

• Turkish (tr-TR)

You can still customize all phrases as desired if one translation does not fit your needs. It’s a time saver for new and existing projects, since you no longer have to manage UI translations for new phrases we introduce over time.

Note that on Newspages, you can now remove the “All publications” link from the side menu by setting the phrase with key menu.all_publications_link_label to an empty value while customizing Newspage phrases.

• In your project settings, you can now configure some default publication preferences, ensuring your team and you don’t overlook enabling or disabling specific options. These settings can still be customized per publication in the editing process at step 2, “Options,” under the “Behaviors” settings group.

  

• When editing a publication, the text color picker now includes a text input displaying the current color in hexadecimal format, allowing you to enter your own color codes directly or copying the existing one.

  

• Additionally, all images on the Newspage and Widgets now open in a modern, responsive lightbox, enhancing the mobile experience and including zoom functionality when needed. If a publication contains multiple images, they are displayed in a carousel within the lightbox, with mouse and keyboard controls for easy navigation.

• When a publication transitions from draft to published, if no prior email forwarding has occurred, the option to forward by email is automatically enabled in the user interface. The same applies for Zapier forwarding. This helps ensure that updates are sent through all configured channels.

• The Zapier integration at the organization level has been improved, simplifying the creation and management of Zaps directly from the Noticeable dashboard.

• You can now hide on your Newspage navigation labels that have no associated publications. To enable the option, open your Newspage settings, scroll down to the “Customization” settings group and click “Hide labels without publications from navigation”.

• Support for Amplitude third-party analytics has been added.

• Third-party analytics options have been moved to a dedicated subgroup for easier management:

  

• A bug to paginate email subscribers in the Noticeable dashboard has been fixed.

• Additional social network footer link options have been added to the Newspage settings, including Discord, Instagram, Slack, TikTok, and YouTube.

• You can specify in what order social network footer link icons appear at the bottom of your Newspage.

We've deployed several internal updates over the past weeks. Here's a summary of the visible changes we've introduced:

• The Emails section now includes a new Events category to list and analyze all email events, with details for each recipient, including subscription methods, reasons for undelivered emails, delivery times, and link clicks.
  

  

  Event access periods vary by plan:

  • Starter: last 24 hours.

  • Growth: last 7 days.

  • Business: last 31 days.

  • Enterprise: last 365 days.

• Emails sent via Noticeable's native email feature now include a link for managing subscription preferences, allowing users to update their first and last names, but also to unsubscribe or resubscribe.

• The unsubscribe link in emails now redirects to a confirmation page to prevent accidental unsubscribes due to some email security client proxies automatically following links.

• The list of email subscribers on the Noticeable dashboard now defaults to sorting by creation time, then by last updated time.

• The Noticeable dashboard pagination now allows you to select the number of rows per page and shows the current position as a range where possible.

• Introducing an advanced feature for Newspages: now you can select publications to exclude from the default Newspage listing based on labels, such as labels for upcoming features. To access this feature, click on "Newspage" in the left navigation menu, scroll to the bottom of the page, and select "Advanced options".

• Add a confirmation dialog to acknowledge the deletion of a featured image from a publication.

• Add AutoSubmitted and Precedence headers when appropriate for emails sent by Noticeable to better manage email behavior.

• Fixed a bug that occurred when duplicating a publication with a featured image; the copy was using the reference to the same featured image instead of creating a copy. Now, a duplicated publication no longer has any featured image.

• Resolved a problem where the drag-and-drop functionality for files was not operating correctly on file input fields.

• Addressed a glitch affecting widget loading and synchronization, which occasionally led to inaccurate view count metrics.

• When a publication configured to open widgets automatically opens a widget, this is counted as a widget view.

• Introduced a convenient refresh shortcut for project analytics, located at the top-right corner, enabling users to update analytics data without reloading the entire dashboard.

  

• Added a smooth animation when changing from an activity period to another on analytics page:

  

We have introduced a technical enhancement that elevates speed, security and the ease of configuring custom domains for your Newspages.

Previously, if you wanted to use a custom domain like updates.acme.com for your Noticeable Newspage, you were required to set up two DNS records: a TXT record to verify domain ownership and another to link to Noticeable's servers.

As of now, Noticeable utilizes Cloudflare's extensive global infrastructure for managing custom domains, simplifying the process. The need for a TXT DNS record for domain verification is eliminated. If you've previously set up a TXT record beginning with _noticeable, it's now safe to remove it. You'll only need a single CNAME record pointing to custom.noticeable.news, which you likely already have if you've configured a custom domain before.

Leveraging Cloudflare's infrastructure enhances the speed of HTTPS certificate issuance for your custom domain and reduces network latency with its presence in over 250 regions worldwide. Additionally, loading times get a boost from early hints support, and security is strengthened with the enforcement of at least TLS 1.2 and support for TLS 1.3.

It's important to note that Cloudflare employs the Google Trust Services certificate authority for signing TLS certificates. If you encounter an ERR_SSL_VERSION_OR_CIPHER_MISMATCH error with your custom domain, it might be due to CAA DNS records that don't include pki.goog on your parent domain. Adding pki.goog to your CAA records and initiating a custom domain verification through the Noticeable dashboard should resolve the issue:

1. Open the Noticeable Dashboard.

2. Navigate to “Newspage” in the left menu.

3. Under “Basic & Custom Domain”, and click on “Verify Domain”.

Should you have any questions or require assistance, feel free to share your feedback below or drop us a line.

We’re excited to introduce end user authentication with Noticeable widgets.

End user authentication is a feature you can optionally integrate to verify the identities of your end users. This ensures that when end users engage with widgets, such as commenting, their identity is confirmed and secure from impersonation.

How does it function?

Noticeable employs Single Sign-On (SSO) tokens for this authentication process:

1. On your server(s) side, you create an SSO token for each end user (using a secret we share).

2. You pass this SSO token with our Javascript SDK before rendering any widget.

3. Voilà! Your end user's identity is now securely authenticated with Noticeable widgets.

Note: While it's still possible to pass end user traits using our Javascript SDK as outlined in our various identification methods, this approach is no longer recommended.