What your posts did last week, by the hour
Views, likes, comments, shares and saves per post, and followers per account, read every hour and kept. Why a kept series beats a counter, what the Trends tab shows, and how to ask your assistant for the numbers.
A platform’s own analytics show you a number: this post has 12,400 views. What it does not show is that 9,000 of them arrived on Tuesday between six and nine in the evening, or that your other account’s post from the same day did a quarter of that. ViewPrinter keeps the series.
Read every hour, and kept
Once an hour, every post you published and every account you connected is read: views, likes, comments, shares and saves per post, and followers, following, likes and posts per account. Each reading is kept rather than overwritten, so “up 1,200 this week” is a real difference between two readings, not a counter that only knows today’s number. An account nobody has measured yet shows no numbers at all, rather than zeroes.
Where to see it
- The Trends tab on the posts page: what the posts you filter to gained each day, over 7, 30 or 90 days, against the same window before, and the posts that gained the most for each counter.
- Every post: its counters and how they moved over the last day or week, for each account it went to.
- The accounts page: followers and engagement per account, with the change over the window you pick.
- Your assistant: the same numbers, over MCP. Ask how last week’s posts did and it reads them rather than guessing.
What to do with it
The series is what makes comparisons honest. Two posts with the same hook on two accounts, read at the same hour, tell you which audience the hook was for. A post that gained most of its views on the second day tells you the platform kept showing it. And when you want the next one to land, timing is a separate question: the best time to post on TikTok.
Common questions
Then post it
Say it once, post it everywhere
Say what to post and when — it goes out on time to every account, without you opening a tab.
Paste this into your client
{
"mcpServers": {
"viewprinter": {
"type": "http",
"url": "https://viewprinter.tech/api/mcp"
}
}
}