This article outlines recommendations and notes certain limitations imposed by the data source API, which you may need to consider when building your queries.
If you are connecting to this data source, please follow the instructions in our <connection guide>, and the available fields for this connector are listed in the <metrics and dimensions documentation>.
Request limits and recommended refresh rate
Request limit: 4,800 requests per engaged user per day.
Recommended refresh window: 5 days. The Insights API has a delay between 0 and 4 days.
Historical range
With the Facebook Insights data source connector, organic data isn’t available before October 2017 (and possibly earlier, as it may be a rolling window).
Insights only retains the last 2 years of data; older data is subject to removal.
Accounts in Facebook Insights
In the Facebook Insights connector, each Page is considered a separate account within the connection.
Your subscription determines the number of data source accounts you can use simultaneously.
Things to consider
Unsupported posts or page types
Donation/Fundraiser posts: This part of Meta’s API is still in closed beta. Supermetrics will not be able to access this until Meta opens this in their API for all users.
Page Events: Meta has locked down this part of the API - There is no option for 3rd parties to request access for this.
Grey accounts: Grey accounts are accounts that are Page accounts specifically. You will need to create a personal user account and give access to your page via that account to log into Supermetrics.
Dark Posts: Fetching data on posts that are not published to a timeline but used as promoted posts/ads is not currently supported.
Boosted Posts: Boosted posts are supported in the Facebook Ads connector but not available in our Facebook Insights data source connector.
Global Brand child pages: We do not currently support any special features for Global Brand pages; they should be fetchable like any other page and require the same access as a normal page. Please note that Meta’s New Page Experience will not support these pages.
Demographic fields
Queries with demographic fields like Age, Gender, City… etc, must be split by a data dimension, such as date, month, or year, for example. Without a date dimension, Meta’s API will return all zeros for the first row of results.
When splitting Total Reach with gender or age demographics, you will need to include either the Gender & Age or both Gender and Age as separate dimensions. Due to this being a unique metric, using only Age or only Gender will return an error.
Meta’s API does not support splitting Page followers by any demographic fields.
Messaging insights
Due to privacy laws in Japan and the EU, messaging-related insights may be unavailable for messages delivered to or from people or businesses based in Europe and/or Japan.
Maximum post limit
Meta’s API will return approximately 600 ranked, published posts per year; this is a limitation of the API. Learn more about Meta’s API limitations here. If your query is likely to include more than 600 posts, it would be better to split your query into smaller data ranges.
Reels and Posts
Meta’s API treats Reels as a video and not as a type of post. This means that data on reels must be fetched separately from other posts. Queries for data on reels may only contain Video dimensions and Reels and video metrics only.