Send X Ads data to Google Sheets
Load X Ads into your data warehouse first, link promoted-post spend to web analytics and CRM by SQL keys, then send the answers to Google Sheets on a schedule. The sheet stays tied to your source of truth.
X AdsConnectedAccountsAd PerformanceAd Performance b…All Cards
Google SheetsDateClicksImpre…Daily 09:00The Twitter Ads sheet tracks likes and clicks, while the sign-ups and deals those posts brought sit in another system.
Paste this into your AI assistant. It loads Twitter Ads into your data warehouse with OWOX Data Marts, links promoted-post spend to web analytics and CRM, and sends the result to a sheet on a schedule.
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/free-x-ads-connector-to-google-sheets.md. The task: send a weekly Google Sheets report of Twitter Ads spend and clicks per campaign next to the sign-ups and deals they led to, refreshed from the Data Mart in my data warehouse. 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 Google Sheets
A direct link gives you a copy of the ad account in a sheet. It shows what promoted posts cost, not which of them led to a sign-up or a deal. Spend, website visits and CRM deals live in different systems, and a sheet is not built to join them reliably, at scale or business-ready, so the join happens in a warehouse first.
- X Ads reports billed engagements, not what an engagement was worth
- The data analyst links promoted-post spend, web analytics and CRM deals by SQL keys and controls the result
- Stakeholders keep the sheet they like, now tied to your source of truth
X AdsPromoted postsGoogle Sheets
Data warehouseJoined by idStep 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
X AdsData MartGoogle BigQuery
AWS Athena
Snowflake
AWS Redshift
Databricksx_ads.statsStep 2: Link X Ads to web analytics and deals
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 spend from every platform sits in one table
- Leads and campaign results join by SQL keys, not VLOOKUP
- Measures such as pipeline_per_dollar are defined once
X AdsAd Performance
LinkedIn AdsAd spend
Google AdsAd spendStep 3: Send X Ads data to Google Sheets
Connect a Sheets report to the Data Mart. Aliases and field descriptions arrive as notes in the column headers, so billed amounts and engagements are read the same way by everyone.
- The sheet reads your data warehouse, not the X Ads API
- Hover a header to see what the field means
Google SheetsNotes in headersdatebilled_charge_loc…impressionsStep 4: Refresh your X Ads sheet on a schedule
Set a scheduled refresh once. Daily is the usual choice and hourly is possible when you need it.
- Every refresh is logged in Run History
- Stakeholders open a sheet that is already up to date
Google SheetsUpdatedStep 5: Reuse X Ads inside OWOX MCP
The same Data Mart works in OWOX MCP, your assistant for data. Request any report, chat with your data, then get the report in Google Sheets or Excel in one click.
- Ask in plain words; the answer comes from your data warehouse
- Define the numbers once and every report reads them
Google SheetsOpen
ExcelOpen
- 0.41.0Rotating a connector key is one change: Sources share reusable Credentials
- 0.41.0Reuse one Google Sheets or Google Chat key across Destinations
- 0.40.0Warnings when a Count reads a joined Data Mart
- 0.40.0Open the Google Sheet a scheduled report fills, right from Triggers
- 0.39.0Reload a year of history in one backfill, not twelve
Why OWOX for X Ads in Google Sheets
Scripts that pull straight from an ad account get numbers into a sheet. OWOX also keeps the data yours, linked and ready to model.
- 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.
- Sheets stay in sync. Notes in the headers, a schedule you set once, no API token to fix in the sheet.
- Maintained for you. No scripts to fix when X changes its API.
- Promoted posts in context. X Ads campaigns and promoted-post performance sit next to every other paid channel in one model.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.