To connect Facebook Insights to ChatGPT:
- Sign up free at portermetrics.com and connect your Facebook Insights account with your Facebook account.
- In ChatGPT, click + → Connectors → Manage connectors → Add custom connector, name it Porter, paste
https://mcp.portermetrics.com/mcp, then click Add and authenticate with Google.
That’s it, you’re connected. Porter’s free plan covers up to 3 Facebook Insights Pages with no usage limits on ChatGPT’s free plan. No credit card required.
What makes Porter different:
- 277+ Facebook Insights fields and metrics, across every reporting level in one connection.
- Universal Facebook Insights MCP. Hosted white-label dashboards and client portals, competitor tracking with creative analysis, idea validation with Google Trends and keyword data. Your whole Facebook Insights operation runs from one chat.
Prerequisites
- A Porter Metrics account with your Facebook Insights account connected (free tier is enough to try it end-to-end)
- A ChatGPT account — the free plan works for ChatGPT Web; a Pro subscription is needed for Codex and Desktop MCP features
- Admin or standard access to the Facebook Insights Pages you want to connect
Connect Facebook Insights to ChatGPT with MCP
For this tutorial we’re going with the MCP method. Here’s a quick explainer of what MCP is and why it’s the best path for Facebook Insights.
MCP (Model Context Protocol) is the open standard that lets AI tools like Claude, ChatGPT, Codex and others access and use external APIs — the things that make tools like Facebook Insights work under the hood. Instead of building a custom integration for every AI tool you use, you install one MCP and every compatible AI gets access to the same data.
The full setup takes under 5 minutes and breaks into three moves: connect Facebook Insights to Porter, point ChatGPT at the Porter MCP, and ask your first question.
1. Connect your Facebook Insights data to Porter
Porter sits between Meta’s Graph API and ChatGPT. It handles OAuth, rate limiting, pagination and all the plumbing so ChatGPT only ever sees clean, structured data.
Sign up for Porter. Create a free account at portermetrics.com. The free tier is enough to run this full workflow end-to-end.
Connect your Facebook. In Porter, click Create → pick ChatGPT as the destination → select Facebook Insights as the source → sign in with Facebook to grant access to your Pages.
Select your Pages. Choose the Facebook Insights Pages you want ChatGPT to query. When you select multiple Pages under a single connection, Porter automatically blends their data together so you can query them as one.
Optional: enable automatic BigQuery storage if you’re connecting multiple Pages with large data volumes. This keeps ChatGPT’s responses fast even at scale.
2. Connect the MCP to ChatGPT
Porter’s MCP URL is what you paste into ChatGPT. Once added, ChatGPT can query Facebook Insights data on demand in any conversation.
Go to chatgpt.com and click the + icon in the chat input to open the tools menu.
In the menu that opens, hover over Connectors and click Manage connectors.
In the Connectors panel, click the + button at the top of the list to start adding a new connector.
Pick Add custom connector from the dropdown that appears.
A dialog opens with the name and URL fields. Type Porter in the first field to name the connector.
In the second field, paste https://mcp.portermetrics.com/mcp. Leave the advanced settings alone.
Click Add at the bottom right of the dialog. ChatGPT opens a sign-in window — use the same Google account linked to your Porter workspace and approve access.
Once the authorization finishes, you’ll see Porter’s tools appear in the connectors panel. You’re ready to start asking questions.
For a fuller walkthrough with screenshots at every step, see the Porter MCP tutorial.
3. Start building questions and dashboards
With Porter connected, open a new ChatGPT chat and ask anything about your Facebook Insights in plain English. ChatGPT calls Porter behind the scenes, pulls live data from Meta, and answers with tables, charts, or summaries.
Try one of these to verify the setup is working:
For a full catalogue of copy-paste prompts organized by use case (performance, brand monitoring, creator growth, cross-channel), jump to the prompts section below.
Alternative ways to connect Facebook Insights to ChatGPT
⚠️ Porter MCP is the path we just walked through and the one we recommend for most marketers. It is not the only way to get Facebook Insights data in front of ChatGPT, though. The most common alternatives are Facebook Insights’s direct API, a live Google Sheets bridge or CSV upload, and BigQuery for scale. Each has trade-offs, so pick the one that fits how your team already works.
- 🔌 Facebook Insights’s direct API — Talk to Meta’s Graph API yourself. Maximum control, but you handle auth, rate limits and pagination — and you only get one source. (Meta doesn’t ship an official MCP yet.)
- 📊 Google Sheets — Live Sheet or one-off CSV upload. Auditable, familiar, faster for big exports — but aggregation happens in the Sheet, not the API.
- 🗄️ Google BigQuery — For large Pages or agencies running multi-Page analysis. BigQuery aggregates; ChatGPT only queries pre-built summaries.
Via the Porter Metrics app in the ChatGPT marketplace
If you’d rather not paste a connector URL, install Porter straight from ChatGPT’s app gallery — it’s the same Porter connection behind the scenes, published as an approved ChatGPT app:
- Open the Porter Metrics app page in ChatGPT (or search “Porter Metrics” in the apps gallery).
- Click Connect and sign in with the same account you use in Porter.
- Authorize it and ask your first Facebook Insights question — same live data as the MCP.
The trade-off to know: the marketplace app only updates after each ChatGPT review cycle, while the MCP updates the moment Porter ships. If you want every new tool and data source immediately, use the MCP; if you want the one-click install and don’t mind waiting for new features, the marketplace app is the shortest path — including write actions through your connected Porter account.
Via Facebook Insights’s direct API
If you’re building a product around Facebook Insights — or you’re a developer who’d rather own every layer of the integration — the most direct path is talking to Meta’s Graph API yourself, or — where it exists — Facebook Insights’s own official MCP. Facebook Insights doesn’t ship an official MCP yet, so going direct means writing API calls yourself in Codex or your own scripts. Whichever route you pick, you still follow Meta’s rate limits & quotas. Either way you skip Porter and call Meta from your own code, from Codex, or from Facebook Insights’s own connector.
The trade-off to know. Going direct gives you maximum control and the freshest possible data — every endpoint, every parameter, no abstraction layer in between. But you’re now responsible for OAuth flows, refresh tokens, rate limits, pagination, schema changes, and error retries. And critically, you only get one source. The moment you also want Google Ads, GA4 or Shopify in the same conversation, you’re back to building (or stitching together) more integrations.
When this makes sense: engineering teams that need a single source with full control, products that ship Facebook Insights data as a feature (where you own the integration anyway), or one-off scripts where you don’t mind writing the auth and pagination code yourself. For marketers who want to ask questions in plain English and blend Facebook Insights with the rest of their stack in a single conversation, the Porter MCP path is dramatically less work.
Via Google Sheets (live Sheet or manual CSV)
If your team already lives in Google Sheets — or you want a paper trail before ChatGPT touches anything — feed Facebook Insights into a Sheet, then let ChatGPT read the Sheet. You can automate the Facebook Insights → Sheets pipeline with Porter so it refreshes daily, or do one-off CSV exports from Meta Business Suite for static analysis.
The trade-off to know. With the MCP path, ChatGPT calls Meta’s API directly and Meta does the filtering and aggregation on its side — clean and deterministic. With the Sheets path, ChatGPT aggregates inside the Sheet itself, which can introduce hallucinations on totals, averages, and joins when you have thousands of rows. The upside is speed: for very large date ranges or historical analysis, a pre-built Sheet is dramatically faster than live API calls.
When this makes sense: finance teams that want to review numbers before ChatGPT acts on them, agencies already delivering client reports in Sheets, historical analysis across years of data, or any case where you care more about speed than real-time freshness.
Via Google BigQuery (for scale)
This is the path most people overlook — and it’s the one that saves you when your Facebook Insights Page gets serious. A single large page manager or an agency managing 10+ Pages will hit API rate limits and latency problems querying ChatGPT directly. ChatGPT will literally tell you it’s taking too long or timing out on big pulls.
BigQuery fixes that. You load Facebook Insights data into BigQuery tables on a schedule, then connect BigQuery to ChatGPT — either through a BigQuery MCP or via Codex with SQL queries. Instead of asking ChatGPT to pull raw Facebook Insights data, you let BigQuery aggregate into small, optimized tables, and ChatGPT only queries the summarized output. Scale problem solved.
When this makes sense: enterprise Pages with thousands of posts and millions of impressions, agencies running multi-Page analysis across 10+ clients, or any team already using BigQuery as a data warehouse. Porter loads Facebook Insights (and 25+ other sources) directly into BigQuery so you don’t have to build your own ETL.
Connecting Facebook Insights to Codex
Most marketers lump ChatGPT and Codex together and miss the biggest advantage of the entire MCP ecosystem. They’re not the same tool — and the difference matters enormously once you start working with Facebook Insights data seriously.
ChatGPT is a chat interface. You ask a question, ChatGPT pulls live data through the MCP, answers, maybe builds a quick dashboard inside the conversation. Great for one-off analysis. The problem: everything is ephemeral. Want to refresh the dashboard tomorrow? You regenerate it from scratch. Want the same report every Monday? You re-ask the question every Monday.
Codex is ChatGPT running inside your computer’s terminal. Because it has access to your filesystem, runtime, and other developer tools, it doesn’t just answer questions — it can build real software. Persistent scripts, scheduled routines, HTML apps, internal dashboards, integrations that run 24/7 without your input. Once it’s connected to Porter’s MCP for Facebook Insights, a whole category of work becomes possible.
What Codex unlocks that ChatGPT alone cannot
This is where the MCP ecosystem pays off most. Because Codex can combine Porter’s MCP with other MCPs — Firecrawl for web scraping, Airtable for structured data, Notion for wikis, Vercel for deployment, Slack and Gmail for delivery — you’re no longer querying data. You’re building tools.
Feed Codex your Facebook Insights targets and goals — engagement rate targets, follower growth goals, content performance thresholds — and ask it to generate a custom engagement and growth dashboard for each client. It builds the HTML, pulls live data, deploys to a URL. No Data Studio embed to break when the vendor changes pricing, no template constraints. The dashboard updates automatically because it queries Porter’s MCP on every page load.
Best for:agencies that want white-label client dashboards without Looker or Data Studio dependencies.
Combine your own Facebook Insights performance from Porter with competitor Pages and public post performance from Facebook Public Data scraped via Firecrawl. Codex stitches both into a weekly competitive intelligence report — your numbers next to their content themes and posting frequency, with an LLM summary on top of what changed week over week. Runs on cron, lands in your inbox every Monday morning.
Best for:in-house teams that need market context, not just internal numbers.
Use Airtable or Notion as the schema, Porter as the data source. Codex keeps every page populated with current Page total reach, Post engagements, and Page new followers for every Page — no stale screenshots, no copy-paste from Excel. New hires read one wiki entry and have full context on a client’s account.
Best for:agencies and ops teams onboarding analysts or rotating account managers frequently.
A Codex routine on cron pulls Facebook Insights via Porter, evaluates thresholds — Page engagement rate drops below 2%, daily new unfollows spike 2× the trailing average — and pushes Slack or Gmail alerts the moment something crosses the line. You stop checking dashboards reactively; the dashboard checks itself and tells you when to look.
Best for:any team that’s ever discovered a problem 48 hours too late because nobody opened the report.
Bottom line: ChatGPT is for quick questions and ad-hoc dashboards. Codex is for building apps, live dashboards, alerts, and actual tools — anything you want to run on its own without re-asking. Same Porter MCP URL works in both, so you don’t pick once and lock in.
Use cases: what you can actually do once Facebook Insights is connected to ChatGPT
Getting the connection right is half the battle. The real value shows up in what you do next. Here are the use cases Porter users build around their Facebook Insights data — from simple Q&A to full client-facing workflows.
1. Chat and ask questions directly
The simplest use case — and still the one 80% of marketers start with. Open ChatGPT, ask a question, get an answer grounded in live data.
It’s the fastest way to replace a daily Meta Business Suite check-in. But chat is table stakes — the interesting use cases come next.
2. Blend Facebook Insights with your revenue data (Meta Ads, Shopify, HubSpot)
This is where a 360° view gets real. When you connect Facebook Insights and your revenue source (Meta Ads for paid social amplification, Shopify for e-commerce conversion, HubSpot CRM for lead nurturing), ChatGPT can map Page posts and content to actual sales and lead conversions — using post URLs, campaign names, and timestamps — and give you attribution that no platform-side number can.
ChatGPT handles the post URLs, campaign names, and timestamps mapping and joins. You get a client-ready attribution report that no single platform can generate on its own.
3. Automated alerts and notifications on Slack or Gmail
With Codex you can turn Facebook Insights monitoring into a routine that runs on its own. Hook Porter’s MCP (for the data) together with a Slack or Gmail MCP (for delivery), then write a Codex scheduled task that pulls performance every morning and pings you only when something actually needs attention.
No dashboards, no daily check-ins. The report comes to you — and only when it matters.
4. Client-ready presentations with live data (Gamma, HTML, PDF)
A common agency pain: you send clients a Data Studio embed, Looker breaks, the client panics — and you spend an hour explaining a broken dashboard. With ChatGPT you can build the presentation itself — as a Gamma deck, a custom HTML page, or a PDF — populated with live numbers each time.
The presentation becomes a delivery artifact you send to the client, not a dashboard that depends on another tool staying up. No broken iframe, no login prompts, just the content.
Facebook Insights fields and metrics you can query with ChatGPT
Before you start writing prompts, it helps to know what data is actually available. Porter MCP gives ChatGPT access to 277 Facebook Insights fields and metrics across every reporting level (Page-level, Post-level, Video, Reels, Reviews), plus breakdowns by audience demographics, geography, time of day, and content type. And the same MCP URL also unlocks 25+ other sources — so ChatGPT can blend Facebook Insights with Google Ads, GA4, Shopify, HubSpot and more in a single prompt.
Prompts you can copy-paste today
…organized by job: Agencies, Brand teams, Creators & DTC, Cross-channel.
1. Agencies
For social media managers and agency account leads managing multiple client Pages.
2. Brand teams
For in-house brand and community managers monitoring sentiment and health.
3. Creators & DTC
For content creators, DTC brands, and video monetizers tracking Reels and ad-break earnings.
4. Cross-channel
For teams blending Facebook Insights with the rest of their marketing stack.
Limits, auth, and best practices for Facebook Insights via ChatGPT
rate limit exceeded errors around 10 AM every day. Turns out we were hitting the 200 calls/user/hour cap because we weren’t batching requests.” — u/marketingops_dude, Reddit r/facebook, 2024-08-14″This is the classic Facebook Insights scaling trap: the API appears generous until you multiply it across many pages or pull granular breakdowns. The cost isn’t a ban—it’s a silent data pipeline failure that leaves your dashboards stale by midday. Marketing teams with 20+ managed pages or agencies running multi-client reporting are most vulnerable.
Meta’s rate limiting for the Facebook Insights API is quota-based, not tool-based. Meta doesn’t ban accounts because you used ChatGPT or an MCP. It throttles because of how the API was used: exceeding the 200 calls per user per hour limit, making unbatched individual requests instead of using batching, or requesting excessive breakdowns that multiply call volume. Read-only access within quota is safe. Bursty traffic, unbatched multi-page requests, and ignoring pagination is not.
The two ways to burn through your Facebook Insights quota
After reviewing official docs and community threads, two patterns come up again and again.
1. Unbatched multi-page requests. Pulling metrics for each Page individually instead of using the Facebook Graph API batching endpoint turns 1 call into 50. This burns through the 200 calls/user/hour quota rapidly and triggers rate limit exceeded errors that halt data collection for the remainder of the hour. Source: Meta Graph API Rate Limiting docs — developers.facebook.com/docs/graph-api/overview/rate-limiting. Use batch requests or the /insights edge with proper pagination.
2. Ignoring pagination on large datasets. Facebook Insights paginates results when requesting data with many breakdowns (e.g., post-level metrics by country/age/gender). Failing to follow paging.next URLs and instead re-requesting the full dataset repeatedly multiplies call volume and hits rate limits unnecessarily. Source: Meta Graph API Pagination docs — developers.facebook.com/docs/graph-api/results. Implement cursor-based pagination in your request logic.
3. Requesting excessive granularity without purpose. Asking for post-level insights with full demographic breakdowns for historical analysis generates massive call volumes. Each additional breakdown dimension multiplies the number of API calls required. Source: Meta Insights API Best Practices — developers.facebook.com/docs/graph-api/insights-api. Request only the metrics and dimensions you actually need for your analysis.
Both behaviors trigger rate throttling. If you want to use ChatGPT for Facebook Insights safely, stay within quota, batch your requests, and paginate properly.
The 5-rule scaling protocol
Based on Facebook Insights’s documented rate limits and quotas and the behaviors that have actually caused throttling — not guesswork:
-
Batch your requests. The Facebook Graph API supports batching up to 50 requests per call. Use this to stay well under the 200 calls/user/hour limit. Source: Meta Graph API Batch Requests docs — developers.facebook.com/docs/graph-api/batch-requests. Ignoring this burns quota and leaves you without data for the rest of the hour.
-
Respect the 200 calls/user/hour hard limit. This is the documented rate limit for Insights API access. Design your data pulls to stay below 80% of this threshold to leave headroom for retries. Source: Meta Graph API Rate Limiting docs — developers.facebook.com/docs/graph-api/overview/rate-limiting. Porter MCP enforces this automatically with per-account request queuing.
-
Use pagination cursors, not offset-based retry loops. Facebook Insights uses cursor-based pagination. Follow the
paging.nextURLs exactly as provided rather than constructing your own offset parameters. Source: Meta Graph API Pagination docs — developers.facebook.com/docs/graph-api/results. Re-requesting from offset zero repeatedly is a fast path to quota exhaustion. -
Request only the metrics you need. The Insights API charges calls per metric requested. Pulling 50+ metrics when you only need 5 multiplies your call volume 10x with no benefit. Source: Meta Insights API Reference — developers.facebook.com/docs/graph-api/reference/insights. Porter MCP defaults to essential metrics only, with opt-in for extended sets.
-
Cache and respect data freshness windows. Facebook Insights data has a known freshness delay of 5-20 minutes for Page metrics and up to several hours for some post-level metrics. Polling more frequently than every 15 minutes wastes quota without improving data quality. Source: Meta Insights API Best Practices — developers.facebook.com/docs/graph-api/insights-api. Porter MCP caches responses and respects platform freshness windows.
What Porter MCP does differently: it enforces these rate limits and safeguards at the platform level. Porter batches requests automatically using the Graph API batch endpoint, queues requests per-account to stay under the 200 calls/user/hour threshold, implements cursor-based pagination following, and caches responses to respect Facebook’s data freshness windows. That’s the behavior Meta’s automated systems handle gracefully—they see well-spaced, batched, read-only requests well within quota, which is exactly what their rate limiting is designed to allow.
Frequently asked questions
Ready to chat with your Facebook Insights?
Open ChatGPT, add the Porter connector, and ask your first question. If you don’t have Porter yet, start a free trial and connect your Facebook Insights account — you’ll be chatting with your campaigns in under five minutes.
rocket_launchStart free Porter trialopen_in_newOpen ChatGPT