Skip to main content Skip to complementary content

YouTube Analytics

The Qlik YouTube Analytics Connector allows you to perform advanced reporting for YouTube channels and videos that you own or administer. You can create your own customized reports and view them in your QlikView and Qlik Sense apps.

Tip note

The Qlik Web Connectors help you connect to different data sources and fetch data in the same way. Learn how to authenticate a data source connection and how to use tables to fetch data.

Connecting to data sources

Supported offerings

  • QlikView

This connector must be installed separately.

Ways to access your data

To use the Qlik YouTube Analytics Connector you must have a YouTube account with administrative privileges for the channels and videos you want to report on. You must use this account to authenticate the connector.

After authenticating the connector, a number of tables are available:

  • MyChannels - Lists information about your YouTube channels, including the channel IDs.
  • Report - Creates a report about your YouTube channels according to the Metrics and Dimensions set in Parameters.


To generate a report using the YouTube Analytics API you need to have your channel IDs. These can be found in your YouTube account under Advanced, or by running the MyChannels table within Qlik Web Connectors.

To enter the channel ID, select the Report table and click on Parameters. Type the ID in the ids field in the following format:


To understand the metrics and dimensions available, see the YouTube Analytics and Reporting API documentation.

Valid combinations of content owner reports and channel reports are found on the following pages:

These pages also provide information on the use of the optional parameters: Filters, Sort, and Max Results.

Content owner reports are only accessible to YouTube content partners who participate in the YouTube Partner Program.

Quota limits

The YouTube Analytics API has some quota limits, although there are no set levels.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!