Connect X (Twitter) Ads to Claude

Automatically sync your X Ads data to Claude using the Windsor.ai connector.

Ask Claude about spend, engagement, conversions, and audience reach across your X campaigns, and compare them with Meta, Google, and LinkedIn Ads in the same chat.

Forget CSVs. Stop copy/paste. Connect data in minutes. No code required.

Try It Free View documentation
Free forever plan No credit card needed
logo connect
Join over 6,000 businesses that trust Windsor.ai to connect X Ads to Claude
audi logo
colgate
asics
roche
novo nordisk logo
UBS
unicef
verisure
wpp
club med
skoda
heineken
puma
audi logo
colgate
asics
roche
novo nordisk logo
UBS
unicef
verisure
wpp
club med
skoda
heineken
puma

Which one do I need?

All four methods below get your X (Twitter) Ads data in front of Claude. They differ in how fresh the data is, how much setup they take, and whether Claude can only read your campaigns or also change them.

“Best for” leads so you can jump straight to the row that matches your situation.

Windsor.ai Manual CSV upload Scheduled pulls into Sheets X Ads API / custom MCP
Best for Live analysis of X Ads next to your other channels A single one-off question A spreadsheet the team keeps using Bespoke workflows, including campaign changes
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) No, read-only No No Yes, if you build it
Setup effort Low (no code) None, but repeated every report Medium High (developer task, plus X Ads API approval)

The API route is last on purpose. It is the heaviest option, a developer task that starts with applying for X Ads API access, so it belongs at the end as the fallback for cases the other three do not cover.

Method 1

Windsor.ai for live analysis and cross-channel reporting

Windsor.ai connects your X Ads account to Claude through Windsor MCP in a few minutes, with no code. Claude queries your live spend, impressions, engagement, and conversion data at prompt time, so every answer comes from the current numbers rather than an export. The X Ads connector is read-only: Claude analyzes and reports on your campaigns but does not change them.

Setup takes a few minutes

1
Connect X Ads to Windsor

Go to onboard.windsor.ai/app/twitter, choose X Ads as the source and authorize with your X account. Windsor pulls campaigns, ad groups, ads, spend, engagement, audience reach and conversion data.

2
Add the Windsor.ai connector to Claude

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.

3
Ask Claude about your X campaigns

Start a new chat and ask for a spend summary, an ad group comparison or a client report. Claude fetches the data through Windsor and answers in the same chat.

No code, API access application, or custom pipelines required. Runs on Windsor MCP for Claude. Screenshots for each step are in the setup guide.

See the setup

How to add the Windsor.ai connector to Claude and start querying your data.

Skip CSV exports and manual formatting, get clean, ready-to-use answers straight in Claude
Puts X Ads next to Meta, Google, LinkedIn and TikTok Ads so Claude can compare channels in one conversation
Tracks cpc and click_rate per ad group over time to catch rising costs early
Read-only access to your X account, so nothing changes in Ads Manager unless you do it

What it can do

  • Query live X Ads performance, spend, impressions, clicks, engagements, follows, video views and conversions, across one or several ad accounts
  • Break results down by campaign, ad group, ad, objective and campaign status
  • Blend X Ads with Meta Ads, Google Ads, LinkedIn Ads, GA4, Shopify or HubSpot data in the same conversation
  • Build recurring reports and client summaries from a single prompt

What it can't do

  • Pause, create or edit X campaigns, the X Ads connector is read-only (Windsor's write actions cover Google, Meta, TikTok, LinkedIn and Microsoft Ads)
  • Report on organic posts, that is the separate X Organic connector

What data is available

X Ads level Key fields What Claude can do with it
Campaign / ad group / ad performance spend, impressions, clicks, url_clicks, cpc, cpm, click_rate Spend audits, week-over-week comparisons, budget decisions
Conversions and revenue conversion_purchases, conversion_purchases_sale_amount, conversion_sign_ups, conversion_site_visits Cost per purchase and sign-up, revenue per campaign
Engagement and audience engagements, likes, retweets, replies, follows, video_total_views, total_audience_reach Creative comparison, follower growth per ad
Structure campaign, adgroup, ad_name, objective, campaign_status Grouping by objective, active versus paused reporting

Queried live from the X Ads API through Windsor, so there is no fixed sync schedule or cache delay. Full list in the X Ads field reference.

Metrics for your own organic posts (impressions, engagement, follower counts) come from the separate X Organic connector, which you can add to the same Claude conversation. See X Organic to Claude.

Example prompts

Campaign spend and results

Show spend, impressions and clicks per X Ads campaign for the last 7 days, by day. Which campaigns are spending more this week than last, and did clicks move with them?
For each X Ads campaign in the last 30 days, show spend, impressions, url_clicks, conversion_purchases and conversion_purchases_sale_amount. Which campaigns have the highest spend per purchase, and what do they have in common?
What did we spend on X Ads today and this month so far, per campaign and per account? Flag any campaign that is on track to spend more than last month.

Ad groups and ads

Break down the last 30 days by campaign, adgroup and ad_name with spend, impressions and clicks. Which ad groups carry most of the spend, and which ads inside them get the fewest clicks per impression?
Compare our X Ads ad groups by cpc and click_rate for the last 7 days against the 7 days before. Flag any ad group where cpc rose while click_rate fell, and suggest what to test.
Group this month's X Ads results by objective. Which objective delivers the lowest cost per url click, and does the ranking change when we look at conversions instead?

Engagement and audience

Rank our X ads by follows per 1,000 impressions for the last 30 days. Show engagements, likes, retweets and replies for the top 10 and describe what the best-performing creatives have in common.
Which X ads have the most video_total_views relative to spend in the last 14 days? Show total_audience_reach alongside so I can see which ones reached new people.

Cross-channel

Compare X Ads, Google Ads and Meta Ads for the last 30 days on spend, clicks, cost per click and cost per conversion. Where would you move budget, and why?
Using GA4, show sessions and conversions from X paid traffic for the last 30 days next to X Ads spend and url_clicks per campaign. Which campaigns bring visitors who convert?

Cross-channel questions to ask next

  • Which X campaigns produce sessions and revenue in GA4, rather than url clicks alone
  • How X cost per conversion compares with Google Ads and LinkedIn Ads on the same conversion
  • Whether follows bought through X Ads show up as growth in your X Organic numbers
  • Blended cost per acquisition across X, Meta and Google for the same launch
Method 2

Manual CSV export and upload

The zero-setup route: export a campaign report from X Ads Manager as a CSV and upload it into a Claude conversation. For a single question about a fixed period, this works 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 snapshot that goes stale the moment you export it
  • Avoid repeat work, every follow-up period means another export and upload
  • Handle large accounts well, file-size and row limits arrive fast
  • Combine X with other channels unless you export and upload each of them too

How: in X Ads Manager, pick the campaign or ad group view and date range you need, export the table as a CSV, then drag the file into Claude and ask your question.

Method 3

Scheduled pulls into Google Sheets

An automation platform such as Zapier, Make or n8n, or a small scheduled script against the X Ads API, writes X Ads data into a Google Sheet on a timer, and Claude reads the Sheet. This suits teams that want a spreadsheet that stays roughly current without manual exports. Note that X Ads support on the automation platforms is thin compared with the organic X API, so this often ends up being a script you maintain.

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 schedule.

What it can do

  • Scheduled refreshes into a Sheet the whole team can also use
  • One step in a broader workflow that spans other tools

What it can't do

  • Deliver live numbers, you get whatever the last scheduled run pulled
  • Run itself, broken runs fail without telling anyone and the fix is on you
  • Hold much history, Sheets caps how many rows fit before it slows down
Method 4

X Ads API with a custom or third-party MCP server

If none of the above cover your workflow, or you need Claude to change campaigns, you can build your own bridge to the X Ads API as a custom MCP server for Claude, or use one of the third-party X Ads MCP servers as a starting point. Some of those expose write endpoints, so Claude can pause or edit campaigns through them.

This is the heaviest route here. X Ads API access has to be applied for and approved before you can call it, and after that you are handling auth, token refresh and rate limits yourself.

What it can do

  • Whatever you build, full flexibility over endpoints, fields and actions
  • Campaign changes from Claude, if the server you build or pick supports them

What it can't do

  • Work without developer effort and X Ads API approval, there is no no-code path
  • Avoid ongoing maintenance, API versions and access tokens rotate

Reach for this only when Methods 1 to 3 do not cover your case. It carries 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 X Ads results without exporting anything” Windsor.ai Live data at prompt time, no code, a few minutes to set up
“I need X Ads next to Meta, Google Ads, GA4 or Shopify revenue” Windsor.ai Cross-channel analysis across 350+ sources in one conversation
“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” Scheduled pulls into Sheets A timed copy of the data is exactly that job
“I need Claude to change campaigns, and I have dev resources” X Ads API / custom MCP The only route with write access, at the cost of build, approval and maintenance

FAQs

What is the Windsor.ai X Ads Claude connector?

The Windsor.ai X Ads Claude connector is a data integration that pulls your X (formerly Twitter) Ads campaigns, ad groups, ads, spend, engagement, audience, and conversion data into Claude through Windsor MCP. Once connected, you ask questions about your X advertising in plain language and Claude answers from live data, with no exports.

Tired of manual X Ads data exports? Try Windsor.ai today to automate your reporting

Access your data from various sources in one place. Get started for free.
Start for Free Book a Demo
g logo
fb logo
big query data
youtube logo
power logo
looker logo