Skip to main content

​
Introduction

YouTube Public pulls publicly visible channel and video metrics for YouTube channels the customer designates as monitoring targets. The customer connects a Google account so the connector can call the YouTube Data API v3; the channels being monitored do not need to belong to the connecting Google account. The connector is intended for competitive monitoring, brand-mention tracking, and influencer analytics across YouTube channels the customer does not own. It reads the public, owner-authentication-free surface of the YouTube Data API v3, so it is limited to data that YouTube exposes publicly. As a public-data connector, engagement metrics and audience breakdowns are standardized so widgets can aggregate alongside owned-account sources without additional configuration. To connect this data source, see How to connect YouTube Public to Adriel.

​
Data refresh strategy

​
Architecture data

The list of monitored YouTube channels is configured per data source by the customer. Channel-level and video-level rows are upserted into a per-asset cache: existing non-null values are preserved when a new fetch returns nulls, and new fields encountered on the YouTube response are added as new columns automatically. Changes to the monitored channel list take effect on the next scheduled refresh.

​
Reports data

This connector follows a simple-cache pattern: every day, for each collection, the data is refetched and the cache is overwritten. The default refresh runs daily at 7:00 PM (UTC). Public YouTube counts (for example subscribers, channel views, and video views) are snapshot values captured at each refresh; video and channel rows are stored without date boundaries. A manual refresh is available from the connection page, rate-limited to 1 refresh per data source per calendar day.

​
Architecture levels

Channel → Video A data source supplies one or more public YouTube channels to monitor, and the channel is the unit of monitoring. Per-video rows are fetched for the videos that resolve under each tracked channel.

​
Metrics

How to read the columns Data type uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean. API Key in code style like statistics.viewCount is the literal YouTube Data API v3 field the value maps to. Italic text describes how a value is produced when it doesn’t map cleanly to a single API field.

​
Channel metrics

​
Video metrics

​
Influencer analytics

These fields expose the same underlying channel and video data under influencer-analytics labels for creator and brand-mention reporting.

​
Breakdowns

​
Channel and video

Between one and two breakdowns can be selected per query. Selecting zero, or more than two, is not supported (see Limitations).

​
Limitations

  • Breakdown count — a query must use one or two breakdowns. Selecting none, or more than two, returns an error.
  • API quota against the connecting GCP project — YouTube Data API v3 charges quota units against the Google Cloud project linked to the OAuth grant. The default quota is 10,000 units per day and a typical list read costs 1 unit (YouTube Data API — Quota usage), so heavy multi-channel monitoring can exhaust the cap and surface as stale or missing data. Scaling further requires a quota increase from Google.
  • Snapshot semantics, not time series — channel and video counts are captured at refresh time and stored as daily snapshots. There is no historical backfill for periods before a channel was added; trend data accumulates from the day the channel was first tracked.
  • Cache preserves prior values on null — upserts keep existing values when a fetch returns null, so transient gaps in the YouTube API response (for example rate-limited reads or momentary outages) do not overwrite previously cached values.
  • Deleted, private, or region-blocked videos — videos that are removed, set to private, or geo-restricted in the region where the API call originates stop returning new metrics. Cached snapshots from earlier refreshes remain queryable until the situation changes.
  • Forced consent screen — the OAuth flow always shows the Google consent screen, even for accounts that have authorized YouTube before, so that a fresh refresh token is issued on every authorization.

​
API references

​
See also