The fastest way to lose someone's trust in an analytics page is to show them a number that is not real. So Clienzo's analytics follow one rule: if a network does not report it, the cell is blank, and Clienzo says why.
Not every network reports
Of the sixteen networks Clienzo posts to, a good number simply do not give an app per-post numbers:
- Discord webhooks, Slack, Telegram channels and Viber channels do not report views or reactions per message.
- Dribbble's API does not report views or likes on a shot.
- Dailymotion retired per-video view counts from its API this year.
- LinkedIn reports them only through a separate API that needs its own approval.
The networks that do report — Facebook, Instagram, Threads, YouTube, Pinterest, Bluesky, Mastodon, DEV and Tumblr — each report a different mix of views, likes, comments and shares. The table on Clienzo's site lists exactly which.
What I decided not to show
Two popular numbers are missing on purpose: engagement rate and reach. Both need a denominator — followers, impressions — that most networks do not hand to an app for each post. Computing them anyway would mean inventing the denominator.
The bug that ate two thirds of the data
Clienzo measures each post three times: an hour after publishing, after a day, and after a week. For a while the job overwrote the result each time. The one-hour and one-day numbers were measured, saved, and then replaced by the next pass — gone for good, because no network will tell you what a post's numbers were yesterday.
Now every pass is kept separately. That made a new number possible: how much of a post's engagement arrived in its first hour. It only shows once a post has been measured past that first hour; before that, the first hour is the total and the share would always read 100%.
What came after
With history kept, the page could grow up: comparison with the previous period, results per account instead of only per network, a day-and-hour view of when posts do best, and cuts by content type — image, video, text, caption length, with or without a link. The heatmap needs a fair number of measured posts before it means anything; with three posts it is noise.
Next: the review process that decided when Facebook, Instagram and Threads could launch.
Originally published on jonasnguyen.com, where I write about building Clienzo and the next startups.
Top comments (0)