Destinations
Data sources
AI insights
About us
Careers
Security
Customer reviews
Contact us
Affiliate program
Solution partners
Template gallery
Looker Studio templates
Power BI templates
Excel templates
Google Sheets templates
Tableau templates
Facebook Ads templates
Google Ads templates
Data fields & Metrics
AI prompt library & Guides
Product documentation
API documentation
Case studies
Blog
Data models
Windsor vs Supermetrics
Windsor vs Funnel.io
Windsor vs Fivetran
Windsor vs Rivery
Windsor vs Portermetrics
Windsor vs Coupler.ioConnect Facebook Ads (Meta Ads) to Claude
Automatically sync your Facebook Ads data to Claude using the Windsor.ai connector.
Analyze your Facebook Ads data, including spend, ROAS, CPA, CTR, and conversions in seconds. Create campaigns and ad sets, pause or enable them, and adjust budgets directly from Claude.
Forget CSVs. Stop copy/paste. Connect data in minutes. No code required.
Free forever plan
Which one do I need?
All four methods below get your Facebook Ads (Meta Ads) data in front of Claude. They differ in freshness, setup effort, and whether Claude can also act on your campaigns rather than just read them.
To help you navigate quicker, here’s what each method allows you to do. “Best for” leads so you can jump straight to the row that matches your situation.
| Windsor.ai | Manual CSV upload | Automation platforms | Marketing API / custom MCP | |
|---|---|---|---|---|
| Best for | Live analysis plus campaign management from Claude | A single one-off question | Scheduled pulls into spreadsheets | Bespoke workflows the others don’t cover |
| Live data | Yes, queried at prompt time | No, static snapshot | Close, on a schedule | Yes, if you build it |
| Cross-channel analysis | Yes, 350+ sources | Only what you upload | Limited, via Sheets | Only if you build it |
| Campaign management (write) | Yes: create, pause, budget | No | No | Yes, if you build it |
| Setup effort | Low (no code) | None, but repeated every report | Medium | High (developer task) |
The Marketing API route is last on purpose. It’s the heaviest-effort option (a real developer task), so it belongs at the end as the fallback for when the other three genuinely don’t cover your case.
Windsor.ai for live analysis and campaign management
Windsor.ai connects your Meta Ads account to Claude through Windsor MCP in about a minute, with no code. Claude queries your live spend, ROAS, CPA, CTR, and conversion data at prompt time, and Windsor’s write actions let it create, pause, and re-budget campaigns from the same conversation, always with your explicit confirmation before any change.
What it can do
- Query live Meta Ads performance, spend, ROAS, CPA, CTR, conversions, across one or many ad accounts
- Blend Meta Ads with GA4, Google Ads, Shopify, CRM and billing data in the same conversation
- Manage campaigns from Claude: create campaigns and ad sets, boost posts, pause or enable, set budgets, with your confirmation first
- Pull custom Facebook Pixel conversions and full breakdowns (age, gender, geo, placement, device)
What it can't do
- Design net-new ad creatives, boosting reuses an existing post's creative
- Manage Instagram organic content, that's the separate Instagram connector (Instagram Ads are included here)
Setup takes about a minute
Go to onboard.windsor.ai/app/facebook, grant access and authorise via Meta's OAuth. This pulls campaigns, ad sets, ads, creatives and conversions, with custom Pixel conversions detected automatically.
In Claude, open Customize, then Connectors, search for Windsor and click Add. Sign in to your Windsor.ai account when prompted, and the connector appears in your Connectors list. You can also open the Windsor.ai listing in the Claude directory (https://claude.ai/directory/360c0c31-4bb6-42ca-8e50-5da0a100a68e) and click Connect.
Open a new chat and query your Meta Ads data in plain language, or tell Claude to pause, boost, or re-budget something and approve the change it proposes.
No code, API calls, or custom pipelines required. Runs on Windsor MCP for Claude.
See the 60-second setup
A walkthrough of connecting Meta Ads to Claude through Windsor.ai.
What data is available
| Meta Ads level | Key fields | What Claude can do with it |
|---|---|---|
| Campaign / ad set / ad performance | spend, impressions, clicks, ctr, cpc, cpm, frequency, reach | Performance reports, WoW/MoM comparisons, scaling decisions |
| Conversions & revenue | actions_purchase, action_values_purchase, actions_offsite_conversion_fb_pixel_purchase | ROAS and CPA analysis, funnel drop-off detection |
| Custom Pixel conversions | custom_conversion_action_name, custom_conversion_id, custom_conversion_rule, counts and values | Reporting on your own conversion definitions |
| Breakdowns | age, gender, geo, placement, device | Audience and placement optimisation |
| Creative performance | ad_name, creative fields, outbound_clicks, outbound_clicks_ctr | Fatigue detection, winning-angle analysis |
| Write actions | campaigns, ad sets, ads, budgets, boosted posts | Acting on the analysis without leaving Claude |
Queried live against the Meta Ads API, so there is no fixed sync schedule or cache delay. Full list in the Facebook Ads field reference.
Example prompts
Performance reporting
Summarize my Facebook Ads performance for the last 30 days by campaign. Include spend, impressions, clicks, CTR, CPC, conversions, CPA, and ROAS. Highlight the top 3 and bottom 3 campaigns by ROAS.
Break down performance over the last 30 days by audience (age, gender, geo) and placement/device. Show which segments have the lowest CPA and highest ROAS, and recommend targeting and placement changes.
Budget and scaling
Calculate my Return on Ad Spend by dividing action_values_purchase by spend across all active campaigns over the last 30 days. Correlate the top 3 highest-ROAS campaigns with their frequency and cpm metrics to tell me if I have room to scale the budget without exhausting the audience.
Based on the last 30 days, recommend how to reallocate the budget across campaigns and ad sets to improve overall ROAS. Specify what to scale, what to pause, and what to test next.
Review all ad sets where spend is over $500 this week. Identify any where the cost per purchase is 20% higher than my account average, and tell me if the drop in efficiency stems from a rising cpc or a drop in website conversion rate.
Creative and ad fatigue
Break down the outbound_clicks_ctr by ad_name. Look at my top 5 ads: what common themes, formats, or primary text keywords are driving the highest volume of outbound_clicks at the lowest cost_per_outbound_click?
Identify ad fatigue in my Meta Ads over the last 14 days vs the previous 14 days, at the ad and creative level. Flag ads where frequency is up and at least two of these worsened: CTR down, CPC up, CPA up, conversion rate down, ROAS down. Recommend next actions for each flagged ad.
Identify my top 10 ads by ROAS from the last 30 days. Summarize what likely makes each work (hook, offer, audience fit, CTA, tone), then generate 15 new ad copy variations inspired by these winners, labeled by angle.
Conversions and tracking
Analyze the daily trend between link_clicks and actions_offsite_conversion_fb_pixel_purchase for this month. Are there specific days of the week where the conversion rate drops significantly despite stable impressions and spend, indicating a potential tracking drop-off?
Show me performance for my custom Facebook Pixel conversions over the last 30 days. Break down by custom conversion name and include spend, conversions, CPA, and ROAS.
True ROAS
Calculate true ROAS across all my Meta Ads accounts for the last 30 days. Use Meta spend and Shopify revenue attributed to Meta (utm_source/utm_medium). Show total spend, attributed revenue, ROAS, and a daily trend table.
Campaign management (write actions)
Act as a senior media buyer. Based on the current spend, cpc, and purchase data across the whole account, give me a prioritized, 3-step optimization plan, and pause the ads suffering from fatigue after I confirm.
Pause every ad set with a CPA above my 30-day account average and frequency above 4. Show me the list and wait for my approval before pausing anything.
Cross-channel questions to ask next
- Which Meta campaigns produce revenue in GA4 or Shopify, not just link clicks
- How Meta CPAs compare with Google Ads on the same conversion
- Whether rising frequency on Meta correlates with falling branded search demand
- Blended ROAS across Meta and LinkedIn Ads for the same launch
Manual CSV export and upload
The zero-setup route: export a report from Meta Ads Manager as a CSV and upload it into a Claude conversation. For a single question about a fixed period, this works fine on any Claude plan.
What it can do
- One-off analysis with no account connection or new tools
- Works on any Claude plan, including free
- Good enough for a fixed-period question you will not repeat
What it can't do
- Stay current, the data is a static snapshot that goes stale the moment you export it
- Avoid repeat work, every follow-up period means another export and upload
- Handle big accounts well, file-size and row limits arrive fast
- Act on campaigns, Claude can only read what you uploaded
How: Ads Manager, Reports, Export table data as CSV, then drag the file into Claude and ask your question.
Automation platforms (Zapier, Make, n8n)
Zapier, Make, or n8n can pull Meta Ads data into Google Sheets on a schedule, and Claude reads the Sheet. This suits teams that want a spreadsheet that stays roughly current without manual exports, or an event-triggered workflow where Meta Ads is one step among several tools. It is a different job from Methods 1 and 2: those answer questions on demand, this keeps a copy of the data flowing on a timer.
What it can do
- Scheduled refreshes into a Sheet the whole team can also use
- Trigger actions off events as one step in a broader workflow spanning other tools
What it can't do
- Deliver truly live numbers, you get whatever the last scheduled run pulled
- Run itself, workflow maintenance is on you and broken runs fail quietly
- Manage campaigns from Claude, and Sheets caps how much history fits
Meta Marketing API with custom MCP or GPT-style actions
If none of the above cover your workflow (a niche endpoint, unusual permissions, an internal tool), you can build your own bridge with Meta’s Marketing API, either as a custom MCP server for Claude or via Claude’s tool use. Open-source Meta Ads MCP projects exist as starting points.
This is the heaviest-effort route here: you are wiring up auth, token refresh, and rate-limit handling yourself rather than doing a no-code setup.
What it can do
- Whatever you build, full flexibility over endpoints, fields and actions
- Cover workflows the no-code methods do not support
What it can't do
- Work without developer effort, there is no no-code path here
- Avoid ongoing maintenance, Meta API versions and access tokens rotate
Reach for this only when Methods 1 to 3 genuinely do not cover your case. It carries ongoing build and maintenance cost that the other three do not.
Conclusions: which method wins for your use case
| Your situation | Recommended | Why |
|---|---|---|
| “I want to analyze live results and act on them, create, pause, re-budget, without leaving Claude” | Windsor.ai | Only method with both live data and write actions |
| “I need Meta Ads next to GA4, Google Ads, or Shopify revenue” | Windsor.ai | Cross-channel analysis across 350+ sources is Windsor’s core differentiator |
| “I have one quick question about last month’s numbers” | Manual CSV upload | Fastest path for a true one-off, no account connection needed |
| “I want a spreadsheet that stays roughly current for the team” | Automation platforms | Scheduled pulls into Sheets are exactly that job |
| “None of the above cover what I need, and I have dev resources” | Custom Marketing API / MCP | Full flexibility, at the cost of build and maintenance effort |
FAQs
How do I connect Claude to Meta Ads?
Connecting Claude to Meta Ads (Facebook Ads) with Windsor.ai takes three steps and about a minute:
- Create a free Windsor.ai account and connect your Meta Ads account via OAuth.
- Add the Windsor MCP connector to Claude.
- Ask Claude anything about your Meta Ads performance, or tell it to create, pause, or re-budget campaigns.
The direction doesn’t matter: whether you think of it as connecting Meta Ads to Claude or connecting Claude to your Meta Ads account, it’s the same one-minute setup. For a full walkthrough with screenshots, see the step-by-step guide on how to connect Facebook Ads to Claude automatically.
Can I use this integration with Claude Code?
Yes. Windsor MCP works anywhere Claude supports MCP connectors: the Claude web app, Claude Desktop, and Claude Code. In Claude Code, add Windsor as an MCP server and you can query your Facebook Ads data (spend, ROAS, CPA, conversions, breakdowns) straight from your terminal sessions, alongside your other tools.
The setup is the same in all three: connect Meta Ads once in Windsor.ai, then add the Windsor MCP connector wherever you use Claude. See the Windsor MCP setup guide for Claude for each variant’s steps.
What can I do with my Facebook Ads data in Claude?
Once your Meta Ads data is available in Claude, you can:
- Generate instant performance reports (daily/weekly/monthly) with spend, ROAS, CPA, CTR, conversions, and more, returned as a text summary, visual dashboard, table, or CSV-ready output.
- Break down results by level (account, campaign, ad set, ad, creative) to quickly spot winners and losers.
- Diagnose performance changes by comparing periods (WoW/MoM) and flagging spikes/drops in CPA, ROAS, CTR, frequency, etc.
- Uncover audience and placement insights by segment (geo, age, gender, device, placement) to find the lowest-cost converters.
- Analyze creatives for fatigue (e.g., rising frequency + declining CTR/conversion rate) and get test ideas for new angles.
- Execute write actions directly from Claude, like creating campaigns and ad sets, boosting existing posts into paid ads, pausing/enabling campaigns, ad sets, and ads, and setting budgets.
- Create client-ready outputs like visual summaries, slide/table-ready dashboards, and action plans on demand and in plain language.
- Run cross-channel analysis (if connected) by combining Facebook Ads with GA4, Google Ads, Shopify, CRM data, etc., inside the same Claude conversation.
Find more details about Windsor MCP for Claude use cases in this guide: https://windsor.ai/how-to-use-windsor-mcp-examples-use-cases/.
How much does it cost to integrate Facebook Ads into Claude using Windsor.ai?
Windsor.ai’s pricing for Claude data integration can vary depending on the number of connected accounts and data sources. We offer absolutely transparent pricing plans, with Windsor MCP for Claude included in every plan.
How long does it take to connect Facebook Ads to Claude?
With Windsor.ai’s intuitive connector, the integration process takes just a minute. No technical expertise is required; connecting Facebook Ads to Claude is simple, straightforward, and completely code-free.
How does Windsor MCP connect Facebook Ads data to Claude?
Windsor MCP acts as a bridge between Meta Ads and Claude:
- You connect your Facebook/Meta Ads account to Windsor.ai (OAuth) so Windsor can access your data via the Meta Ads API.
- Windsor then pulls the data in the background, normalizes/cleans it, and structures it into analysis-ready datasets.
- When you use the Windsor MCP connector in Claude, Claude can query those datasets directly (instead of you exporting CSVs), so your answers are based on fresh, structured Meta Ads data; no code, no uploads, no manual prep.
Do you have helpful links to get started with integrating Facebook Ads and Claude using Windsor.ai?
Yes, we have helpful resources to help you get started. You can explore our official documentation and tutorials for Facebook Ads to Claude integration with Windsor.ai:
How often does the Facebook Ads data refresh in Claude via Windsor MCP?
With Windsor MCP, your Facebook Ads data refreshes whenever you query it in Claude. Each time you run a prompt, Windsor pulls the latest available numbers from the Meta Ads API, so you’re not working from a static CSV snapshot.
A couple of important notes:
- “Live” doesn’t always mean instant to-the-second: Meta can have natural reporting delays (especially for conversions), so some metrics may lag by minutes or longer depending on Meta’s reporting.
- If you’re comparing very recent data (e.g., “today”), it’s normal to see slight shifts as Meta finalizes results.
Can I analyze Instagram data in Claude via the same connector?
Yes. Claude can analyze Instagram data via the same Windsor MCP connector. You just need to connect Instagram (Organic) as an additional data source in your Windsor.ai account, and then query it in Claude the same way you do with Facebook Ads.
A couple of quick notes:
- Instagram Organic = profile/content metrics (posts, engagement, etc., depending on what you’ve connected).
- Instagram Ads is a part of the Facebook Ads connector.
Can Claude manage my Meta Ads campaigns?
Yes. Windsor’s write-enabled MCP gives Claude full campaign management access to your Meta Ads account. Here’s what you can do:
- Create campaigns: set objective (Traffic, Leads, or Sales), budget, bid strategy, and run dates.
- Create ad sets: define your target audience, where ads appear, and how Meta optimizes delivery.
- Boost an existing post: turn a published Facebook or Instagram post into a paid ad, reusing the original content instead of building new creative.
- Pause or enable campaigns, ad sets, and individual ads.
- Adjust budgets: set daily or lifetime spend limits at campaign or ad set level.
Nothing changes without your explicit approval. Claude shows you exactly what it’s about to do and waits for your confirmation before making any change.
Does this integration support custom Facebook Pixel conversions?
Yes. The Windsor MCP Facebook Ads connector supports custom Facebook Pixel conversions, so you can pull custom conversion metadata (e.g., custom conversion name/ID, event source, rule, retention days) and their related action counts/values, then analyze them in Claude.
In Windsor’s available Meta Ads fields, you’ll see custom conversion fields like custom_conversion_action_name, custom_conversion_id, custom_conversion_rule, plus custom conversion action count/value fields. These are what you’d use to report on Pixel custom conversions.
Example prompt:
Show me performance for my custom Facebook Pixel conversions over the last 30 days. Break down by custom conversion name and include spend, conversions, CPA, and ROAS. Highlight the top and bottom performers and suggest optimizations.
Is my advertising data used to train Claude's public models?
Data routed through Anthropic’s API (and Windsor.ai’s pipeline) is generally completely private and not used for model training, unlike consumer chat interfaces.
How far back can I pull historical Facebook Ads data?
In most cases, you can pull Facebook (Meta) Ads data as far back as your Meta ad account has reporting data available via the Meta Ads API.
Your exact historical lookback may also depend on your Windsor plan limits.
Tired of manual Facebook Ads data exports into Claude? Try Windsor.ai today to automate your reporting
