Facebook - June 2026 Insights Deprecation

On 15 June 2026 Meta retired its impression and unique-reach metrics across Facebook Page, Post and Video Insights. This page explains what changed, what Outstand returns now, and how to read the numbers.

What Meta changed

Meta removed the long-standing impression metrics (post_impressions, post_impressions_unique, page_impressions, page_impressions_unique) along with several engagement metrics (page_engaged_users, page_consumptions), and replaced them with a new family of media view metrics.

Two properties of this change matter more than the rename itself:

• It applied to every API version at once. Meta did not gate the removal behind a version bump, so pinning an older Graph API version did not avoid it.
• The Graph API rejects the entire request when one metric name is unrecognised. A single retired metric in a batch does not return partial data - it fails the whole call.

What you should expect to see

• Impressions and reach read lower than before. A media view counts content that was actually rendered on screen; an impression counted content that was delivered. These measure different things, and the new number is smaller for the same content.
• History was not backfilled. A drop across 15 June 2026 in your reporting reflects the change of definition, not a change in your audience. Avoid mixing the old and new values in a single time series.
• The paid/organic split is no longer available as a unique-user metric.

What Outstand does

• Post analytics (Post Analytics API) return impressions and reach from the media-view metrics, plus an engagement_rate calculated against reach.
• Account metrics (Account Metrics API) return impressions, reach and post_engagements for the requested period.
• Unavailable metrics are reported, not faked. When Meta does not return a metric, Outstand sends null rather than 0, so you can tell "nobody saw this" apart from "this could not be measured". The specific metric names that failed are listed in platform_specific.insights_unavailable.
• One failed metric no longer costs you the rest. Outstand requests metrics as a batch and, if the Graph API rejects the batch, retries each metric individually and keeps whatever still works. A future Meta rename costs you that single metric instead of your whole analytics response.

If your metrics are empty

Check these in order:

1. Permissions. Post and Page insights need both pages_read_engagement and read_insights approved on your Meta app. See the Facebook configuration guide.
2. Page role. The user who connected the Page must hold the Analyze task on it. A user with only Editor access can publish through Outstand but cannot read insights.
3. insights_unavailable. If this lists metric names, Meta rejected them - most likely another rename. Contact support@outstand.so with the list and we will update the metric mapping.

References

• Meta - deprecated Page Insights metrics
• Meta - Graph API Insights reference