YouTube Analytics to PostgreSQL integration

Connect YouTube Analytics to PostgreSQL and automatically sync your marketing platform data. Weld extracts Videos, Channels, Playlists, and Views from YouTube Analytics, loads them into PostgreSQL, and lets you transform the data using SQL or dbt, no custom scripts required.

4.8 on G2
YouTube AnalyticsSource
WeldWeld
PostgreSQLWarehouse
Weld · New sync
YouTube AnalyticsSourceYouTube AnalyticsConnected
Tables to sync
  • content_owner_basic_a437 cols
  • content_owner_asset_basic_a336 cols
  • channel_basic_a335 cols
  • content_owner_asset_province_a331 cols
  • content_owner_province_a330 cols
  • channel_province_a328 cols
  • Extract
  • Load
  • Keep in sync
PostgreSQLDestinationPostgreSQLReady
youtube_analytics schema
  • youtube_analytics.content_owner_basic_a4Synced
  • youtube_analytics.content_owner_asset_basic_a3Syncing
  • youtube_analytics.channel_basic_a3Synced
  • youtube_analytics.content_owner_asset_province_a3Synced
  • youtube_analytics.content_owner_province_a3Synced
  • youtube_analytics.channel_province_a3Synced
YouTube Analytics tables
52
fields, typed
921
agent context included
MCP

Trusted by data and AI teams

  • Flatpay
  • Holafly
  • eComplete
  • Dishoom
  • Danish Endurance
  • Female Invest
  • Son of a Tailor
  • Onomondo
  • Medik8
  • Pas Normal Studios
How it works

How to set up YouTube Analytics to PostgreSQL in Weld.
In the app, with the API or an agent.

Weld · New YouTube Analytics sync
YouTube AnalyticsNew connectionYouTube AnalyticsAuthorised
Connection nameyoutube_analytics
AuthorizeOpens YouTube Analytics to grant read access
Use cases

Why sync YouTube Analytics to PostgreSQL?
Ready for analysis.

Centralizing your YouTube Analytics data in PostgreSQL lets you join it with other data sources for cross-platform analytics and deeper insights.

Build reliable dashboards and reports by querying YouTube Analytics data directly in PostgreSQL using SQL or your preferred BI tool.

  • Centralized data warehouse

    Bring YouTube Analytics data into PostgreSQL alongside other sources to create a single source of truth for your organization.

  • Automated reporting

    Replace manual exports and spreadsheet-based reporting with automated pipelines from YouTube Analytics to PostgreSQL. Connect BI tools like Looker, Metabase, or Power BI.

Schema

What data can you sync?
Every YouTube Analytics table, keys intact.

Weld syncs the following data objects from YouTube Analytics into PostgreSQL. The exact tables and fields depend on your YouTube Analytics configuration and the permissions granted during setup.

Open the schema explorer
All 52 tables
  • content_owner_basic_a4
  • content_owner_asset_basic_a3
  • channel_basic_a3
  • content_owner_asset_province_a3
  • content_owner_province_a3
  • channel_province_a3
  • content_owner_asset_combined_a3
  • content_owner_combined_a3
  • content_owner_asset_annotations_a1
  • content_owner_asset_device_os_a3
  • content_owner_asset_playback_location_a3
  • content_owner_asset_traffic_source_a3
  • content_owner_playlist_combined_a2
  • playlist_combined_a2
  • channel_combined_a3
  • content_owner_annotations_a1
  • content_owner_asset_cards_a1
  • content_owner_device_os_a3
  • content_owner_estimated_revenue_a1
  • content_owner_playback_location_a3
  • content_owner_subtitles_a3
  • content_owner_traffic_source_a3
  • content_owner_cards_a1
  • content_owner_playlist_device_os_a2
  • content_owner_playlist_playback_location_a2
  • content_owner_playlist_traffic_source_a2
  • playlist_device_os_a2
  • playlist_playback_location_a2
  • playlist_traffic_source_a2
  • channel_annotations_a2
  • and 22 more
Weld MCP server

Ask your agent.
It queries PostgreSQL for you.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the YouTube Analytics context, finds the tables it needs and runs the query in PostgreSQL.

Claude CodeOpus 5
>

How many content_owner_basic_a4 rows do we have in PostgreSQL?

Reading the YouTube Analytics context first, so the query uses the right tables and keys.

●weld·search_available_references
⎿raw.youtube_analytics.content_owner_basic_a4
+ 51 more YouTube Analytics tables
●weld·get_reference_schema
⎿content_owner_basic_a4 · 37 columns
columns and types
●weld·run_query
⎿select count(*) from {{raw.youtube_analytics.content_owner_basic_a4}}
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from YouTube Analytics data in PostgreSQL
>Ask about your YouTube Analytics data
Under the hood

Technical considerations.
What to expect.

Incremental syncing
Weld uses incremental syncing where supported by the YouTube Analytics API, loading only new and updated records to minimize data transfer and warehouse costs.
Schema handling
Weld automatically manages schema changes. If YouTube Analytics adds new fields, they're detected and added to the corresponding PostgreSQL tables.
Data freshness
Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
Security
All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
FAQ

Common questions.
About YouTube Analytics to PostgreSQL.

Start syncing YouTube Analytics to PostgreSQL.

Set up your YouTube Analytics data pipeline in minutes. No credit card required. Free for 14 days.

YouTube AnalyticsSource
WeldWeld
PostgreSQLWarehouse