Did this affect our reach?
https://www.facebook.com/business/news/page-insights-bug
Page Insights Bug
We wanted to let Page owners know of a bug that affected all Pages from October 4-14 that has now been fixed. During this period, the bug prevented us from reporting on organic engagement counts—reactions, shares, comments—in Page Insights.
As a result, while people continued to engage with Pages and posts during this time, Page owners may have noticed lower-than-usual Page and post engagement counts when reviewing their Page Insights for this time period. This also affected all post engagement-related metrics in the Pages Insights APIs.
This bug did not affect the count of reactions featured on posts that were promoted/paid, nor did it affect how ads were delivered or billed. The impact of this bug was limited to the reaction counts reported in Page Insights specifically—Page owners for this period could still see the right counts on specific posts.
We apologize for the inconvenience this may have caused. We now understand the root cause of the bug and can help prevent this issue from happening in the future.
https://www.facebook.com/business/news/page-insights-bug
Page Insights Bug
We wanted to let Page owners know of a bug that affected all Pages from October 4-14 that has now been fixed. During this period, the bug prevented us from reporting on organic engagement counts—reactions, shares, comments—in Page Insights.
As a result, while people continued to engage with Pages and posts during this time, Page owners may have noticed lower-than-usual Page and post engagement counts when reviewing their Page Insights for this time period. This also affected all post engagement-related metrics in the Pages Insights APIs.
This bug did not affect the count of reactions featured on posts that were promoted/paid, nor did it affect how ads were delivered or billed. The impact of this bug was limited to the reaction counts reported in Page Insights specifically—Page owners for this period could still see the right counts on specific posts.
We apologize for the inconvenience this may have caused. We now understand the root cause of the bug and can help prevent this issue from happening in the future.
