Twitter/X Ads → Google BigQuery
AI-first ETL from Twitter/X Ads into Google BigQuery. Governed entities, incremental sync, typed landing tables.
How Datrise loads Twitter/X Ads into Google BigQuery
Datrise syncs Twitter/X Ads's campaign metrics, spend, engagement, and ad conversion performance into Google BigQuery as a partitioned table per source entity. Flexible or custom fields land in JSON or nested/repeated (STRUCT) columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target, so re-runs update only what changed. Partition by ingestion or event date and cluster by entity id to keep scanned bytes low. BigQuery bills by bytes scanned, so Datrise partitions and clusters every table to keep query costs predictable.
Ideal for Google-stack analytics and ML on serverless infrastructure.
Endpoints
Twitter/X Ads: Ad performance source for X campaign analytics.
Google BigQuery: Serverless analytics warehouse on GCP.
How Twitter/X Ads entities map to Google BigQuery
| Twitter/X Ads entity | Google BigQuery object | Notes |
|---|---|---|
| campaign metrics | twitter_x_ads_campaign_metrics | id PK · custom fields → JSON or nested/repeated (STRUCT) columns |
| spend | twitter_x_ads_spend | id PK · linked to twitter_x_ads_campaign_metrics |
| engagement | twitter_x_ads_engagement | id PK · linked to twitter_x_ads_campaign_metrics |
| ad conversion performance | twitter_x_ads_ad_conversion_performance | id PK · linked to twitter_x_ads_campaign_metrics |
FAQ
How does Datrise handle Twitter/X Ads's custom fields in Google BigQuery?
Flexible values are stored as JSON or nested/repeated (STRUCT) columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Google BigQuery types.
How does the Twitter/X Ads to Google BigQuery sync stay up to date?
It runs incrementally — Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target.
Related pipelines
More destinations for Twitter/X Ads
- Twitter/X Ads → Amazon Redshift
- Twitter/X Ads → Databricks SQL Warehouse
- Twitter/X Ads → ClickHouse
- Twitter/X Ads → DuckDB
- Twitter/X Ads → Amazon Athena
- Twitter/X Ads → Amazon S3 Data Lake
- Twitter/X Ads → Azure Data Lake Storage
- Twitter/X Ads → Azure Synapse
- Twitter/X Ads → Spreadsheets
- Twitter/X Ads → Airtable
- Twitter/X Ads → CSV Files
- Twitter/X Ads → MongoDB
More sources for Google BigQuery
- LinkedIn Ads → Google BigQuery
- Meta Ads → Google BigQuery
- SAP → Google BigQuery
- Amplitude → Google BigQuery
- MoEngage → Google BigQuery
- Auth0 → Google BigQuery
- Attio → Google BigQuery
- Bigin by Zoho → Google BigQuery
- BambooHR → Google BigQuery
- Workday → Google BigQuery
- Pipeliner CRM → Google BigQuery
- Kommo → Google BigQuery
Early access
Connect Twitter/X Ads to Google BigQuery the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.