Starter
For freelancers and small teams.
Billed monthly · cancel anytime
Used by the world's leading companies
















Available metrics
Available dimensions





What our customers say about us.
After three years of use, Catchr has become essential for both our teams and our clients. So far, it has been our best solution for compiling and analyzing data from different advertising platforms. It’s easy to set up, and the customer service is responsive and excellent.

With Catchr’s automated API, we can finally collect and centralize all advertising data, connect it with booking information, and calculate the real ROAS for our restaurant clients. It gives them full visibility, more autonomy, and the ability to optimize campaigns to maximize ROI.
The solution is a real game changer, providing optimal time savings for our data reporting. The major strength of the solution is their highly responsive and professional support.
Connect Facebook Public Data in Catchr through Facebook authorization and enter the Page IDs you want to report on. Select the configured Page in your Catchr data source, then connect it to Looker Studio. Start with Page Name and a small table of recent post links and engagement counts to check access and coverage. Use the business Page identifier rather than a personal-profile name or an advertising account ID.
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.
Our team is always here to answer any questions you may have about our data connector.