Connector

Collect X Ads data in Google BigQuery

Load X Ads, formerly Twitter Ads, into your own BigQuery tables with OWOX Data Marts: campaigns, line items, promoted tweets and daily performance, refreshed on a schedule. Read each promoted post next to its cost, then join it with web analytics and CRM.

X AdsConnectedAccountsAd PerformanceAd Performance b…All Cards
Data MartPublishedone definition
Google BigQueryDateClicksImpre…Daily 09:00
Refreshed on a schedule. No exports, no copy-paste.

Get Started Free

Hand this to your AI

X Ads reports impressions, engagements and what it billed, never what the visitors from a promoted post were worth.

Paste this into your AI assistant. It loads X Ads into Google BigQuery with OWOX Data Marts and joins link clicks to web analytics visits and CRM deals, so each campaign gets a value next to its cost.

The prompt

load X Ads into Google BigQuery and join link clicks to the web analytics visits and CRM deals that followed, so I get deals and revenue per campaign next to billed spend

Endpoints

S00 · Why

Why join X Ads with your web analytics and CRM

On X, an ad is a post. X Ads reports its impressions, engagements and the amount billed, but not what the visitors it sent were worth. To see that, a promoted post, its cost, website touch points and CRM deals have to sit in one data warehouse.

  • Read the promoted post's text and counts beside what it cost
  • Compare X with LinkedIn, Facebook and Google in one spend table
  • Connect link clicks to the visits and deals that followed
X AdsPromoted post spend
Web analyticsVisits, sign-ups
CRMDeals
Your data warehouseBigQueryPromoted po…Touch pointDealJoined by idPost promotedDeal months laterOne query links the ad to the deal.

S01 · Step 1

Step 1: Connect X Ads and pick the fields

Create a Data Mart, choose X Ads as the data source, enter your developer app keys and tokens and the Account ID, and tick only the fields you need.

  • 10 endpoints and 187 fields to choose from
  • Ad Performance has 20 fields: impressions, clicks, billed charge, engagements, follows, likes
  • Several account ids can load into one Data Mart
New Data MartChoose a sourceLinkedIn AdsX AdsReddit AdsAuthorizeConnectedEndpointAd PerformanceAccountsAd Performance by…All Cards
Ad Performance20 fieldsdateplacementimpressionsclicksbilled_engagementsbilled_charge_local_micro

S02 · Step 2

Step 2: Load X Ads into a BigQuery table

The dataset and table in your data storage are pre-filled, and you can change them. Run it and the first load, from the start of the previous month through today, lands in your own BigQuery project.

  • Performance goes to a table such as x_ads_stats
  • The billed amount is in micros of local currency (billed_charge_local_micro); convert it once in your model
DestinationBigQueryDatasetx_adsTablestatsRun
Run HistoryPendingRunningSuccessIncremental load
Tablex_ads.stats

S03 · Step 3

Step 3: Get a business-friendly output schema

After the first run you get the output schema: every field with a readable description, not an API identifier. Your data quality checks can read it too.

  • placement tells ALL_ON_TWITTER from PUBLISHER_NETWORK
  • Anyone on the team can read the table
x_ads.statsOutput schemaFieldDescriptiondateThe date for which the…placementThe placement type (ALL_ON_TWITT…impressionsNumber of impressions.clicksNumber of clicks.billed_engagementsNumber of billed engagements.billed_charge_local_microBilled amount in micros.

S04 · Step 4

Step 4: Keep the X Ads tables linked

Line items, promoted tweets and tweets stay separate tables, joined by ids. Together they become one X Ads data model.

  • A promoted tweet's tweet_id finds the post's full_text and counts in Tweets
  • Campaigns, accounts and cards load as tables of their own
Line Itemsidnamecampaign_id
Tweetstweet_idfull_textretweet_count
Promoted Tweetsidline_item_idtweet_id

S05 · Step 5

Step 5: Schedule the refresh and backfill history

Set it once. A scheduled refresh keeps the tables current, and a manual backfill loads any past period.

  • Add a run trigger once; a lookback window, 2 days by default, reloads recent days
  • Backfill a custom start and end date
ScheduleRun on a scheduleDaily 09:00
BackfillRun backfill
Run HistoryDaily scheduleManual backfillDaily schedule

S06 · Step 6

Step 6: Reuse the same table everywhere

One table feeds your data model, spreadsheets, dashboards, AI assistants like Claude and ChatGPT, and scheduled AI insights in Slack or email.

  • See which promoted posts earned their cost
  • Every report reads the same table
X AdsData MartPublished
Your data model
Google Sheets
Data Studio dashboards
Claude, ChatGPT
Slack, email

Recent updates

Why OWOX

Why OWOX for X Ads in BigQuery

Hand-built Ads API scripts, a generic ETL tool or manual exports each get X data out. OWOX also keeps it yours, readable and ready to model.

  • You own the data. It lands in your own BigQuery project, in tables you control.
  • The post and its cost together. Promoted tweets load next to the tweets themselves, with text and engagement counts you can join to spend.
  • Ready for a data model. Separate tables joined by line item and tweet ids, built to connect to web analytics and CRM.
  • Maintained for you. No scripts to fix when X changes its Ads API.
  • Free to self-host. The open-source OWOX Data Marts runs in your own infrastructure.

Book a callGet Started Free

Trust

The Data Partner You Can Trust

users

166K Source: Internal OWOX data as of 2026-11-15

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

171K3

In Open Source We Trust

Customers