Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

YouTube Analytics - Add Reach reports (channel_reach_basic_a1 / channel_reach_combined_a1)

Planned
ABEMA ABEMA User
  • Edited

Connector name: YouTube Analytics

Table name:
channel_reach_basic_a1
channel_reach_combined_a1
content_owner_reach_basic_a1
content_owner_reach_combined_a1.

API documentation link: https://developers.google.com/youtube/reporting/v1/reports/channel_reports#reach-basic

Additional details:

Why we need this ASAP & Why it should be a quick win:

  • Urgent timing constraint: YouTube only generates historical reports for the 30 days prior to the reporting-job creation. Any delay means permanent data loss for our business, so we strongly request this to be added as soon as possible.

  • Simple implementation: Since the connector already uses the YouTube Reporting API with the correct OAuth scope, this should only require adding these new tables to your existing bulk report sync mechanism, rather than building a new API integration.

• Revision history (Jan 15, 2026 entry): https://developers.google.com/youtube/reporting/revision_history
• Channel reach reports: https://developers.google.com/youtube/reporting/v1/reports/channel_reports#reach-basic
• Content owner reports: https://developers.google.com/youtube/reporting/v1/reports/content_owner_reports

• Full report list: https://developers.google.com/youtube/reporting/v1/reports/full_report_list

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Lucas Alexander Fivetranner

    Hi all,

    Thanks for the detailed request and for flagging the timing concern. The four reach reports you listed (channel_reach_basic_a1, channel_reach_combined_a1, content_owner_reach_basic_a1, content_owner_reach_combined_a1) are on our roadmap, and engineering work is in progress to add them to the YouTube Analytics connector. The new tables will expose the video_thumbnail_impressions and video_thumbnail_impressions_ctr metrics described in the reach reports documentation.

    On the historical data point: the 30-day limit applies on our side as well, since the connector relies on the same reporting-job API. Once these tables are available, history will only backfill to 30 days before the sync begins.

    I can't commit to a release date, but I've linked your request to the engineering ticket so it stays attached to the work, and we'll follow up here when the tables ship.

    Cheers,
    Luke

  • Matthew Macwan User

    Agreed, this would be a super valuable integration