YouTube as a Listening source

Updated 

YouTube is one of the most sought-after channels for understanding the voice of netizens. Brands can monitor sentiment around mentions and enable use cases across PR, brand health, and marketing campaigns. 

YouTube listening in Sprinklr happens via two routes: Earned and Owned

  • Earned Listening: Competitor monitoring and industry conversations 

  • Owned Listening: Brand health, audience sentiment, and campaign analysis 

Sprinklr ingests YouTube data via public YouTube APIs.

YouTube Data Classification

Sprinklr supports the following YouTube entities:

  • Video Posts

  • Video Comments

  • Video Comments Reply

YouTube source capabilities

  • Source: YouTube

  • Source of data: Public YouTube APIs

  • Coverage: Publicly available native data

  • Latency (Keyword Authentication): Within ~2 hours

  • Latency (Source Verified Channels): 24–48 hours

  • Historical Data (Keyword Auth): Past 7 days

  • Historical Data (Source Verified): Going-forward only

  • Backfill support: Yes

  • Author/ Profile metadata details: Yes (Earned & Owned)

  • Location Metadata: Not supported

AI Enriched Attributes

  • Language

  • Sentiment

  • Emotions & Emotion Categories

  • Gender

YouTube data entities in Social Listening

Data Entitiy

Type

Description

Earned Engagement

Metric

Views + Likes + Comments

View count

Metric

Total views on a video

Likes Count

Metric

Total likes on a video

Distinct Users

Metric

Not accurate due to API limitations

Comments Count

Metric

Total comments on a video

Ways to Listen to YouTube in Sprinklr

Sprinklr supports two listening routes for YouTube:

Case 1

Source Verified Channels

  • Use Case: Monitor specific YouTube channels or videos for competitors, influencers, or priority creators.

  • Steps

    • Raise a Source Verification request with the list of YouTube channel or video URLs.

      Once verification is completed, create:

      • Domain-based topics, or

      • Query-based topics using YouTube as the source.

  • Scope and Limitation

    • Data is pulled via YouTube APIs and is subject to quota limitations.

    • Engagement metrics are captured only at ingestion time.

    • No historical backfill is supported for source-verified routes.

Case 2

Keyword Authentication Route (Updated)

  • Use case: Monitor share of voice, brand sentiment, and competitor conversations across YouTube using keywords.

  • Current & Correct Workflow

    • Users can register YouTube keywords via the YouTube Keyword Manager

    • The YouTube Keyword Manager is available under Listening Settings

    • Feature availability is controlled via the DP: LST_YOUTUBE_KEYWORDS_MANAGER_ENABLED

    • Keyword registration is self-serve

    • No support ticket or Product team involvement is required.

  • Once keywords are registered:

    • Videos containing the keywords in:

      • Title, or

      • First ~150 characters of the description

        are fetched

    • All comments and replies on those videos are fetched, regardless of keyword presence

    • Data is ingested:

      • On a going-forward basis.

      • Plus past 7 days of historical data.

  • Scope & Limitations

    • Requires at least one active YouTube account in the workspace

    • Maximum keywords supported:

      • 15 keywords per active YouTube account

    • Proximity operators are not supported

    • Engagement metrics (likes, views, comments) refresh every ~2 hours

    • Coverage is representative; up to ~90% coverage observed in POCs

Creating Topics for YouTube Listening

Query-based Topic

  • Select YouTube as the social channel in Topic Creation

  • Apply filters as required

  • Widgets can also be filtered by Source: YouTube

Domain-based Topic

  • Add YouTube URLs in the Setup Profile section.

  • Select YouTube as the source.

  • Useful for source-verified channels or specific videos.

Backfill Support

Route 

Backfill 

Keyword Authentication 

Past 7 days 

Source Verified Channels 

Not supported 

Important Notes & FAQs

  • YouTube Listening is representative, not exhaustive

  • Native API quota limitations may result in missed mentions

  • Deleted native posts remain in Sprinklr unless deletion signals are received

  • Keyword Authentication is the recommended approach for broader coverage and lower latency