· 5 min read
A 15-minute weekly review of your Threads stats
What to look at in your Threads stats each week, in what order, and what to change. Five steps and a notes template that fit in about 15 minutes.
Govir Team · How we write

A weekly Threads review takes about a quarter of an hour if you keep it to one question: what deserves more posts, and what should stop? Look at the same few numbers in the same order every week, write down one finding and one change, and close the tab. Everything else in your stats is optional.
This guide gives the order to look in, what each step is for, and a notes template. For the formulas behind engagement rate, use the engagement rate calculator instead of re-deriving them here.
What to have open before you start
You need two things: a list of last week's posts with their numbers, and last week's notes. The Threads app has insights of its own: on mobile, tap the icon at the top left of your profile; on the web, open the menu at the bottom left or go to threads.com/insights (Threads, on insights).
In Govir, open Analytics → Posts and choose 7 days: every post of the week is listed with its views, likes, replies, reposts and engagement rate, and a click on a column sorts by it (Analytics in Govir). The numbers are what each post gained in that period, so an older post doesn't win just by being older. On Pro, the Monday email brings last week's views, followers and top posts to your inbox, and Download PDF keeps the week as a report to file next to your notes.
Pick a fixed day and time, and compare posts that have been live for about the same time. A post keeps collecting views after the first day, so judging Monday's post on Monday evening against Friday's post on Saturday is unfair to Friday.
The review in five steps
Give each step a fixed share of the time. If a step runs over, skip ahead; a rough answer every week beats a perfect one once a month.
1. Check the account, not the posts (2 minutes)
Look at followers gained or lost and profile views for the week. This is the context for everything else. In Govir, both are on Analytics → Audience. A quiet week for followers with strong posts points at the profile or the call to action; a strong week with weak posts usually means one post travelled far.
2. Sort last week's posts by one metric (3 minutes)
Choose a metric and keep it for months. Views tell you what reached people; replies tell you what started a conversation. Sort the week's posts by it and mark the top one and the bottom one. Ignore the middle.
If you want a rate rather than a raw count, use the same formula every time, as explained on the engagement rate calculator page.
3. Read the top and the bottom post (4 minutes)
Open both and ask the same four questions:
- What did the first line promise? (See writing hooks that stop the scroll.)
- What format was it: a single post, a thread, an image, a poll?
- What topic was it about?
- When did it go out?
Write one sentence per post. Do not try to explain the difference with a single cause; you are collecting hints, not proofs.
4. Read the replies (3 minutes)
Replies are the part of your stats that numbers cannot show. Scan the replies on your top post for questions you could answer with a new post, and for objections you could address. A recurring question is a ready-made topic for next week. In Govir, Inbox gathers the replies to all your posts in one list (Inbox).
5. Decide one thing to repeat and one thing to change (3 minutes)
End with exactly two decisions:
- Repeat: one pattern from the top post to use again, such as its format or the shape of its opening.
- Change: one thing from the bottom post to try differently, such as a different first line or a different time.
Two decisions are enough to test properly. Five at once leave you unable to tell what worked.
A notes template
Copy this into a note and fill it in every week. The brackets show where your own numbers go; write down the date you measured them.
Illustrative example (a template written for this article, not a real review):
Week of [date] · Measured on [date] Followers: [start] → [end] · Profile views: [number] Metric used for sorting: [views / replies] Top post: [first line] · [format] · [topic] · [time] · [your number] Bottom post: [first line] · [format] · [topic] · [time] · [your number] Question from replies: [text] Repeat: [one thing] Change: [one thing] Check next week: [did the change help?]
The last line is what turns a pile of notes into a loop: next week's first job is to read it.
Mistakes that waste the review
| Mistake | Why it hurts | Instead |
|---|---|---|
| Comparing a young post with an old one | The young one has had less time to collect views | Compare posts of the same age |
| Changing the metric every week | You cannot see a trend | Keep one metric for a few months |
| Reading one post as a rule | One result can be luck | Wait for the pattern to show up in several weeks of notes |
| Counting your own replies | They inflate interaction counts | Count only other people's replies |
| Checking daily | Daily numbers swing and tempt you into changes | Review once a week, change one thing |
Where the review leads
Once you have several weeks of notes, the same pattern should show up in your top posts. Use it for the next steps: decide whether to adjust how often you post, or choose a thread structure for the formats that keep winning. When the notes start to repeat themselves, Govir's Analytics → Content and Timing tabs (on Pro) show which formats, lengths and hours work best for you over a longer period.
Questions
How often should you check Threads analytics? Once a week is enough for decisions. Looking more often is fine for curiosity, but change your plan only at the weekly review.
Which metric matters most on Threads? There is no single right one. Views show reach and replies show conversation; pick the one that matches your goal and stay with it.
How many posts do you need for a useful review? Enough that the top and bottom posts differ clearly. With very few posts, read the replies and the content instead of the numbers.
What if every post looks the same? Change one variable on purpose, such as the format or the first line, and compare the next week against the notes.
Sources
- Threads, post by @threads, "To access Threads insights, tap the icon at the top left of your profile on mobile. On web, click the menu at the bottom left or visit www.threads.com/insights." https://www.threads.com/@threads/post/DMavCS_AMq8 (accessed 2026-10-12).


