Why Instagram view counts don't match
Instagram can show more views in the app than our API returns. You're not imagining it—this is a known, annoying issue.
Why it happens
Our Instagram endpoints return real-time public Instagram-side play counts. They don't include Facebook views.
When a Reel is also shown on Facebook, the logged-in Instagram app can show the combined Instagram + Facebook total. The public Instagram data can show only the Instagram side. A fresh API response can therefore be lower without being stale.
Here's the Reddit discussion we often share for more context.
An example
In a support check on April 29, 2026, we found:
- Instagram app: about 167,000 views.
- Public Instagram count: 76,648 plays.
- Matching Facebook Reel: about 90,000 views.
76,648 + 90,000 = 166,648—about 167K. The combined count explained the difference in that example. These are the counts from that check, not today's totals.
What you can do
- For Instagram-only counts: use Post/Reel Info with
include_play_count=true. - For Facebook views too: use Facebook Profile Reels and find the same video. Match the caption, video and posting date—not just the creator's name. Once you have a confirmed match, adding the two public counts can help explain the gap.
We don't have a combined-views field or a force-refresh parameter that unlocks the larger number. Public counts also won't always recreate the exact total shown in Instagram's app or Insights. Facebook does not explain every mismatch. Don't assume the difference is a Facebook count without finding the matching Reel.
Still doesn't look right?
Send us the Reel URL, the endpoint you used, the returned count and a screenshot taken around the same time. We'll check the specific example. Please leave your API key out.