Ask Claude about your X Ads data
X Ads bills by engagement, not by outcome. Link that billed spend to web analytics and CRM in your data warehouse, then ask Claude which campaigns bring pipeline.
X Ads impressions spread across many countries, and which ones actually engage is a guess.
Paste this into your AI assistant. It loads X Ads performance by country into a governed Data Mart with OWOX Data Marts and connects Claude through the OWOX MCP server, so engagement rates are calculated by SQL.
The prompt
Read https://www.owox.com/ai-agent-setup.md and follow it to set up OWOX Data Marts for me, starting from /connectors/x-ads-connector-to-claude.md. The task: connect Claude to our X Ads Data Mart and rank countries by impressions, then add clicks and engagement rate for each, with location names matched to our targeting. Tag the links you give me with utm_campaign=ai-task and utm_term=data-foundation. Use what you know about my context and goals
X Ads Endpoints
10 X Ads endpoints you can import. Each lands in its own table in your data warehouse.
Accounts
Advertising accounts — name, business, country, timezone, and approval status.
12 fieldsAd Performance
Daily ad performance by placement — impressions, clicks, spend, engagements, and social actions.
20 fieldsTime seriesAd Performance by Country
Daily ad performance broken down by country — impressions, clicks, spend, engagements, and social actions.
21 fieldsTime seriesAll Cards
All card types with full creative details — type, title, destination URL, call to action, and media.
30 fieldsCampaigns
Your campaigns — status, budget optimization, daily and total budget, and currency.
19 fieldsCards
Website and app cards — type, URI, and components.
8 fieldsLine Items
Line items within campaigns — bid strategy, goal, product type, budget, and schedule.
33 fieldsPromoted Tweets
Tweets promoted as ads — status, approval, and links to their tweets and line items.
8 fieldsTargeting Locations
Reference table of location IDs with names and country codes — join targeting_value with the country field in Ad Performance by Country.
4 fieldsTweets
Original tweets used as ad creatives — text, type, language, engagement counts, and card URI.
34 fields
Why X Ads does not go straight to Claude
Claude can read an ad account, but that shows what promoted posts cost, not which of them led to a sign-up or a deal. Spend, website visits and CRM deals sit apart; the join belongs in a warehouse first, where it is reliable, scalable and business-ready.
- X Ads reports billed engagements, not what an engagement was worth
- The data analyst joins promoted-post spend to visits and CRM deals by SQL keys and controls the result
- Claude answers from that joined data, not from billed engagements alone
Step 1: Load X Ads into your data warehouse first
Create a Data Mart with X Ads as the source and choose where the data lands. It works with any popular data warehouse.
- 10 endpoints and 187 fields to choose from, each endpoint in its own table
- Campaigns, line items, promoted posts and performance by country
- Open the X Ads connector for your data warehouse below
Step 2: Put X Ads billed spend next to your leads
In your data warehouse the model merges X Ads with your other ad platforms, then joins leads and campaign results by a key. Pick an industry to see the shape of its model.
- Billed engagements become spend you can compare across platforms
- Leads join campaign results by SQL keys, not VLOOKUP
- Measures such as pipeline_per_dollar are defined once
Step 3: Connect Claude to your X Ads data with OWOX MCP
Add the OWOX MCP server in Claude under Settings > Connectors > Add custom connector. Claude then sees the Data Marts you publish and queries them through MCP.
- Settings > Connectors > Add custom connector, paste the OWOX MCP URL and sign in
- Claude sees only the Data Marts you publish
Step 4: Ask Claude which X Ads campaigns bring pipeline
Ask in plain words. Claude finds the right Data Mart and queries it, so the numbers come from your data warehouse and not from a guess.
- Ask about a campaign, a line item or a country in plain words
- The answer sets billed spend against leads and pipeline, with measure names shown
Step 5: Export the answer to Google Sheets, CSV or XLS
Optional: in one click send Claude's answer, or the data behind it, to Google Sheets, CSV or XLS to check it or share it.
- Verify the answer in a sheet before it goes to stakeholders
- One Data Mart feeds the chat, the sheet and the file
- 0.41.0Rotating a connector key is one change: Sources share reusable Credentials
- 0.39.0Reload a year of history in one backfill, not twelve
- 0.37.0Short links resolve only on known short link services and domains you allow
- 0.37.0Clearer connector errors, and custom connectors that handle more APIs
- 0.36.0Support MCP protocol 2026-07-28 and alert on compatibility failures
Why OWOX for X Ads in Claude
Connecting Claude straight to X Ads gets billed engagements into a chat. OWOX ties them to leads and pipeline in your data warehouse.
- You own the data. It lands in your own data warehouse, in tables you control.
- Answers about the whole business. Promoted-post spend, web analytics, CRM and deals are linked, not copied from an ad account.
- Zero hallucinations on your data. Claude answers from governed Data Marts and shows the measure names it used.
- Promoted posts in context. X Ads campaigns and promoted-post performance sit next to every other paid channel in one model.
- Maintained for you. No scripts to fix when X changes its API.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.
