General
The YouTube channel integration allows videos created and rendered in Flight Control to be uploaded directly to your YouTube channel (created within your Google account) for use in Google Ads or DV360 campaigns.
While Google Ads and DV360 are used to manage the campaigns, the actual video ads are hosted on your YouTube channel, which serves as the video creative library.
Once you have integrated your YouTube channel with Flight Control and specified which channels to use in the campaign, the process is fully automated and requires no further action.
Note: There is a daily limit on the number of videos a channel can upload within a 24-hour period, but the exact number can vary by channel. This limit is a safety feature on YouTube. The limit is dynamic and can be influenced by a few factors, primarily your channel's history and verification status.
Prerequisite
- Have at least Owner or Manager access to the YouTube channel you want to connect with.
- For more information on granting permissions for your YouTube account, see YouTube's Change channel owners & managers with a Brand Account.
Connect a YouTube Channel with Flight Control
- Go to Account > Integrations.
- Click Add and select YouTube.
- Select a Google account to use and follow the on-screen prompts.
- Note: If the desired account isn't listed, it may indicate that access hasn't been granted. Please see the Prerequisites section above for more details.
If access is granted, the YouTube channel will display as a row in the Integrations table.
You can now use the YouTube channel integration for YouTube campaigns handled through Google Ads or DV360.
Security Aspects
This information is provided to help Clinch clients evaluate the security aspects of enabling the YouTube Channel Integration in Flight Control.
Clinch’s YouTube integration employs OAuth 2.0 tokens, issued when an authorized user with Editor permissions on the client's YouTube channel initiates the connection. This process generates an access token (with expiry) and a refresh token, which are securely stored and managed by Clinch according to industry best practices, ensuring the protection of client credentials and limiting access only to the necessary resources.
The OAuth token is configured with the following scopes, providing specific permissions:
- youtube.upload – allows the system to upload videos directly to the designated YouTube channel.
- youtube.readonly – allows viewing of the YouTube account and associated details necessary for the integration to function seamlessly.
Notably, the integration excludes the youtube.force-ssl scope, meaning it does not permit actions such as deleting or modifying video content, ratings, comments, or captions. This scope restriction reduces the risk of unauthorized or unintended changes to channel content.
If the initiating user from the client side wishes to revoke access, they can terminate the token at any time, immediately disabling integration access to their YouTube account.