Why your data in Buffer Insights might look different from native analytics

This guide aims to outline the reasons why the data within your Buffer Insights dashboard may differ from the data you see in the native analytics. This article explains the most common causes and what to do about each.

We can only pull so much history when you connect

When you connect a channel, Buffer backfills as much historical data as that network's API allows. How far back depends entirely on the platform. Some networks give us up to two years; others give us only today.

This is what you're seeing when Insights shows "No historical data" for a period. It means data for that time range wasn't available to pull when you connected.

Network	History backfilled on connect	Metrics included
YouTube	~24 months (analytics permission required — see note below)	Views, likes, shares, followers
LinkedIn Page	~12 months	Followers, reach, views
LinkedIn Profile	Up to ~12 months	Followers, reach, impressions, views
Facebook Pages	90 days	Reach, views, followers
Pinterest	90 days	Impressions, views (followers = today only)
Instagram (Instagram Login)	50 posts	Views, reach, followers
Threads	60 days	Views, likes, replies, reposts, quotes (followers = today only)
TikTok	60 days	Followers, views, likes, reach
Instagram (Facebook Login)	30 days	Views, reach, followers
X / Twitter	Today only	Followers
Mastodon	Today only	Followers
Bluesky	Today only	Followers
Google Business Profile	Not supported	—

:::info Insights data is collected in daily batches and can take up to 24 hours to appear after connecting. :::

A few network-specific things to know:

• YouTube — Buffer needs your YouTube Analytics permission to backfill history. If you didn't grant it when connecting, you'll only see today's data going forward. To fix this, disconnect and reconnect your channel and accept all permissions when prompted.
• Instagram — How much history you see depends on how you connected. Instagram Login gives you 50 posts; Facebook Login gives you 30 days. Two people managing the same account may see different amounts of history depending on their connection method. Like Facebook, Instagram reach and views can occasionally show a gap instead of a number if Meta returns a temporary error. See Missing data isn't the same as zero below.
• Facebook Pages — Pages with fewer than roughly 100 likes will only see today's follower count. Meta doesn't return historical insights for small Pages. Meta also occasionally returns temporary errors when we request daily reach and views. We retry automatically; if a day still can't be collected, you'll see a gap in the chart rather than a zero. See Missing data isn't the same as zero below.
• Pinterest — The 90-day window covers impressions and views. Follower count is today-only.
• Threads — Followers and demographics are today-only, and only available with a linked Instagram account that has 100+ followers.
• X / Twitter, Mastodon, and Bluesky — These networks only expose a current follower count through their APIs. Buffer records one data point when you connect and builds history going forward.
• Google Business Profile — Google doesn't provide an analytics API, so no channel-level analytics are available in Insights.

Some channels collect data in intervals, not daily

Even after you've connected, some channels don't collect data every single day. This can create gaps for specific dates even within your normal data range.

This is what you're seeing when Insights shows "Missing data" for a specific date. It doesn't mean something went wrong. It means Buffer hasn't collected a data point for that exact day yet, or the network doesn't provide data at that frequency.

For example, Bluesky data is collected approximately every 10 days. TikTok and LinkedIn often have a 24- to 48-hour lag on recent posts. When you hover on a data point where the most recent data is older than today, you'll see an "as of [date]" label showing when the data was last collected.

Missing data isn't the same as zero

Buffer collects Insights data from each network on a regular schedule. If a network returns a temporary error while we're collecting a day's data, we retry automatically. If those retries also fail, we leave that day's data missing rather than storing it as zero.

This is why you might see a gap in a chart instead of a data point. A gap means we couldn't collect that day's data, not that your content got zero reach or views. The real number is still available on the native platform.

A genuine zero (showing on both Buffer and the native platform) means your content really didn't get any reach that day. A gap on Buffer next to a non-zero number is, by default, a collection issue, not a performance issue.

This mainly affects reach and views on Facebook and Instagram, where Meta occasionally returns temporary errors on its insights endpoints.

Buffer lost access to your analytics permissions

Each social network requires specific permissions for Buffer to read your analytics. If those permissions are removed or expire, Buffer can't collect new data for that channel, and a gap appears in your Insights charts.

If this happens, Insights will show a banner on the affected channel with the date data collection stopped and the permissions that need to be restored. Your publishing and other features may continue to work normally, since they rely on different permissions.

To restore data collection:

1. Click your profile avatar in the bottom left and choose Channels
2. Click the three-dot menu next to the affected channel
3. Click Refresh Connection

For a full walkthrough, see Refreshing a channel in Buffer.

:::warning Important: If you’re refreshing a Meta account (Facebook or Instagram): When you see the permissions screen, accept all permissions as they appear. Do not click "Edit" to customize what you're granting. Doing so can accidentally remove access Buffer needs to collect your analytics.

If you're having any connection issue, always use Refresh Connection rather than disconnecting. Fully disconnecting a channel permanently deletes all of its associated analytics data. If you reconnect later, Buffer will backfill based on the windows in the table above, but data from before the disconnection can't be recovered. :::

Metrics are sometimes calculated differently

Even when Buffer has complete data for a channel, some numbers may still differ from what you see natively. This is because platforms calculate certain metrics differently from how Buffer does.

For example, X/Twitter's native analytics counts engagement differently from Buffer's (Buffer counts likes, replies, reposts, quotes, link clicks, and profile clicks; X/Twitter includes additional interactions such as app opens and hashtag clicks).

Another example: The Summary area of Insights in Buffer totals up the lifetime stats of posts that were published within the date range (Buffer-published only), while LinkedIn native sums impressions that occur within the date range across all Page content.

These differences are expected and don't indicate missing or incorrect data.

:::info Note for LinkedIn profiles*:* Reshare data isn't available at a reliable level of accuracy for LinkedIn profile posts, so Buffer uses (reactions + comments) / impressions for the engagement rate on those posts. LinkedIn Page posts are unaffected — they use the engagement rate LinkedIn itself reports, which includes shares. :::

:::info Still seeing something unexpected? Reach us at hello@buffer.com and our team will take a look. :::