How to connect X Ads (Twitter Ads) to Google Sheets with OWOX Data Marts

Why we made this free connector

At OWOX, we’ve always believed that businesses shouldn’t have to rent their own data. So the X Ads connector is free and open source: run OWOX Data Marts yourself and there is no paid tier and no hidden features. The longer story is in why we built free data connectors for analysts.

Join the open-source movement

We’re not just releasing a free connector – we’re inviting you to help shape the future of open marketing analytics tools.

At OWOX, we believe that data access and transparency should be a right, not a luxury. That’s why this connector is 100% open-source – giving you full control over how it works, what it does, and how far it can go.

If you like what we do, please ⭐ star our GitHub repo to show your support – it helps us reach more analysts and grow the number of available connectors.

Also, feel free to:

• Explore the code and customize it to fit your needs.
• Contribute to this data connectivity ecosystem: suggest new connectors, pull new connectors, and/or provide documentation to support the wider community.
• Join our community and share your feedback.

We’ve built the core, the foundation – now it’s your turn to take it further.

Why bring X Ads data into Google Sheets?

X Ads Manager reports are fine for a quick look, and hard to bend once you need them next to other channels:

• Custom reports your way: reshape X Ads data to fit your reporting, not the platform’s.
• Side by side with other paid channels: blend X performance with CRM, GA4 or offline conversions.
• Automated dashboards and live insights your team can share, instead of manual exports.

Sheets is where marketers want to work, and that part is right. The open question is where the data should live while they do.

Why the data goes through a data warehouse

A sheet is where people read data, not where it should live. That is why OWOX Data Marts puts a data warehouse in the middle, and why there is no direct X Ads-to-sheet connector. Four things follow.

The sheet has a ceiling

A Google Sheets file holds at most 10 million cells. Ad data eats cells quietly: every ad, every day and every breakdown is a row, and every field you pull is a column, so a wide import burns through the limit faster than the row count suggests.

The data warehouse holds the full history, while the sheet report holds only the columns you choose. A backfill loads a custom date range once, and a trigger keeps the data fresh afterwards.

History outlives the sheet

Data loaded into a data warehouse stays there. A tab that gets overwritten, a sheet someone re-copies or an upstream API that changes its schema does not take last year’s numbers with it. That continuity is what campaign-over-campaign and year-on-year questions depend on.

X is rarely the only paid channel

The moment the question is “is X worth it next to the other channels?”, X data alone is not enough, and blending tabs in a sheet means lookup formulas that break when a campaign is renamed.

OWOX’s demo e-commerce project shows the alternative. Each ad platform is collected by its own connector data mart, and X Ads is one of them.

A separate data mart, Unified Ad Spend, brings the platforms together. The analyst who owns it wrote the SQL: one SELECT per platform, all UNION ALLed to one daily grain with a shared source, medium and campaign naming. Here is its X Ads block. It converts the billed charge from micros, labels the source twitter, uses url_clicks rather than app_clicks because this is a web store, and leaves conversions as NULL because the X Ads connector exposes no conversion fields – a comment in the SQL says so:

OWOX Data Marts does not model the data for you. It publishes and governs the query the analyst wrote, so everyone reads the same definition.

One number, every place you read it

The same data mart can feed a Google Sheets report, a Looker Studio dashboard, a Slack channel or an email, so the number in the sheet is the number in the dashboard. Business users read it without needing data warehouse credentials.

How it works

1. A X Ads data mart of the Connector type loads your ad data into tables in your data warehouse. A manual run backfills history, and a trigger keeps it fresh.
2. Google Sheets is connected as a destination. The data mart publishes its data there.
3. You read it in Sheets with a report created on the data mart, or by pulling it with the OWOX Data Marts extension inside Google Sheets.
4. Or you just ask. Through OWOX MCP you can blend the same data with other X Ads endpoints, other ad platforms, or your CRM and GA4 data, using the data model.

OWOX Data Marts does not transform your data. It loads, publishes and governs it, and any SQL on top is written by an analyst.

What you need

• An X Ads account and its Account ID (in the address bar of ads.x.com).
• An X developer app with Ads API access: its Consumer Key and Consumer Secret, plus an Access Token and Access Token Secret. X has to approve the app for the Ads API first, which the X documentation says can take up to three business days.
• A data warehouse. OWOX Data Marts supports BigQuery, Snowflake, Databricks, AWS Athena and AWS Redshift. The examples here use BigQuery.
• OWOX Data Marts: OWOX Cloud for the quickest start, or self-managed with Node.js and the OWOX CLI (free and open source).
• A Google account for the Google Sheets report.

Step-by-step: send X Ads data to Google Sheets

Seven steps. The first five load your X Ads data into your data warehouse. The last two bring it into Google Sheets.

Step 1: Start OWOX Data Marts ( ~2 min)

Choose how to run it:

• OWOX Cloud: sign in or sign up and you are ready for step 2.

• Self-managed (open source): install Node.js 22.22.0 or later, then run:

  npm install -g owox
  owox serve

  Open http://localhost:3000 and you are in. The OWOX docs cover deployment options beyond a local machine.

Step 2: Connect your data warehouse ( ~3 min)

Open Storages in the left menu and add your data warehouse, for example BigQuery. This is where the X Ads tables will be created. The BigQuery walkthrough, including the service account, is in the X Ads → BigQuery guide.

Step 3: Create the X Ads Data Mart ( ~5 min)

1. Click New Data Mart, give it a title and select the data warehouse from step 2.
2. Set the type to Connector and choose X Ads (the X Ads data source).
3. Add your Account ID: sign in to ads.x.com and copy the ID from the address bar.
4. Add the four app credentials: Consumer Key, Consumer Secret, Access Token and Access Token Secret. The X Ads connector signs its requests with OAuth 1.0a, so there is no sign-in button: the next section shows where each credential comes from.

Get your X Ads credentials

1. Get Ads API access for an X developer app

• In the X Developer Portal, open your app. The App ID on the app details page is the ID you submit when you ask X for Ads API access.

• Submit the X Ads API access request with that App ID and choose Standard access (analytics, campaign management, creatives and custom audiences). X emails you when the app is approved.

2. Set the app permissions

• Under User authentication settings, set the app permissions to Read and write and turn on OAuth 1.0a.

• Fill in the App info: a callback URL (for example a localhost address) and your website URL, then save.

3. Copy the keys and generate the tokens

• Open the Keys and tokens tab. Copy the API Key and Secret, which are the Consumer Key and Consumer Secret, and generate the Access Token and Secret.

• Generate the tokens while signed in as the user that has access to the ad account. On the authorization screen, click Authorize app.

Keep all four values private: anyone who has them can read your X Ads data.

Step 4: Choose what to load and backfill your history ( ~3 min)

1. Select the Ad Performance endpoint, which loads into the x_ads_stats table, and the fields you need.
2. Set the dataset, or keep the default.
3. Click Publish Data Mart.
4. Click Manual Run and choose Backfill for the first run. Add the start and end dates and click Run. Without dates, the first run imports from the first day of the previous month.
5. Open Run History and check for Success.

Step 5: Schedule the refresh ( ~1 min)

1. Open the Triggers tab of the data mart and click Add Trigger.
2. Choose Connector Run as the trigger type, then set daily, weekly, monthly or interval, plus the time, days and time zone.
3. Click Create Trigger. X Ads data now refreshes on its own.

Step 6: Connect Google Sheets as a destination ( ~2 min)

Open Destinations in the left menu, click New Destination and choose Google Sheets (more on the Google Sheets destination). A destination is where a data mart can deliver its data; the same list also holds Looker Studio, Slack and email.

Step 7: Bring the data into Google Sheets ( ~2 min)

You have two ways to read the data mart in Sheets. Both are part of spreadsheet reporting in OWOX Data Marts.

Option A: a report on the data mart. Reports live on the Destinations tab.

1. Open the data mart, go to the Destinations tab and click New Report under your Google Sheets destination.
2. Give the report a title and share the Google document with the address the form shows.
3. Paste the URL of your Google Sheet, or click New Sheet to create one.
4. Choose the report columns you want in the sheet.
5. Click Create & Run report.

Each report is listed on the Destinations tab with its last run and status. Run it again whenever you need fresh data, or put it on a schedule with a report trigger.

Option B: the OWOX Data Marts extension. Install OWOX Data Marts from the Google Workspace Marketplace, open it inside Google Sheets and pull the data mart from there, without leaving the sheet. If your team works in Excel, there is an OWOX Excel add-in too.

Ask the blended question in plain language

X Ads data rarely answers a question on its own. With OWOX MCP you can blend it with other X Ads endpoints, with other ad platforms, or with your CRM data and GA4 data (GA4 through its native BigQuery export), using the data model, and ask for all of it in plain language.

Once ad spend is a governed data mart, nobody has to write the join to ask about it. Connect Claude to OWOX Data Marts with the OWOX Claude connector and a marketer can ask:

Compare our X Ads spend with our other paid channels.

Claude asks OWOX which data marts are relevant, reads their fields and the joins the analyst defined, and queries the one it picks. Ask it against raw data warehouse tables instead and it has to guess the join.

MCP is the interface here, not the guarantee. The guarantee is the governed data mart behind it, and every question is logged in Run History. For how that works end to end, read governed MCP analytics.

What’s next?

This connector is part of our effort to make data ownership simple, transparent and accessible for everyone.

Here are more resources to explore:

• The X Ads connector for each data warehouse: BigQuery, Snowflake, Databricks, AWS Athena and AWS Redshift.
• The full data warehouse setup in the X Ads → BigQuery guide.
• The same route for another platform: Facebook Ads → Google Sheets, LinkedIn Ads → Google Sheets and TikTok Ads → Google Sheets. More free connectors are on the connectors page.

Check out our GitHub repo, leave us a ⭐ star, and let’s build better tools together.

Data IntegrationHow to Connect Facebook Ads to Google Sheets with OWOX Data MartsSeptember 30, 2026→Google BigQueryHow to Connect BigQuery to Google Sheets: Three WaysOctober 6, 2026→Data IntegrationCRM and Digital Marketing Data Integration: A Practical GuideSeptember 30, 2026→

See all articles →