Advanced Analytica Advanced Analytica: IBOM
← All connectors
YouTube Analytics logo

Source connector

YouTube Analytics

Set up YouTube Analytics as a source and move its data into your chosen destination.

Version 2.0.3 certified generally available

YouTube Analytics

Use this guide to set up the YouTube Analytics source connector and find reference information.

Upgrade

Before upgrading from a version earlier than 2.0.0, review the migration guide. Version 2.0.0 changes metric field types across seven report streams. Preserve historical data before clearing or rebuilding affected streams. You can’t download reports again once they fall outside YouTube’s retention window.

Prerequisites

Authorise a Google account that owns or manages a YouTube channel. Accounts without an associated channel can’t access YouTube Reporting API data.

For Airbyte Open Source, you need a Google Cloud project with the YouTube Reporting API enabled. You also need an OAuth 2.0 Client ID, Client Secret, and Refresh Token with the https://www.googleapis.com/auth/yt-analytics.readonly scope. See Set up YouTube Analytics for instructions. Airbyte Cloud users authenticate with OAuth during setup and don’t need to provide these credentials. The Airbyte Cloud consent screen requests the yt-analytics.readonly and yt-analytics-monetary.readonly scopes.

YouTube partners can also provide a Content Owner ID to retrieve data for that content owner.

Set up the connector

Prepare YouTube access, then add the source in Airbyte.

Set up YouTube Analytics

Airbyte Cloud users can authorise their Google account during source setup. For Airbyte Open Source, create OAuth credentials for the Google account that owns or manages your YouTube channel:

  1. Create or select a Google Cloud project and enable the YouTube Reporting API.
  2. Configure the OAuth consent screen and add the https://www.googleapis.com/auth/yt-analytics.readonly scope. If the app’s publishing status is Testing, add the channel’s Google account as a test user. Google states that refresh tokens for External apps in Testing status expire after 7 days. See refresh token expiration.
  3. Create an OAuth client ID with the application type Web application. Add https://developers.google.com/oauthplayground as an authorised redirect URI. Then copy the Client ID and Client Secret.
  4. Open the OAuth 2.0 Playground. Select the gear icon, choose Use your own OAuth credentials, and enter the Client ID and Client Secret. In Step 1, enter https://www.googleapis.com/auth/yt-analytics.readonly as the scope and select Authorize APIs. Sign in with the channel’s Google account. In Step 2, select Exchange authorization code for tokens and copy the Refresh token.

For more information, see Google’s YouTube Reporting API authorization guide.

Add the connector in Airbyte

Airbyte Cloud

  1. Log in to Airbyte Cloud.
  2. From the left navigation bar, select Sources, then select + new source.
  3. Name the source and select YouTube Analytics from the source type list.
  4. Select Authenticate your account and sign in with the Google account that owns or manages the channel. Then authorise access.
  5. Select Set up source.

Airbyte Open Source

  1. From the left navigation bar, select Sources, then select + new source.
  2. Name the source and select YouTube Analytics from the source type list.
  3. Enter the Client ID, Client Secret, and Refresh Token you created in Set up YouTube Analytics.
  4. Optionally, enter a Content Owner ID.
  5. Select Set up source.

Content Owner ID

The optional Content Owner ID field is for YouTube partners participating in the YouTube Partner Program. These partners manage multiple channels through a content owner account. This includes Multi-Channel Networks (MCNs) and media companies managing content across multiple YouTube channels.

  • If you own a regular YouTube channel, leave this field empty. The connector retrieves data for the channel associated with your OAuth credentials.
  • If you’re a YouTube partner with a content owner account, enter your content owner ID. The connector then retrieves data for channels managed under that account.
  • To find your content owner ID, check the URL while signed in to YouTube Studio. Look for the o= parameter. You can also use the YouTube Content ID API or contact your YouTube partner manager.

Supported sync modes

The YouTube Analytics source connector supports these sync modes:

FeatureSupported?
Full Refresh SyncYes
Incremental SyncYes — report streams; report_types is full refresh only

Supported streams

Each report stream provides one YouTube bulk report. Incremental syncs only download report files YouTube created after the previous sync. They also download reissued files containing corrected data. A reissued file replaces an earlier report covering the same days, so use Incremental | Append + Deduped for report streams. With Incremental | Append, the destination keeps both the original and corrected rows.

Report availability

During the first sync, Airbyte creates a reporting job for each selected report without an existing job. YouTube starts generating reports after creating a job. The first report is typically available within 48 hours and covers the day the job was scheduled. For example, schedule a job on September 1, 2015, and the September 1 report becomes available on September 3. The September 2 report is posted on September 4.

When scheduling a new job, YouTube also generates historical reports for the preceding 30 days. Historical reports are typically posted within a couple of days, and Airbyte syncs the available historical data. Therefore, a first sync that creates new jobs might return no records from report streams.

YouTube keeps generated reports available for 60 days. Historical reports remain available for 30 days. See the YouTube Reporting API report documentation for details.

YouTube API Services disclosure

This connector uses YouTube API Services to retrieve data from YouTube. By using the connector, you agree to the YouTube Terms of Service.

Google provides YouTube API Services. To understand how Google handles data, review the Google Privacy Policy.

With OAuth 2.0 authentication, this connector accesses authorised user data. You can revoke its Google account access at any time through the Google security settings page. To delete previously synced YouTube data, remove it from your configured destination. Removing the Airbyte connection or revoking Google access doesn’t delete data already stored in the destination.

Rate limits and quotas

The connector limits requests to 60 per minute. YouTube might also return a rate-limit error. The connector automatically retries rate-limited requests and Google server errors (HTTP 5xx) after 30 seconds. Repeated rate-limit errors cause the sync to fail. If your project’s daily YouTube API quota is exhausted, the sync stops with Daily YouTube API project quota is exhausted.. Try again when quota becomes available.

Airbyte Cloud uses an Airbyte Google Cloud project with a YouTube API quota shared across Cloud connections. Airbyte Open Source uses the quota from the Google Cloud project configured for the source. Check your project’s quota page in Google Cloud for current limits.

IP allow list

If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

Performance

Each selected report stream requests its reporting job and available reports, then downloads every available report file. Selecting more report streams can use more of your project’s quota.

The optional Number of Concurrent Workers setting controls how many report files download in parallel. The default is 2, and the maximum is 4. More workers can shorten syncs containing many report files. However, every worker shares the same request limit and YouTube API quota. Higher values can therefore reach rate limits sooner.

Limitations and troubleshooting

  • 401: no channel associated with the Google account. The error starts with The authorized Google account does not appear to have an associated YouTube channel.. Use an account that owns or manages a YouTube channel. When connecting as a content owner, also confirm that the Content Owner ID is correct.
  • 401: credentials rejected. The error starts with Google rejected the YouTube Reporting API credentials:, followed by Google’s message. Re-authenticate the source. If the error continues, the Google account probably has no associated YouTube channel.
  • 403: access denied. The error starts with The YouTube Reporting API denied access:, followed by Google’s message. Confirm that the authorised Google account owns or manages the channel. Also confirm that the OAuth consent screen includes the required scope. If you set a Content Owner ID, confirm that the account can act for that content owner.
  • Refresh token is invalid or expired. Google rejected the refresh token, for example, because it was revoked or expired. Re-authenticate the source on Airbyte Cloud. For Airbyte Open Source, create a new refresh token.
  • Daily quota exhausted. If the sync reports Daily YouTube API project quota is exhausted., check your project’s quota. Try again when quota becomes available.
  • No rows on the first sync. YouTube might not have generated reports for newly created reporting jobs. Reports are typically available within 48 hours.
  • Skipped report files. YouTube might list a report file that can no longer be downloaded (HTTP 404). This usually happens after its retention period. The connector skips the file, records a message in the sync logs, and continues the remaining sync. The rows in that file aren’t synced.
  • Refresh token expires after 7 days. This applies to External OAuth apps in Testing status, even when the channel’s Google account is a test user. For ongoing syncs, move the app to In production according to Google’s publishing requirements. Then generate a new refresh token and update the source. While the app remains in Testing, generate a new refresh token whenever it expires.
  • Content-owner reports are not available as streams. The available streams are channel and playlist reports. To retrieve YouTube Data API information, use the separate YouTube Data connector.

Changelog

Expand to review
VersionDatePull RequestSubject
2.0.32026-11-0591124Promote the connector to Certified (Generally Available) support
2.0.22026-11-0491024Replace the icon with YouTube’s official icon from brand.youtube and remove the added ANALYTICS wordmark
2.0.12026-11-0490433Merge the report download error handlers into one handler; no behaviour change
2.0.02026-11-0489628Correct the declared types of report metric fields to match YouTube’s metric definitions
1.6.12026-11-0390800Update dependencies
1.6.02026-10-3089627Add the channel_reach_basic_a1 and channel_reach_combined_a1 streams for video thumbnail impressions and click-through rate
1.5.02026-10-2789629Emit report metrics as numbers, follow pagination on job and report listings, and give clearer errors for credential, permission and missing-file failures
1.4.72026-10-2790075Update dependencies
1.4.62026-10-2089472Update dependencies
1.4.52026-10-1388882Update dependencies
1.4.42026-10-0688106Update dependencies
1.4.32026-09-2987431Update dependencies
1.4.22026-09-2286879Update dependencies
1.4.12026-09-1586309Update dependencies
1.4.02026-09-1085335Restore incremental syncs for report streams, including reports that YouTube re-issues with corrected data
1.3.42026-09-0885727Update dependencies
1.3.32026-08-2684945Fail fast with a clear transient error when the daily YouTube API project quota is exhausted, and correctly classify rate-limited and server-error responses
1.3.22026-08-1884816Update dependencies
1.3.12026-08-1182653Update dependencies
1.3.02026-08-0483286Add new report_types stream, fix check failures, and explain 401s caused by a Google account with no YouTube channel
1.2.122026-07-3082712Fix setup check failure by pointing the connection check at the always-available channel_basic_a3 report instead of channel_annotations_a1
1.2.112026-07-1482069Update dependencies
1.2.102026-06-3081330Update dependencies
1.2.92026-06-2380732Update dependencies
1.2.82026-06-1680106Update dependencies
1.2.72026-06-0979579Update dependencies
1.2.62026-06-0279073Update dependencies
1.2.52026-04-2877489Update dependencies
1.2.42026-04-2174693Update dependencies
1.2.32026-02-2473149Update dependencies
1.2.22026-02-0672635Update dependencies
1.2.12026-01-2072048Update dependencies
1.2.02026-01-1471377Promoting release candidate 1.2.0-rc.2 to a main version.
1.2.0-rc.22026-01-0971244Fix incorrect report_id key and remove additional error message
1.2.0-rc.12026-01-0771169Add optional content_owner_id config for multi-channel support and improve error handling
1.1.22025-12-1870715Update dependencies
1.1.12025-12-0264964Update dependencies
1.1.02025-11-1769352Promoting release candidate 1.1.0-rc.1 to a main version.
1.1.0-rc.12025-11-1042838Migrate to Manifest-only
1.0.02025-10-3066558Update deprecated channel and playlist BULK reports
0.2.02025-05-2953196Update check connection and empty responses
0.1.72025-02-2754696Update requests-mock dependency version
0.1.62024-06-1739529Pin CDK version to 0.38.0
0.1.52024-06-1338546[autopull] base image + poetry + up_to_date
0.1.42023-05-2626420Migrate to advancedAuth
0.1.32022-10-0717454Added custom backoff logic
0.1.22022-09-2917399Fixed 403 error while check connection
0.1.12022-08-2215744Fix channel_basic_a2 schema fields data type
0.1.02021-11-197407Initial Release
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.