Connect Facebook Public Data to Power BI

Authorize Facebook Public Data in Catchr and enter the business Page IDs to monitor. In Catchr’s Power BI query builder, select Page Name, recent post links and available engagement counters and preview a short extraction. Import the generated URL through Get data > Web in Power BI Desktop. Check the returned rows before building measures, keeping Page and post IDs, with missing fields kept distinct from zero clear in the model.

Public Page reporting can support competitor comparisons when Meta permits the application to retrieve the requested Page data. A Page being visible in a browser does not guarantee that every field is available through the API. Meta's Page Public Content Access and Page Public Metadata Access requirements govern access alongside other permissions. Test the specific Pages and fields you need before building a recurring comparison; the connection does not provide private Page insights.

Facebook Public Data focuses on available Page information and public post engagement, such as reactions, comments, and shares. It does not expose private reach, impression, audience-demographic, or conversion fields in its current catalog. Use Facebook Pages for supported insights on Pages you manage, and Facebook Ads for campaign spend and advertising outcomes. Keep those reporting scopes separate when comparing results.

The selected dates filter posts by their creation time. Reaction, comment, and share counts are the values returned for those posts when the data is retrieved, not a history of when each interaction occurred. An older post can gain engagement after the selected period and change the report. Label the chart as engagement on posts published during the period, rather than interactions received exclusively during those dates.

Total Reactions already includes likes, so do not add Likes Count to Reactions Count as if they were separate actions. For a simple interaction total, combine reactions, comments, and shares using consistent availability and scope. Compare that total per post alongside posting volume and publication age. These are actions, not unique people, and a rate based on current followers is not the same as engagement divided by reach.

Followers Count and Fan Count are current Page values, not daily histories. Followers and Page likes also describe different relationships, so use consistent fields when comparing Pages. Changing a report's date range cannot reconstruct a past follower count. Store dated snapshots separately if you need growth over time, and avoid summing a Page-level counter repeated across multiple post rows.

Check the Page ID, authorization, requested dates, and whether Meta makes the selected field available to the application. Fields can be unavailable even when the Page itself is accessible, and an unavailable value should not be treated as zero. Compare the same post by its permalink, start with a small field set, and refresh before investigating further. Public-data reporting does not guarantee a complete archive of removed, restricted, or historically unavailable posts.