YouTube documents a 48 to 72 hour delay in Analytics API data and points to videos.list for live counts

What this means for you

YouTube's reporting system is a bit like a slow post office: the numbers for a day arrive two or three days later. YouTube has now written this down. So if your report tool shows fewer views than YouTube's own app for the last few days, nothing is broken. For up-to-the-minute view counts, tools should use a different, faster YouTube service.

The details

• Latency: "Data processing typically introduces a latency of 48 to 72 hours. Therefore, API responses do not contain data for the most recent days."
• End date truncation: "the endDate of your report only includes data up until the last day for which all requested metrics are fully processed."
• Real-time counts: for current view, like or comment counts of individual videos, use the Data API's videos.list instead of the Analytics API (or videos.batchGetStats, our entry).
• Monetary metrics: estimated revenue and ad performance metrics in channel reports work with the https://www.googleapis.com/auth/yt-analytics-monetary.readonly scope when the channel is in the YouTube Partner Program. Non-monetized channels return HTTP 403 Forbidden.
• Unsupported queries: invalid or mutually exclusive dimension, metric and filter combinations return HTTP 400 badRequest ("The query is not supported.").
• Bulk reports: video_id or channel_id columns can hold empty strings, to keep totals for deleted resources and to represent channel-level events.
• Type note: a documented limit, not a new restriction; Google does not say the behaviour changed on this date.

What to do next

• Business owners: Expect the last two or three days in YouTube reports to look low; check again later.
• Marketers and agencies: Add a "data is 2 to 3 days behind" note to YouTube client reports.
• Developers: Treat the latest days as incomplete, use videos.list for live counts, catch 403 on revenue metrics for non-YPP channels, and allow empty IDs in bulk report rows.