How it works
Three steps, one narrow job: take a video you published, ask the platform that hosts it what the real numbers are, and show you the answer without rounding it.
The three steps
- 1Connect the account you publish from.
You are sent to the platform's own login screen — TikTok's, Instagram's, Facebook's or Google's — where you approve read-only access. BountyTN never sees a password, because you never type one into BountyTN. The platform hands back an access token, and that token is the whole of BountyTN's access to your account.
It asks for the narrowest scopes that will do the job: enough to know which account you are, and enough to list the videos published on it. Nothing that would let it post, change a setting or read a message.
- 2Paste a link to one of your videos.
Any normal post URL works — a TikTok video link, an Instagram Reel, a Facebook Reel, a YouTube video or Short. Connected platforms also list your recent uploads, so you can pick one from the list instead of copying a link at all.
- 3Read the exact counts.
Views, likes, comments and shares, as integers — plus the caption and publish time. Every reading also tells you which account it was taken with, whether ownership was confirmed, and whether any figure came back rounded rather than exact. You always know how much to trust the number in front of you.
Open the app and connect a platform
Why “exact” is the whole point
Public pages round. A video sitting at 6,325,200 views is shown to the world as “6.3M”, and “1.2M views” could be anything from 1,150,000 to 1,249,999 — a span of a hundred thousand views. Some platforms go further and serve no view count at all to a visitor who is not signed in.
That vagueness is harmless when you are browsing and useless when you are reporting a campaign result, invoicing against a deliverable, or checking whether a video is still climbing. Reading through the platform's API, with the authorisation of the account that owns the video, returns the integer instead of the display figure.
| The same Reel, the same moment | Views | Likes |
|---|---|---|
| What a public page shows a signed-out visitor | — none served — | 29,000 |
| What the API returns for the account that owns it | 6,325,200 | 28,862 |
A real reading taken during development. The rounded figure was not merely imprecise — it was 138 likes off, and the view count was absent entirely.
Ownership is checked, not assumed
BountyTN is built for reading your own numbers, and it enforces that rather than trusting it. Before any figure is shown, the post you asked about is compared against the account you connected — by owner id where the platform provides one, or by using an endpoint that only ever returns your own posts.
If the post is not yours, you get a refusal that names the owner it found and withholds every metric. Not a partial answer, not a rounded consolation figure — nothing. Each reading also records the basis on which ownership was decided, so a number can always be traced back to the account and the moment it came from.
This is a design constraint rather than a setting. There is no mode that turns it off, and attempting to work around it breaches the Terms of Service.
What a reading records
A number with no provenance is a rumour. Each reading is stored with everything needed to check it later:
- the video's id and URL, its caption and its publish time;
- the view, like, comment and share counts as the platform reported them;
- the moment of the reading, and which connected account it was taken with;
- whether ownership was confirmed, and on what basis;
- which figures, if any, came back rounded rather than exact — per metric, because one reading can legitimately mix the two;
- the raw response the platform sent, kept as the record of what was actually said and when.
You can have all of it deleted at any time. See Deleting your data.
Where the numbers come from, and what can go wrong
BountyTN reports what the platform returned. It does not compute, estimate or adjust anything, and it cannot make a platform's own numbers correct. Two consequences worth knowing:
- Counters are live. Two readings minutes apart will legitimately differ. One Reel read ten minutes apart during development moved from 6,281,208 to 6,325,200 — that is the counter working, not the tool failing.
- Some content will not yield an exact figure. What a platform will report is set by that platform, and it varies by platform and sometimes by post. When a figure comes back rounded, the app says so rather than quietly presenting it as exact.