Youtube Content Owner Transfers | Bigquery Data Transfer Service

8/23/2020 YouTube Content Owner transfers | BigQuery Data Transfer Service

YouTube Content Owner transfers

The BigQuery Data Transfer Service for YouTube allows you to automatically schedule and manage recurring load jobs for YouTube Content Owner reports.

Suppoed Repos

The BigQuery Data Transfer Service for YouTube Content Owner reports currently supports the following reporting options:

Content Owner Reports (https://developers.google.com/youtube/reporting/v1/reports/content_owner_reports)

System-Managed Reports

Overview (https://developers.google.com/youtube/reporting/v1/reports/system_managed)

Reports (https://developers.google.com/youtube/reporting/v1/reports/system_managed/reports)

Fields (https://developers.google.com/youtube/reporting/v1/reports/system_managed/elds)

For information on how YouTube Content Owner reports are transformed into BigQuery tables and views, see YouTube Content Owner report transformations (/bigquery-transfer/docs/youtube-content-owner-transformation).

Reporting Support option

SupportedJune 18, 2018 (https://developers.google.com/youtube/reporting/revision_history#june-18-2018) API version

Schedule Daily, around 14:45 UTC

You can congure the time of day

Refresh Last 1 day window Not congurable.

Maximum 30 days

https://cloud.google.com/bigquery-transfer/docs/youtube-content-owner-transfer/ 1/7 8/23/2020 YouTube Content Owner transfers | BigQuery Data Transfer Service

backll As of July 2018, YouTube reports containing historical data are available for 30 days from the time duration that they are generated. Reports that contain non-historical data are available for 60 days after the policy change. For more information, see Historical data (https://developers.google.com/youtube/reporting/v1/reports/#historical-data) in the YouTube Reporting API documentation.

Before you begin

Before you create a YouTube Content Owner transfer:

Verify that you have completed all actions required to enable the BigQuery Data Transfer Service (/bigquery-transfer/docs/enable-transfer-service).

Create a BigQuery dataset (/bigquery/docs/datasets) to store the YouTube data.

Verify that you have a YouTube Content Owner (https://support.google.com/youtube/answer/6301188?hl=en) account. A YouTube Content Owner is not the same as a YouTube channel. Typically, you only have a YouTube Content Owner account if you manage many different channels.

If you intend to create transfers using the classic BigQuery web UI, allow pop-ups from bigquery.cloud.google.com so you can view the permissions window. You must allow the BigQuery Data Transfer Service permission to manage your YouTube reporting data for the transfer to succeed.

If you intend to setup transfer run notications for Pub/Sub, you must have pubsub.topics.setIamPolicy permissions. Pub/Sub permissions are not required if you just set up email notications. For more information, see BigQuery Data Transfer Service run notications (/bigquery-transfer/docs/transfer-run-notications).

Required permissions

Ensure that the person creating the transfer has the following required permissions:

BigQuery:

bigquery.transfers.update permissions to create the transfer

bigquery.datasets.update permissions on the target dataset

https://cloud.google.com/bigquery-transfer/docs/youtube-content-owner-transfer/ 2/7 8/23/2020 YouTube Content Owner transfers | BigQuery Data Transfer Service

The bigquery.admin predened, project-level IAM role includes bigquery.transfers.update and bigquery.datasets.update permissions. For more information on IAM roles in BigQuery Data Transfer Service, see Access control reference (/bigquery-transfer/docs/reference/access-control).

YouTube:

YouTube Content Manager or YouTube Content Owner.

A Content Manager is granted rights to administer YouTube content for a Content Owner. A Content Owner is an umbrella account that owns one or more YouTube channels and the videos on those channels.

Hide revenue data is unchecked in YouTube Content Owner report settings.

For revenue-related reports to transfer, the YouTube reports permission setting Hide revenue data should be unchecked for the user creating the transfer.

Seing up a YouTube Content Owner transfer

Setting up a YouTube Content Owner transfer requires a:

https://cloud.google.com/bigquery-transfer/docs/youtube-content-owner-transfer/ 3/7 8/23/2020 YouTube Content Owner transfers | BigQuery Data Transfer Service

Content Owner ID: Provided by YouTube. When you log in to YouTube as a Content Owner or Manager, your ID appears in the URL after o=. For example, if the URL is https://youtube.com/dashboard?0=AbCDE_8FghIjK, the Content Owner ID is AbCDE_8FghIjK. For more information on your Content Manager account, see: Congure Content Manager account settings (https://support.google.com/youtube/topic/6032636?hl=en&ref_topic=24324).

Table Sux: A user-friendly name for the channel provided by you when you set up the transfer. The sux is appended to the job ID to create the table name, for example reportTypeId_sux. The sux is used to prevent separate transfers from writing to the same tables. The table sux must be unique across all transfers that load data into the same dataset, and the sux should be short to minimize the length of the resulting table name.

If you currently use the YouTube Reporting API (https://developers.google.com/youtube/reporting/v1/reference/rest/) and have existing reporting jobs, the BigQuery Data Transfer Service loads your report data. If you do not have existing reporting jobs, setting up the transfer automatically enables YouTube reporting jobs.

To set up a YouTube Content Owner transfer:

ConsoleClassic UI (#classic-ui)bq (#bq)API (#api)

1. Go to the BigQuery web UI in the Cloud Console.

Go to the Cloud Console (https://console.cloud.google.com/bigquery)

2. Click Transfers.

3. Click Create Transfer.

4. On the Create Transfer page:

In the Source type section, for Source, choose YouTube Content Owner.

In the Transfer cong name section, for Display name, enter a name for the transfer such as My Transfer. The transfer name can be any value that allows you to easily

https://cloud.google.com/bigquery-transfer/docs/youtube-content-owner-transfer/ 4/7 8/23/2020 YouTube Content Owner transfers | BigQuery Data Transfer Service

identify the transfer if you need to modify it later.

In the Schedule options section, for Schedule, leave the default value (Start now) or click Start at a set time.

For Repeats, choose an option for how often to run the transfer.

Daily (default)

Weekly

Monthly

Custom

On-demand

For Start date and run time, enter the date and time to start the transfer. If you choose Start now, this option is disabled.

In the Destination settings section, for Destination dataset, choose the dataset you created to store your data.

https://cloud.google.com/bigquery-transfer/docs/youtube-content-owner-transfer/ 5/7 8/23/2020 YouTube Content Owner transfers | BigQuery Data Transfer Service

In the Data source details section:

For Content owner ID, enter your Content Owner ID.

For Table sux, enter a sux such as MT.

(Optional) In the Notication options section:

Click the toggle to enable email notications. When you enable this option, the transfer administrator receives an email notication when a transfer run fails.

For Select a Pub/Sub topic, choose your topic (/pubsub/docs/overview#types) name or click Create a topic. This option congures Pub/Sub run notications (/bigquery-transfer/docs/transfer-run-notications) for your transfer.

5. Click Save.

If you are setting up YouTube reporting jobs for the rst time, you will experience a delay of up to 48 hours befo rst reports are ready. For more information, see Create a reporting job s://developers.google.com/youtube/reporting/v1/reports/#step-3-create-a-reporting-job) in the YouTube Repo ocumentation.

Querying your data

When your data is transferred to BigQuery, the data is written to ingestion-time partitioned tables. For more information, see Partitioned tables (/bigquery/docs/partitioned-tables).

https://cloud.google.com/bigquery-transfer/docs/youtube-content-owner-transfer/ 6/7 8/23/2020 YouTube Content Owner transfers | BigQuery Data Transfer Service

If you query your tables directly instead of using the auto-generated views, you must use the _PARTITIONTIME pseudo-column in your query. For more information, see Querying partitioned tables (/bigquery/docs/querying-partitioned-tables).

Troubleshooting YouTube Content Owner transfer setup

If you are having issues setting up your transfer, see YouTube transfer issues (/bigquery-transfer/docs/transfer-troubleshooting#youtube_transfer_issues) in Troubleshooting BigQuery Data Transfer Service transfer setup (/bigquery-transfer/docs/transfer-troubleshooting).

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License (https://creativecommons.org/licenses/by/4.0/), and code samples are licensed under the Apache 2.0 License (https://www.apache.org/licenses/LICENSE-2.0). For details, see the Google Developers Site Policies (https://developers.google.com/site-policies). Java is a registered trademark of Oracle and/or its aliates.

Last updated 2020-07-21 UTC.

https://cloud.google.com/bigquery-transfer/docs/youtube-content-owner-transfer/ 7/7