Subscriber count is for the business card. What actually matters is whether those subscribers read what you post, react to it, forward it. That's what determines channel value for advertisers — and whether you're having a real conversation with your audience or just broadcasting into a void.
ERR: the number worth paying attention to
ERR stands for Engagement Rate by Reach — average post views divided by subscriber count, multiplied by 100. A channel with 20,000 subscribers and 5,000 views per post sits at 25% ERR.
Why ERR and not just raw views? Because raw views lie when you're comparing channels. A 5,000-subscriber channel with 3,000 views (60% ERR) is dramatically more engaged than a 500,000-subscriber channel with 40,000 views (8% ERR). The big number looks impressive, but most of that audience isn't reading.
Rough benchmarks: channels under 10K should be somewhere in the 20–40% range normally, up to 80% if content is exceptional. From 10K to 100K, the 10–20% range is typical. Large channels between 100K and 1M tend to land at 5–10%. Above a million, anything around 2–5% is considered healthy. Significantly below those floors is worth investigating.
When the ERR number lies
View inflation is a commercial service — bots open post links from different accounts, the counter ticks up, ERR looks fine. Spotting it isn't hard once you know what to look for.
Reactions are the most reliable signal. Real readers occasionally tap a button. A healthy channel converts somewhere between 0.5% and 5% of views into reactions. A post with 50,000 views and 30 reactions isn't a real audience — it's a number.
Forwards matter too. Content that resonates gets shared to chats, forwarded to Saved Messages. Zero forwards alongside thousands of views is a red flag. And watch for uniformity — organic ERR bounces around from post to post based on how interesting each one is. If every single post lands at nearly the same view count, that's automation, not an audience.
What actually moves the number
Honestly, it depends on the channel. A financial news feed and a cooking tutorial channel play by completely different rules. But a few things tend to work broadly.
Exclusivity consistently bumps ERR. If someone can't find the information anywhere else — real personal experience, industry insider detail, a genuinely original take — people share it. Polls and direct questions to the audience reliably generate the highest interaction rates, because clicking a button costs almost nothing. Actionable guides and checklists get saved and forwarded more than opinion pieces.
What works in a breaking-news channel won't work in an educational one. Use these as starting hypotheses, then look at your own data after a month.
How TGuard catches view spikes
TGuard logs view counts for each post every hour and compares them against that channel's historical baseline for similar time windows. When a specific post spikes anomalously — without an obvious external trigger like a repost in a major channel — the bot sends an alert: post link, hour of the spike, view count, percentage above baseline. Everything is logged in the engagement dashboard so you can review the pattern later.
This works both ways. Sometimes a post goes organically viral and you genuinely want to know why — seeing it flagged as a spike is useful data about what resonated.
Putting the data to work
The simplest starting point is publication timing. Compare ERR across posts at different times of day and days of the week. Within three or four weeks, a pattern usually becomes clear.
From there, track by content type. Which series consistently outperform your average? Which ones drag below it? You don't need to kill underperforming formats immediately, but knowing which is which is half the work.
The one signal worth watching for over the longer term: if ERR drifts downward across several consecutive months with no obvious cause, that's a sign your content and audience are slowly drifting apart. Catching it early is much easier to fix than catching it late.
Frequently Asked Questions
ERR (Engagement Rate by Reach) is the ratio of a post's views to the channel's subscriber count. It shows what share of the audience actually reads each publication and is the primary indicator of audience quality and engagement.
TGuard tracks view counts for each post on an hourly basis and compares them to the channel's historical baseline. When a spike is detected, the channel owner receives an alert with the post link and the percentage increase. A log of all view spike events is available in the TGuard engagement dashboard.
Analytics consistently shows the highest engagement for exclusive insights, opinion pieces, polls and interactive content, and actionable practical guides. But the best answer is always to analyze your specific audience data rather than follow generic advice.