How to Tell If a Website Uses Chartbeat

Chartbeat is the leading real-time editorial analytics platform for publishers — the dashboard newsrooms watch to see what readers are engaging with right now. Because it exposes a distinctive config global and pings a recognisable domain, detecting it is straightforward: type _sf_async_config into the console or look for static.chartbeat.com scripts. This guide covers every reliable signal, the real-time model behind them, the look-alikes to rule out, and what Chartbeat usage tells you about the site and the newsroom behind it. Because Chartbeat is built specifically for editorial teams, recognising it is also a quick way to confirm you are looking at a professional publisher rather than a general business blog.

What is Chartbeat?

Chartbeat is an analytics platform built specifically for publishers and editorial teams. Unlike general web analytics, it focuses on real-time, attention-based metrics: how many people are on the site right now, engaged time (how long readers actually spend reading, not just page views), which articles and sections are performing live, and where traffic is coming from minute by minute. Newsrooms use Chartbeat's real-time dashboard to make editorial decisions — what to promote on the homepage, which stories are resonating, when to push a piece on social. It is a fixture of news organisations, magazines and large content sites.

For detection, the key context is that Chartbeat signals a publisher with an editorial, audience-engagement focus. Finding it tells you the site is a content operation that monitors live reader engagement to drive editorial decisions — a news or media property rather than a typical business site. Because Chartbeat exposes the _sf_async_config global (with the account uid) and pings ping.chartbeat.net, it is easy to confirm, and the uid identifies the account. Its presence marks the editorial-analytics-driven publisher segment.

How Chartbeat loads and runs

A Chartbeat install defines the global window._sf_async_config object carrying the account uid, the domain, and settings (e.g. useCanonical, sections, authors). It then loads Chartbeat's scripts from static.chartbeat.com (the main chartbeat.js and the video/engagement modules). Once running, it sends frequent real-time pings to ping.chartbeat.net (and pingjs.chartbeat.net) to track engaged time and concurrent readers — the continuous pinging is characteristic of its real-time, attention-based model.

The _sf_ prefix in the config global is a historical artefact (Chartbeat's lineage), but it remains the defining signal. The uid identifies the Chartbeat account, and the domain/sections/authors fields reflect the publisher's content structure. So a Chartbeat site shows the _sf_async_config global (with uid), the static.chartbeat.com scripts, and the ping.chartbeat.net real-time pings. Knowing these makes detection quick and account-identifiable.

How to tell if a website uses Chartbeat

Confirm at least one strong signal (the config global suffices).

1. Use the console. Type _sf_async_config and press Enter. A returned object with a uid and domain confirms Chartbeat.

2. Check the Network tab. Filter for chartbeat. Scripts from static.chartbeat.com and pings to ping.chartbeat.net/pingjs.chartbeat.net confirm Chartbeat.

3. View the source. Search for chartbeat or _sf_async_config. The config object and the static.chartbeat.com script reference are usually visible.

4. Read the uid. The uid in _sf_async_config identifies the Chartbeat account.

5. Note the real-time pings. Frequent pings to ping.chartbeat.net reflect Chartbeat's engaged-time measurement.

What the Chartbeat signals look like

var _sf_async_config = window._sf_async_config = (window._sf_async_config || {});
_sf_async_config.uid = 12345; _sf_async_config.domain = "example.com"; _sf_async_config.useCanonical = true;
<script src="//static.chartbeat.com/js/chartbeat.js"></script>
GET https://ping.chartbeat.net/ping?h=example.com&...   (real-time engagement ping)

The _sf_async_config global with a uid, the static.chartbeat.com scripts, and the ping.chartbeat.net pings are conclusive.

Chartbeat versus other analytics — avoiding false positives

Match the global and domains to keep editorial/analytics tools distinct. Chartbeat uses _sf_async_config, static.chartbeat.com and ping.chartbeat.net; Parse.ly (another publisher analytics tool) uses cdn.parsely.com and a PARSELY global; comScore is audience measurement on scorecardresearch.com; general analytics (GA4) is different. The _sf_async_config global and the chartbeat.net pings are unique to Chartbeat. Publishers often run Chartbeat alongside GA4 and an audience-measurement tool (comScore), so finding Chartbeat does not exclude those — each serves a different purpose (real-time editorial vs general analytics vs audience measurement). The real-time pinging is Chartbeat's behavioural signature.

How reliable is each Chartbeat signal?

The _sf_async_config global with a uid is definitive and identifies the account, as are the static.chartbeat.com scripts and the ping.chartbeat.net pings. The continuous real-time pinging corroborates. There is essentially no false-positive risk once you see _sf_async_config with a uid. As a rule, the config global or the chartbeat.net pings settle it immediately, and the uid identifies the publisher's account.

What Chartbeat usage reveals about a site

Finding Chartbeat signals a publisher with a real-time, editorial-engagement focus. Its attention-based metrics are built for newsrooms making live content decisions, so its presence almost always means a news organisation, magazine or large content site with an editorial team that watches reader engagement minute by minute. Finding it tells you the site treats audience engagement as an editorial discipline, not just a marketing metric. The sections and authors configured in _sf_async_config even reveal the publisher's content structure. If you sell publisher tools, content, audience, or editorial-analytics products, a Chartbeat site marks an editorial-driven publisher. It commonly accompanies other publisher infrastructure (ad networks, comScore, a CMS built for publishing), so it is a strong marker of the professional media segment.

What finding Chartbeat means for sales, agencies and competitive research

For sales and prospecting, Chartbeat marks a professional publisher with an editorial-analytics practice — a fit for publisher tools, content, audience and editorial products. It signals a content operation with a newsroom.

For agencies and consultants, finding Chartbeat tells you the client makes real-time editorial decisions, so engagements can focus on content strategy, homepage optimisation, or audience growth informed by engaged-time data.

For competitive and market research, Chartbeat (versus general analytics alone) reveals which competitors run a real-time editorial practice, and the content structure in its config hints at how they organise their newsroom — useful when benchmarking publishing sophistication.

Chartbeat in the wider publisher stack

Chartbeat sits in the editorial-analytics layer of a publisher's stack. It accompanies a publishing CMS (WordPress VIP, Arc, or a custom platform), general analytics (GA4), audience measurement (comScore), advertising (Google Ad Manager, header bidding, native ads like Taboola/Outbrain), and a consent-management platform. The combination of Chartbeat plus comScore plus ad infrastructure is a classic professional-publisher signature. For an auditor, the valuable details are the Chartbeat uid, the sections/authors structure, and the surrounding publishing, ad and measurement tools; together these reveal a professional media operation and how it runs its editorial and monetisation. Chartbeat is also a strong segmentation signal in its own right: because it is built specifically for newsrooms and rarely appears outside professional publishing, its presence reliably separates genuine editorial operations from ordinary content marketing or business blogs. The configured sections and authors go further still, sketching the publisher's beat structure and bylined contributors — an unusually detailed glimpse into how the newsroom is organised. For anyone selling to, partnering with, or competing against publishers, that editorial fingerprint turns a Chartbeat detection into a rich, actionable profile rather than a bare tooling fact, and tracking it across a media market quickly maps who runs a serious, real-time newsroom.

A quick Chartbeat confirmation walkthrough

Open the site (a news or content page) with developer tools on the Console panel and type _sf_async_config — a returned object with a uid and domain confirms Chartbeat. Switch to the Network tab, filter for chartbeat, and confirm scripts from static.chartbeat.com and frequent pings to ping.chartbeat.net. View the source for chartbeat and the config object; read the uid. The _sf_async_config global or the chartbeat.net pings confirm Chartbeat.

A quick Chartbeat detection checklist

• Type _sf_async_config in the console; a returned object with a uid is conclusive.
• Filter the Network tab for chartbeat; static.chartbeat.com scripts and ping.chartbeat.net pings confirm it.
• Read the uid to identify the Chartbeat account.
• Note the frequent real-time pings (engaged-time measurement).
• Check the sections/authors config for the publisher's content structure.
• Distinguish Chartbeat (_sf_async_config) from Parse.ly (PARSELY) and comScore.

Detecting Chartbeat at scale

Checking one site is quick, but mapping editorial-analytics adoption across many domains — to find and segment professional publishers — calls for automation. StackOptic detects Chartbeat and thousands of other technologies from a real browser, reading the config global, scripts and pings. Tracking Chartbeat adoption across a media market is a quick way to identify which outlets run a real-time newsroom and which rely only on retrospective analytics — a meaningful distinction in editorial sophistication. For related reading, see our guide to finding out what analytics a website uses and the full Chartbeat technology profile.