What's the difference between inserting a YouTube video vs embedding a YouTube video?

Options
Maureen.Barrow4
Maureen.Barrow4 Posts: 160 🌱
in Customer Enablement
Our Brightspace instance does not have an API key, so we can't use Insert Stuff > YouTube. As a workaround, our instructors use Insert Stuff > Enter Embed Code, then we use the embed URL from YouTube. What are the functional differences between these options? Are there benefits to using Insert Stuff > Youtube? Should I push my org to set up an API key?
Tagged:
· Share on FacebookShare on Twitter

Answers

  • Geoff.M.46
    Geoff.M.46 Posts: 11
    edited November 2022

    Hi @Maureen Barrow​,

     

    The main benefit to the Insert Stuff > YouTube workflow is that it can make use of the YouTube API to search for videos within ISF itself. In terms of just playback, there is no meaningful difference. So, in your case, it sounds like using the embed codes is fine.

     

    Hope this helps. Have a great day.

    · Share on FacebookShare on Twitter
  • Brock.Parks96
    Brock.Parks96 Posts: 16 🌱
    edited November 2022

    Hi - a related question. My impression has been that other advantages of using Insert Stuff for YouTube used to be that:

     

    1) It defaulted to using the https:// version of the video;

    2) It prevented recommended videos from appearing after playback completes.

     

    From a quick google, a few years back, YouTube has changed the parameter that used to allow the disabling of recommended videos (which now results, at best, in showing videos from the channel itself, rather than the anyone of YouTube).

     

    In short, I'm just wondering - is there anywhere in the Community or in the Documentation where any unique advantages of embedding through the LMS (rather than gathering embed code from YouTube itself) are detailed?

     

    (I can try and guess through observation and testing, but it would be nice to know if this is already covered in detail somewhere, and a summary would be useful to the whole community.)

     

    Thanks,

    Brock

     

     

    · Share on FacebookShare on Twitter

Categories