Chartbeat

What Is Chartbeat?

Chartbeat is a real-time content analytics platform built specifically for publishers, newsrooms, and media companies. Rather than focusing on conversions or ecommerce funnels, it answers the questions editors and content teams care about most: how many people are reading right now, which stories are holding attention, how visitors arrived, and whether they are scrolling and engaging or bouncing away. Chartbeat's signature is its live dashboard, which shows traffic and engagement updating second by second, giving newsroom staff an at-a-glance picture of what is resonating with the audience at this very moment.

Chartbeat has long been associated with journalism and digital media, and it is widely used inside newsrooms to inform editorial decisions like homepage curation, headline testing, and promotion of stories that are gaining traction. Its emphasis on engaged time, the amount of time a reader is actively paying attention to a page rather than simply having it open, helped popularize attention as a more meaningful metric than raw page views for content businesses. That focus on quality of attention is central to how Chartbeat positions itself against general-purpose analytics tools.

The platform is a hosted, server-side analytics service fed by a client-side tracking script. A small JavaScript snippet on each page measures activity, scrolling, clicks, tab focus, time on page, and streams it to Chartbeat's servers, which aggregate the data and surface it in real-time and historical dashboards. It is not a CMS, an ad system, or a browser extension; it is a measurement layer that a publisher adds to an existing website to understand audience behavior, particularly while that behavior is still unfolding.

Chartbeat's product family extends beyond the live dashboard. Over time it has offered headline testing tools, historical and editorial reporting, and video analytics, all oriented around the needs of content teams. The unifying idea is that newsrooms operate on fast cycles, a story can surge or fade within an hour, and that the analytics serving them must be immediate and editorially relevant rather than retrospective and conversion-focused. This is why Chartbeat is often described as an editorial analytics or audience-engagement tool rather than a generic web analytics product.

It helps to frame Chartbeat against more familiar analytics. Tools like Google Analytics are broad, retrospective, and built for any kind of site, excelling at sessions, acquisition, and conversion reporting. Chartbeat is narrow and real-time, built for the specific moment-to-moment decisions a newsroom makes. Many publishers run both: a general analytics platform for overall reporting and Chartbeat for the live editorial view. Detecting Chartbeat on a site is therefore a strong indicator that the site is a content publisher with an active editorial operation.

How Chartbeat Works

Chartbeat follows the standard analytics architecture of client-side collection feeding server-side aggregation, but tuned for real-time engagement measurement. When a page loads, the Chartbeat tracking snippet initializes and begins measuring not just that the page was viewed but how the visitor interacts with it over time. Crucially, it tracks engaged time, using signals like scrolling, mouse movement, clicks, and whether the browser tab is focused to estimate how long a reader is actively paying attention, as opposed to leaving the tab open in the background.

The snippet streams this activity to Chartbeat's collection servers, frequently and continuously while the reader is on the page, which is what enables the live, second-by-second dashboard. Configuration values in the snippet identify the publisher's account and often the section, author, and page type, so the data can be broken down editorially, by section, by article, by author, in the dashboard. This per-article, per-section granularity is exactly what newsroom teams need to decide what to promote or rework.

On the server side, Chartbeat aggregates the incoming activity into the real-time view (concurrent visitors, where they came from, which pages they are on, and how engaged they are) and into historical reports for longer-term analysis. Additional Chartbeat products layer on top of this foundation: headline testing runs experiments on story headlines to see which drives more clicks and engagement, and video analytics extends the engagement model to video content. Editorial dashboards present this data in a way designed for fast scanning during a news cycle rather than deep analyst exploration.

Because the measurement depends on a persistent client-side script communicating with Chartbeat's servers, the platform reveals itself through identifiable scripts and network traffic on the publisher's pages, even though the aggregation and dashboards live entirely on Chartbeat's infrastructure.

A practical detail worth understanding is that Chartbeat is often deployed across an entire publication, on every article, section page, and the homepage, because newsrooms want a complete real-time picture of the whole site. This site-wide presence makes Chartbeat comparatively easy to detect: unlike a payment processor that only appears at checkout, Chartbeat's script typically loads on virtually every content page, so any representative page is likely to show its fingerprints.

How to Tell if a Website Uses Chartbeat

Chartbeat leaves recognizable fingerprints on the pages it tracks. StackOptic inspects these from the server side, and you can confirm them manually with browser tools.

Chartbeat script domains. The strongest signal is loading the Chartbeat tracking library from its asset domains, historically files such as chartbeat.js and chartbeat_video.js served from Chartbeat-associated hosts (for example static.chartbeat.com). A request to a Chartbeat domain as the page loads is a direct indicator.

Network beacons to Chartbeat. Beyond the library, the page continuously sends activity pings to Chartbeat's collection endpoints (Chartbeat-associated "ping" domains). Seeing repeated requests to a Chartbeat host while you sit on the page, rather than a single load-time hit, is characteristic of its real-time engagement tracking.

JavaScript configuration globals. Chartbeat implementations expose a recognizable configuration object in the page source, commonly a _sf_async_config object that holds the account UID, domain, and editorial metadata like section and author. Finding _sf_async_config in the source is a reliable tell.

Inline initialization snippet. The standard install includes an inline script that sets up _sf_async_config and asynchronously loads the Chartbeat library. The presence of that snippet pattern in the HTML confirms the platform.

Method	What to do	What Chartbeat reveals
View Source	"View Page Source" and search the markup	A _sf_async_config object and the inline Chartbeat loader snippet
DevTools Network	Open the Network tab and stay on the page	The chartbeat.js library plus repeated activity pings to Chartbeat hosts
DevTools Console	Type _sf_async_config and inspect	The account UID and editorial configuration values
curl -s	`curl -s https://example.com	grep -i chartbeat`
Wappalyzer / BuiltWith	Run on the live page	Identifies "Chartbeat" under analytics

A quick terminal check is curl -s https://example.com | grep -i "_sf_async_config"; a match strongly suggests Chartbeat. Because Chartbeat is one of several content-measurement tools a publisher might run, our guide on how to find out what analytics a website uses is a useful companion, and how to find out what technology a website uses covers the broader detection workflow.

A couple of nuances are worth noting. Chartbeat is frequently loaded through a tag manager rather than hard-coded, so a raw server-side fetch of the initial HTML may not always show the snippet even though the live page loads it; in that situation, the runtime network pings and the _sf_async_config global remain reliable signals. Some publishers also customize the configuration to add their own metadata, but the _sf_async_config object name and the characteristic continuous pinging behavior are stable across installs. Because the strongest confirmation comes from seeing the ongoing activity beacons, watching the Network tab for a few seconds while remaining on the page is the single most decisive manual check. Combining the source-level _sf_async_config clue with the observed pinging gives a confident verdict. For analysts who rely on header-level signals as part of their process, how to read a website HTTP headers explains the complementary techniques.

Key Features

• Real-time dashboard. Live, second-by-second view of concurrent readers, traffic sources, and the stories they are on.
• Engaged time measurement. Tracks active attention rather than just page views, a more meaningful metric for content.
• Editorial breakdowns. Data segmented by section, author, and article to inform newsroom decisions.
• Headline testing. Experiments that compare headline variants for clicks and engagement.
• Historical reporting. Longer-term trends alongside the real-time view for editorial analysis.
• Video analytics. Engagement measurement extended to video content.
• Newsroom-oriented design. Dashboards built for fast scanning during a live news cycle.

Pros and Cons

Pros

• Purpose-built for publishers, with metrics and dashboards aligned to editorial work.
• Real-time insight that supports fast homepage and promotion decisions.
• Engaged-time focus gives a truer picture of content quality than page views alone.
• Headline testing and editorial breakdowns directly support content strategy.

Cons

• Narrow focus: not designed for ecommerce, conversion, or product analytics.
• A paid, specialized tool that may be unnecessary outside publishing.
• Real-time emphasis is less suited to deep, retrospective analysis than general platforms.
• Typically used alongside, not instead of, a general analytics tool, adding another vendor.

Chartbeat vs Alternatives

Chartbeat competes with other content-and-engagement analytics tools and overlaps partly with general analytics. The table positions it against common alternatives.

Tool	Focus	Real-time strength	Best for
Chartbeat	Editorial / engagement	Live newsroom dashboard	Publishers and newsrooms
Parse.ly	Content analytics	Real-time and historical	Content marketing and publishers
Google Analytics 4	General web analytics	Real-time view, broad reporting	Most websites
Adobe Analytics	Enterprise analytics	Real-time at scale	Large analytically mature orgs
Matomo	General / privacy	Real-time visits	Privacy-conscious and self-hosting teams

If a site turns out to use a different measurement tool, the same signals identify it. You can compare Chartbeat with the general-purpose Google Analytics to see how editorial real-time analytics differs from broad web reporting.

Use Cases

Chartbeat is the natural fit for newsrooms and digital publishers that make fast, audience-driven editorial decisions. News organizations use the real-time dashboard to see which stories are surging and to curate the homepage accordingly, promoting pieces that are gaining traction and reworking those that are not. Editors use engaged-time data to judge whether readers are actually consuming an article or bouncing, a more honest signal than clicks alone.

It also serves digital magazines and content-marketing teams measuring how well articles hold attention, media companies running headline tests to improve click-through, and video-led publishers tracking engagement on their players. For technology and competitive research, the presence of Chartbeat is a clear marker that a site is a content publisher with an active, metrics-informed editorial operation.

Consider a few concrete scenarios. A national news site might keep the Chartbeat live dashboard open on a newsroom wall, watching concurrent readers and traffic sources shift through the day and moving the most engaging stories to the top of the homepage. A digital magazine might A/B test two headlines on a feature and let Chartbeat's data decide which to keep. A business publisher might review engaged-time trends each week to understand which topics sustain reader attention and shape its editorial calendar accordingly. The common thread is a content operation that treats audience attention as a live, actionable signal.

From a technographic standpoint, detecting Chartbeat tells you something specific about the organization behind a site: it is almost certainly a publisher or media business with a real editorial team and a culture of measuring engagement. For vendors selling to media companies, content tools, advertising technology, subscription platforms, that is a precise qualifying signal. For analysts mapping the publishing landscape, Chartbeat helps distinguish genuine newsrooms from sites that merely host occasional articles. Our guide on what is technographics and using tech stack data to qualify leads explains how to act on signals like this at scale.

Frequently Asked Questions

What is Chartbeat used for?

Chartbeat is a real-time content analytics platform used by publishers and newsrooms to see how many people are reading right now, which stories are holding attention, where visitors came from, and how engaged readers are. Its live dashboard supports fast editorial decisions like homepage curation and story promotion, while its engaged-time metric measures active attention rather than raw page views, which content teams find more meaningful.

How do I know if a website uses Chartbeat?

View the page source and look for a _sf_async_config JavaScript object and the inline Chartbeat loader snippet, then open DevTools and watch the Network tab while staying on the page, Chartbeat sends repeated activity pings to its servers rather than a single load-time request. You can also run curl -s URL | grep -i "_sf_async_config". Tools like Wappalyzer, BuiltWith, and StackOptic identify Chartbeat automatically.

What is the difference between Chartbeat and Google Analytics?

Google Analytics is a broad, general-purpose, largely retrospective web analytics tool suited to any site, strong on sessions, acquisition, and conversions. Chartbeat is narrow and real-time, built for newsrooms making moment-to-moment editorial decisions, with engaged-time and per-article breakdowns at its core. Many publishers run both: Google Analytics for overall reporting and Chartbeat for the live editorial view, so finding Chartbeat signals a content-focused publisher.

What is engaged time in Chartbeat?

Engaged time is Chartbeat's measure of how long a reader is actively paying attention to a page, estimated from signals like scrolling, mouse movement, clicks, and whether the browser tab is focused. It distinguishes genuine reading from a page simply being left open in a background tab. Because it reflects quality of attention rather than raw views, engaged time is more useful for judging whether content is resonating with an audience.

Is Chartbeat only for large news organizations?

While Chartbeat is strongly associated with major newsrooms, it is used across content businesses of varying sizes, from large national publishers to digital magazines and content-marketing teams. The common factor is an active editorial operation that benefits from real-time, engagement-focused analytics. Smaller sites without frequent publishing or a newsroom culture often find general analytics tools sufficient and do not need Chartbeat's specialized, real-time focus.

Want to detect Chartbeat and the rest of a site's analytics stack instantly? Run any URL through StackOptic at https://stackoptic.com.