YouTube Analytics

Requirements

YouTube does not begin producing reports until a reporting job has been created. The xGen platform either initiates a new reporting job or uses an existing one, depending on availability. Reports are generated with a 48-hour delay. For instance, a job created on September 1st will yield a report for that date by September 3rd. The report for September 2nd will become available on September 4th, and so on.

Additionally, YouTube provides historical data for the 30 days leading up to the creation of the reporting job. xGen automatically syncs all available historical data during setup.

How to Connect YouTube Analytics in xGen

1. Navigate to the Set up the source page.
2. Choose YouTube Analytics from the dropdown list under source types.
3. Assign a name for your YouTube Analytics connection to help identify it within xGen.
4. Provide the following OAuth credentials:
   • Client ID
   • Client Secret
   • Refresh Token
5. Click Set up source to initiate the integration. xGen will establish a connection and begin syncing data based on the reporting jobs.

Supported Sync Modes

Feature	Available?
Full Refresh Sync	✔ Yes
Incremental Sync	✔ Yes
SSL Encryption	✔ Yes
Channel-Level Reports	✔ Yes
Content Owner Reports	✖ Coming Soon
YouTube Data API	✖ Coming Soon

Available Data Streams

xGen supports the synchronization of the following datasets from YouTube Analytics:

• channel_annotations_a1
• channel_basic_a2
• channel_cards_a1
• channel_combined_a2
• channel_demographics_a1
• channel_device_os_a2
• channel_end_screens_a1
• channel_playback_location_a2
• channel_province_a2
• channel_sharing_service_a1
• channel_subtitles_a2
• channel_traffic_source_a2
• playlist_basic_a1
• playlist_combined_a1
• playlist_device_os_a1
• playlist_playback_location_a1
• playlist_province_a1
• playlist_traffic_source_a1

Performance Notes

YouTube API usage is subject to the following rate limits:

• 20,000 free requests per day
• 100 requests every 100 seconds
• 60 requests per minute

However, these limits are rarely a concern since data is pulled once and processed within the xGen application for filtering and querying, minimizing repeated API calls.