Added Google Search Console data to the Parse.ly MCP server: top Google searches, top Discover and News pages, and the searches that bring readers to an article.
Fixed
Fixed large tag and section exports with share columns failing to generate.
Added site-specific styling for the HUD. Reach out to your Parse.ly relationship or account manager to have the HUD adjusted for your site, for example to make its metric badges smaller or more transparent so they cover less of your headlines.
Fixed
The dashboard no longer gets stuck on a blank loading screen during a backend outage — it now shows a retry screen that keeps trying automatically.
Fixed an illegible logo on the “Can’t reach Parse.ly” screen when the dashboard’s theme is set to Auto.
Added a resize handle to the Parse.ly HUD’s side panel. Drag it, or focus it and use the arrow keys, to set the panel’s width; double-click it to go back to the default. Your chosen width is remembered.
Changed
Narrowed the Parse.ly HUD’s side panel so more of your page stays visible beside it.
Fixed
Fixed the Parse.ly HUD’s side panel reopening on every page load after being closed. It now stays closed as you move between pages, for the rest of the browser session.
Restored the explanations that appear when you hover a metric in a metric picker. They also now appear when you reach a metric with the keyboard.
Search results on a network dashboard now show which site each post, video or page belongs to, on the Search page and in the top bar search.
Fixed
Fixed the links to the original article on search results when picking a post for a new headline test.
Fixed search suggestions on networks without rollup opening a page that said “This view is not available for this account.” They now open on the site each result comes from.
Restored Parse.ly MCP sign-in for clients that register dynamically (Claude Desktop, Copilot Studio).
MCP connections stay authenticated longer between sign-ins, so tools that don’t refresh tokens silently disconnect less often.
Engaged minutes for new and returning visitors can now be picked as the primary metric in the Parse.ly MCP and Sage analytics tools.
Sage and the MCP server can now return a single video’s detail: the pages it played on with the video’s starts and watched minutes on each, plus its totals and timeline.
Color vision modes in the Overlay. The View menu now offers palettes tuned for red-green, blue-yellow and monochrome color vision, each chosen so that performance levels stay distinguishable. The setting is independent of the light and dark themes, and the existing colors remain the default.
The Overlay panel can now be docked to the left or right side of the page.
Added an Export option to the Categories tab under Referrers, which downloads the full referrer breakdown by category as a spreadsheet or CSV.
Sage app can now answer Parse.ly usage and adoption questions, such as active users, reports run, and API calls per endpoint.
Sage now answers Parse.ly dashboard-usage and adoption questions, including for a specific past month (e.g. “dashboard usage for February 2026”).
Changed
Signal now measures conversion-based scores using your site’s conversion attribution model of preference, and site admins can choose a different one for Signal from the KPI Metrics page.
Fixed
Author, tag, section, campaign, referrer, and conversion groups beyond the first 100 are now available in filters, reports, and group management. Previously a site with many groups could see a group in its listing but not select it as a filter or edit it.
Fixed the Sage chat sometimes staying stuck loading after a reply finished.
Fixed Sage documentation links: removed duplicates, made same-named links distinct, and stopped showing bare URLs.
We’re experimenting with new ways of exporting large amounts of data. If you’d like to try it out, contact support and ask to be included in the Bulk Exports beta!
Fixed
Closing the Heads Up Display now sticks. It stays closed as you move between pages until you reopen it from the Parse.ly leaf.
A public Parse.ly changelog at docs.parse.ly/changelog. New features, changes, and fixes to the Parse.ly Dashboard now publish there automatically as they ship.
As an open source company, we take your privacy seriously and want to be as transparent as possible.
So: We use cookies to collect some personal data from you (like your browsing data, IP addresses,
and other unique identifiers). Some of these cookies we absolutely need in order to make things
work, and others you can choose in order to optimize your experience while using our site and
services.
As an open source company, we take your privacy seriously and want to be as transparent as possible.
So: We use cookies to collect some personal data from you (like your browsing data, IP addresses,
and other unique identifiers). Some of these cookies we absolutely need in order to make things
work, and others you can choose in order to optimize your experience while using our site and
services.
Required
These cookies are essential for our websites and services to perform basic functions and are
necessary for us to operate certain features, like allowing registered users to authenticate and
perform account-related functions, storing preferences set by users (like account name,
language, and location), and ensuring our services operate properly.
Analytics
These cookies allow us to optimize performance by collecting information on how users interact
with our websites.
Advertising
We and our advertising partners set these cookies to provide you with relevant content and to understand that content’s effectiveness.