DEV Community

Cover image for 78 Posts, 131 Views, 5 Reactions — What "Being on Platforms" Actually Got Us

78 Posts, 131 Views, 5 Reactions — What "Being on Platforms" Actually Got Us

We had been counting the wrong number for a long time. The metric that felt like progress was posts published — the content calendar filling up, articles going live across four platforms, the reassuring sense of presence. So we finally added up what that presence actually produced in the only terms that matter downstream: did anyone view these posts, and did anyone react. The answer is small enough to be uncomfortable, and that discomfort is the entire point of writing it down.

This is a report on our own reach numbers. It is not a tools review and it is not a content-strategy pep talk. It is the raw count of what publishing across platforms yielded in views and reactions, what those numbers do and do not mean, and why one of them is more misleading than it looks.

What we wanted to find out, and why it matters to you

The question is blunt: for all the posts we put on other people's platforms, how many views and reactions came back?

It matters because "we're active on platforms" is one of the easiest claims in marketing to make and one of the least examined. Publishing is visible and feels productive; readership is invisible unless you go count it. Any team running a multi-platform content push is implicitly betting that presence converts into attention, and almost nobody checks the exchange rate. We checked ours. If you run the same kind of program, this is the number you are probably not looking at either.

How we measured it, so you can repeat it

We pulled each platform's own reported statistics, using its API where one exists. Views come from the platform's own numbers, not from an estimate or a third-party guess — if the platform says a post got a certain number of views, that is what we recorded.

The one rule that shapes everything downstream: where a platform reports nothing, we counted the post but did not count views for it. That is not the same as recording zero reads. A platform that exposes no view stats gives us no data, and "no data" is a different state from "measured and found empty." We kept those apart deliberately, because collapsing them would turn "we can't see it" into "nobody read it," which is a claim we cannot support.

If you want to repeat this, the method is just discipline: go to each platform's own analytics, record what it reports per post, count the post either way, and never fill an unreported field with a zero. Presence is easy to tally from your own publishing log; reception has to come from the platforms themselves.

What came out

Across everything, 78 posts. 131 views. 5 reactions.

The average the arithmetic produces is 1.7 views per post. We are stating it because it is the honest headline figure, but it is also the most misleading one in this report, and the next paragraph is why.

Broken out by platform: devto, 19 posts and 131 views. telegram_dzen, 19 posts and 0 views. telegraph, 20 posts and 0 views. tumblr, 20 posts and 0 views. Every measured view we have came from one platform. The zeros on the other three are not a verdict that nobody read them — they are the "no data" state from the method above. Those platforms reported nothing back to us, so we have nothing to record, which is not the same as a confirmed absence of readers.

That is what makes the 1.7 average deceptive in both directions at once. It divides 131 views across all 78 posts, including the posts on platforms that never reported a single figure. So it understates whatever the reporting platform actually did, and it silently treats unmeasured posts as if they contributed nothing. The average is arithmetically correct and analytically close to meaningless, which is a useful reminder that a true number can still mislead.

The reactions figure needs no such caveat. 5 reactions across 78 posts is simply small, and we are not going to dress it up. Whatever readership exists behind the views, almost none of it did the one thing that signals a post landed — clicked a reaction. That is the least flattering number here and the one we are most sure of.

Limits: what this does not prove

The caveats are not a footnote, they are half the finding.

The total is a floor, not the full picture. Because three of the four platforms reported no view stats at all, 131 is the number we could see, not the number that happened. The real total could be higher and we have no way, from this data, to know by how much. We are reporting what is measurable and refusing to guess at what is not.

These numbers cannot rank the platforms. This is the trap to avoid hardest. It is tempting to read the breakdown and conclude that the one platform showing 131 views is our "best" channel and the others are dead. That conclusion is not available from this data, because the others are not showing zeros — they are showing nothing. A platform that reports well will always look better than one that reports nothing, regardless of what actually happened on either. Comparing them here would be measuring which platform has an analytics API, not which platform has readers.

It is one snapshot, and views are not reads and not value. A view is a platform's count of a page load; it is not proof someone read the piece, and reading is not proof the piece did anything for us. We measured the shallowest layer of attention, because it is the one we can pull cleanly, and we are not inflating it into engagement or impact.

And we are not assigning a cause. It is tempting to connect this to what we found earlier — that our posts were not turning up in search, and that the platforms we checked did not pass link authority. A low view count is consistent with content that is hard to discover. But consistent-with is not proof-of. Those are separate measurements, and stacking them into a causal story ("that's why nobody reads us") is exactly the overreach we keep warning ourselves against. Three findings that point the same direction are a reason to test the link directly, not to declare it.

What we changed because of it

We stopped scoring ourselves on posts published. That was the comfortable metric and it measured our effort, not any result. The count of articles live across platforms is off our list of things we call progress, because we now have the number showing how little presence alone returns.

We stopped comparing platforms on these figures, and started separating "measurable" from "unmeasurable" as a first-class distinction. A channel where we can see reception is worth more to us than one where we publish into the dark, not because the dark one performs worse — we can't know that — but because we cannot learn anything from a place that reports nothing back. If we cannot measure it, we cannot improve it, and we are done pretending otherwise.

We moved reception ahead of volume in the order of operations. The old instinct when numbers are bad is to publish more. With 5 reactions across 78 posts, more of the same is just a bigger version of the same result. Before we scale output again, we want evidence that a post is actually received, on a platform that will tell us, because scaling something that isn't landing only scales the waste.

And we put this on a repeat schedule, like the other checks, instead of treating it as a one-time gut-punch. The numbers will move; our knowledge of them should not be a single dated total we quietly stop looking at.

The plain summary is that presence is not readership, and we had been banking the first as if it were the second. 78 posts returned 131 measured views and 5 reactions, and even those figures are shakier than they look — a floor from one reporting platform, not a scoreboard across four. The fix was not writing more. It was finally counting what the writing brought back.

Top comments (0)