Facebook reach shows N/A instead of a false 0
- 2 fixed
Meta retired Facebook post reach in June 2026 and its replacement metric returns no data. Analytics now says so instead of showing 0 everywhere.
Fixed
- Facebook reach showed 0 on every post - Meta retired the Facebook post reach metric on June 15, 2026. The replacement metric Meta documents is accepted by the API but returns 0 for every Page post, while views and clicks on the same posts keep counting. OmniSocials stored that 0 as a real number, so the Reach column, the Reach card and the channel totals read 0 for Facebook. They now read N/A with the reason on hover, the same as X, which has never had a reach metric. The Reach card and the channel total also show N/A when every selected channel lacks the metric, instead of a summed 0. Reach still counts for Instagram and LinkedIn, and the moment Meta starts populating the metric the Facebook numbers appear again without any change on your side.
- API, MCP and CLI -
reachis now absent (never 0) in Facebook post analytics. A Facebook row collected before this release may still carryreach: 0until its next collection; the API drops it, so treat a missing key as "not reported".




