Skip to content
Stackposts
Product guide

Facebook Analytics

📖 Documentation: Adding read_insights in Facebook API Settings 🔹 Step 1. Navigate to API Integration Log in to your Stackposts Admin Dashboard. Go to Settings → API Integ...

3 mins read
StackPosts guide

Facebook Analytics

Use this practical guide to complete the task with a clear setup path and an observable result.

Use this guide

  1. Open the related workspace area and confirm the intended account or workspace.
  2. Follow the detailed instructions below and save each change before moving on.
  3. Run a small, observable test so you can confirm the result on the connected service.

Detailed steps

📖 Documentation: Adding read_insights in Facebook API Settings

🔹 Step 1. Navigate to API Integration

  1. Log in to your Stackposts Admin Dashboard.

  2. Go to Settings → API Integration → Facebook.


🔹 Step 2. Add read_insights Permission

  1. In the Facebook Page section, locate the Permissions field.

  2. Add read_insights to the list of permissions.
    Example:

     
    pages_read_engagement,pages_manage_posts,pages_show_list,read_insights
  3. Ensure your Callback URL is correctly set (e.g., https://yourdomain.com/app/facebook/page).


🔹 Step 3. Save Changes

  • Click Save changes to update the Facebook integration settings.


🔹 Step 4. Re-authenticate Facebook Pages

  • Users who have already connected their Facebook Pages will need to reconnect them.

  • During re-authentication, they will see the additional read_insights permission request.


🔹 Step 5. Submit read_insights for Facebook App Review

  1. Go to your Facebook App Dashboard → App Review → Permissions and Features.

  2. Request approval for read_insights.

  3. Provide explanation + screenshots (Stackposts fetching page analytics such as reach, impressions, and engagement).

 

📊 Adding read_insights Permission for Facebook Analytics

To enable Facebook Analytics in Stackposts, your Facebook App must request and be approved for the read_insights permission. This permission allows your app to read metrics, insights, and other analytical data from Pages, Posts, and other Facebook objects.


🔹 Step 1. Go to Facebook App Dashboard

  1. Log in to Meta for Developers.

  2. Select your Facebook App used for Stackposts.

  3. Navigate to App Review → Permissions and Features.


🔹 Step 2. Request read_insights

  1. In the list of permissions, find read_insights.

  2. Click Request.

  3. Fill out the required details:

    • How you will use this permission → Explain that your app uses it to fetch analytics data from Facebook Pages and Posts for users who have connected their accounts in Stackposts.

    • Provide screenshots or video showing:

      • How users connect their Facebook Page in Stackposts.

      • How insights (reach, impressions, engagement) are displayed inside the dashboard.


🔹 Step 3. Provide Test Accounts for Review

  • Add a test account with access to a Facebook Page.

  • Ensure that the reviewer can:

    1. Log in via your Stackposts app.

    2. Connect a Page.

    3. See analytics data (Page reach, Post engagement, etc.) fetched using read_insights.


🔹 Step 4. Update Scopes in Stackposts

In your Stackposts configuration (Facebook integration), make sure you include read_insights when requesting permissions during the login flow. Example scopes:

 
pages_read_engagement, pages_manage_posts, pages_show_list, read_insights

🔹 Step 5. Submit for Review

  • After preparing the explanation and demo, click Submit for Review.

  • Once approved, all Stackposts users can grant this permission when connecting their Facebook Pages, enabling advanced analytics.


⚠️ Important Notes

  • read_insights is a standard permission but still requires review by Meta.

  • Without approval, only Admins/Developers/Testers of your app can use it.

  • Ensure your app’s Privacy Policy and Terms of Service links are valid before submission.

Quick check

  • The save or publish action completes without an error.
  • The visible status, preview, or connected account matches the change.
  • If the result differs, capture the exact message and review the troubleshooting guidance before retrying.
Still need help?

Tell us where you are stuck.

Share the product, the step you reached, and any error shown. Our team can point you in the right direction.