YouTube Analytics Connector

Start for free View documentation

4.8 on G2

Weld · Data Sources

YouTube AnalyticsYour warehouseLive

content_owner_basic_a437 columnsSynced

content_owner_asset_basic_a336 columnsSynced

channel_basic_a335 columnsSynced

content_owner_asset_province_a331 columnsSyncing

content_owner_province_a330 columnsQueued

Lands in

Agent context over MCP

How it works

Set up in minutes.
No code, no maintenance.

YouTube Analytics

Data source

Authenticating...

Ready to connect

Overview

YouTube Analytics in your warehouse.
Ready for your agents.

This integration connects YouTube Analytics with your destination, part of the broader cloud-computing platform. By integrating YouTube Analytics with your destination, you can consolidate your video performance data into a single, unified repository, allowing for advanced data analysis and reporting. Weld's YouTube Analytics connector is fully managed: it extracts data from YouTube Analytics, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

Agent context

YouTube Analytics data schema.
The map your agents read.

Every table, field and relationship Weld syncs from YouTube Analytics is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables: 52
fields: 921

52 tables

Open the schema explorer Open the full schema explorer

Weld MCP server

Ask your agent.
It already knows YouTube Analytics.

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

Agent contextYouTube Analytics tables, fields and joins
QuerySQL against your warehouse
OperateCheck, rerun and refresh syncs

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCPAgent contextYouTube Analyticstables52fields921

How many content_owner_basic_a4 rows do we have in our YouTube Analytics data?

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

date, channel_id

●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 your warehouse

>Ask about your YouTube Analytics dataMCP

Destinations

Load YouTube Analytics into any warehouse.
Set up in minutes, no code.

Resources

Everything you need.
To get started.

Documentation

YouTube Analytics setup guide

Step-by-step instructions to configure and start syncing.

MCP server

Connect your agents

Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.

Weld Connect API

Build custom connectors

Use the Weld Connect API to build and publish your own connector.

FAQ

Common questions

Answers to frequently asked questions about Weld connectors.

Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create YouTube Analytics connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

Explore Weld Connect API reference

POST/elt_syncs

# Create a YouTube Analytics ELT sync
curl -X POST https://connect.weld.app/elt_syncs \
  -H "x-api-key: $API_KEY" \
  -d '{
    "connection_id": "conn_abc123",
    "integration_id": "youtube-analytics",
    "destination_schema_name": "youtube-analytics_data",
    "sync_interval": "0 * * * *"
  }'
▌