How to connect X (Twitter) Ads to Looker Studio without wrong numbers

To connect X (formerly Twitter) Ads to Looker Studio you need a go-between: Google has no native X connector, and X does not publish one either. The real options are three. A partner connector from the Looker Studio gallery (Supermetrics, Windsor.ai, Porter Metrics, Catchr and others) refreshes on its own. A CSV export from X Ads Manager, pasted into a Google Sheet, is free and manual. The X Ads API requires an approved access request. The part that breaks most X reports is not the connection, though. It is the metric: the engagement count X shows includes engagement you never paid for.

Naming note: Looker Studio went back to the Data Studio name in April 2026. Same product, at datastudio.google.com.

First question: does X deserve its own page?

I ask because I have watched agencies build a full X Ads dashboard for an account where X was a sliver next to Meta and Google. A paid connector, a dashboard to maintain, and a client who opened the X page once a quarter.

My rule of thumb: if X is a secondary channel, it goes into the report as one row (spend, impressions, clicks, result), not as a page. A sheet updated weekly is enough. If X is a primary channel with its own budget and target, then a partner connector and a dedicated page are worth it. Report depth should follow budget, not the number of platforms you can plug in; what to cut from a recurring report is covered in the weekly ad report.

What the gallery offers for X

I searched "twitter" in the gallery in October 2026. Google-built connectors: none. Partner connectors: about 40 results, mixing X Ads, X organic and multi-source connectors. The X Ads ones include Supermetrics, Windsor.ai, Porter Metrics, Catchr, Dataslayer, Two Minute Reports, Power My Analytics, Reporting Ninja, Cervinodata, Adzviser, Detrics, everythingData and TapClicks.

Two things to check before you choose:

• Ads or organic. Several vendors list an "X Ads" connector and a separate "X Organic" or "X Insights" one. Only the ads connector brings campaign spend and results.
• Who stands behind the number. The gallery states that partner connectors are not provided by Google and that Google makes no promises about their performance or quality. If X spend in Looker drifts from X Ads Manager, the vendor's support is your only line.

Connecting works like any partner connector: Create → Data source, search "X Ads", authorize the connector, sign in to X inside it, pick the ad account and connect. Google Ads is the exception with a shorter native path: connect Google Ads to Looker Studio.

The free route: export from X Ads Manager

X Ads Manager exports campaign CSVs. Per X's help center:

1. Open the campaign dashboard in X Ads Manager.
2. Click Export at the top right.
3. Choose a daily or hourly breakdown. Columns vary with the campaign objective.
4. If you manage several ad accounts, use bulk export, which pulls across all of them; the standard export covers one account.

From there it is the same flow as TikTok: paste the CSV into a Google Sheet tab with fixed columns and connect the sheet through the native Google Sheets connector. For a one-time report, upload the CSV through the File Upload connector, which accepts up to 100 MB per dataset and requires the same structure in every file. I compare those two routes in more depth in connect TikTok Ads to Looker Studio.

One difference from TikTok: I did not find a scheduled email delivery for X Ads reports in X's help center, the way TikTok has one. Plan on a person doing the export.

The X Ads API, if you have a developer

The X Ads API is not open to any app. The documentation asks for a developer account, an app created in the developer console, and an Ads API access form submitted for each app; only after approval do you regenerate user tokens and start calling it. The tier that includes analytics is Standard Access.

Three rules from the analytics documentation that matter if an API feeds your Looker report:

• Time range per request. The synchronous endpoint takes up to 7 days per call; asynchronous jobs take up to 90 days non-segmented and 45 days segmented.
• Numbers that still move. Metrics are final after 24 hours, except spend, which can change for up to 3 days; billing data can take up to 14 days.
• Store your history. X recommends storing metrics locally rather than repeatedly querying data older than 30 days.

Translation: without a database in between, the API is not your path. A partner connector already does that work.

The X metrics that mislead in Looker

This is where X reports go wrong, whatever pipe brought the data in. Definitions below come from X's help center page on campaign CSV exports.

X's help center says plainly that CSV metrics include engagement you are not billed for: if someone reposts your ad and others interact with the repost, it lands in your numbers. A cost per engagement built on Engagements looks better than reality. Build it on Billed engagements.

If X shares a report with Meta and Google, give each platform its own column and only total the spend. The reasons are the same as in Meta and Google Ads in one dashboard.

Checklist for an X report in Looker

• X Ads connector (not X organic), or the campaign CSV, not the post activity export
• Cost per engagement built on Billed engagements
• Cost per click built on Link clicks, not Clicks
• Footer note: spend for the latest 3 days may still change
• X in its own column, conversions never added to Meta's or Google's
• Sanity check: last full week's spend matches X Ads Manager

Next step

Decide first whether X earns a page or a row. If it is a row, export the CSV weekly into a sheet; that takes less time than evaluating connectors. If it is a page, trial two partner connectors on the same account and keep the one whose last full week of spend matches X Ads Manager. And if Meta, Google and TikTok carry most of your work, see how the Claude connector handles those three in one conversation.