LinkedIn Learning

LinkedIn Learning is a popular content library that is capable of sending xAPI data about course completions to Watershed. This guide explains how to set up the connection. 

 Please note: This article relates to the LinkedIn Learning platform. If your organization has not yet migrated from Lynda.com, see our Lynda.com article, or speak to LinkedIn Learning about migrating.

Who can use this feature?

 User Roles

Global Admins can use this feature.

 Pricing 

Available on all plans (Essentials, Analyst, CLO, and Enterprise).

 Expertise

Both beginners and experts can use this feature.

How to connect

To connect LinkedIn Learning to Watershed you first need to add a new Activity Provider in Watershed [guide]. Don't forget to give the Activity Provider a memorable name like 'LinkedIn Learning'. Adding an Activity Provider will give you the endpoint url, key and secret which will look something like:

Endpoint

https://watershedlrs.com/api/organizations/1234/lrs/

Key

30db41b72cbffb

Secret

eb510b89c18441

Next, log in to Linkedin Learning as an administrator and in your LinkedIn Learning admin settings, select Settings from the navigation header.

From the side navigation menu, select Reporting APIs. Expand the xAPI section as shown below.

 Select the Add xAPI Integration button.

This will open a settings page as shown:

Complete the settings as follows:

Integration Name

The name of the integration, for example "Watershed".

User Type

The identifier to use for learners in the actor of the xAPI statements.

OAuth Server URL

Based on the Watershed Endpoint but replace /lrs/ with /oauth2/token

Tenant Server URL

Based on the Watershed Endpoint but add /statements on the end

Client ID

The Key from Watershed

Client Secret

The Secret from Watershed

See the sections below for more details about the URL settings and the User Type options. 

Once all settings have been populated correctly, click Enable to enable the connection. 

OAuth and Tenant Server URLs

The OAuth and Tenant Server URLs are both based on the start of the Watershed Endpoint but have slightly different endings.  

If your Watershed Endpoint is

https://watershedlrs.com/api/organizations/1234/lrs/

then your OAuth Server URL removes the 'lrs' and adds 'oauth2/token' to become

https://watershedlrs.com/api/organizations/1234/oauth2/token

and your Tenant Server URL adds 'statements' to become

https://watershedlrs.com/api/organizations/1234/lrs/statements

 Please note: Your Endpoint may begin with https://watershedlrs.eu, https://sandbox.watershedlrs.com, or another domain instead of https://watershedlrs.com.

User Types

The User Types drop-down has three options which determine how learners will be identified in xAPI statements sent to Watershed.

Email

The user's email address as used in LinkedIn Learning. Use this value if you are unsure what to select.

ID

The user's SSO Unique id value. Use this only if you are using SAML SSO to authenticate into LinkedIn learning and you are sure that the SSO id is the right value to use.

Username

SAML SSO custom attribute used solely for communication with external systems. Generally, you'll need to make a modification to your SSO configuration so you should only select this value if a LinkedIn Learning Technical Consultant explicitly recommends it.

 Hint: Use Email or discuss with the Watershed team if you are unsure what to select.

  When using email, the xAPI mbox identifier is used. The other two options use an account identifier with a homePage of "http://www.linkedin.com/learning/" 

Measures

Data from LinkedIn Learning is simply a record of who completed which courses and when. The following measures can be used with the data and visualized using the cards described in the next section. Measures are created using the Measure Editor.

Person Count

A count of how many people have completed the course. This is configured as shown below:

Course Count

A count of how many courses have been completed. This is configured as shown below:

Completion Count

How many times have courses been completed? This is configured as shown below:

First Completion

When was the course first completed by the learner? This is configured as shown below:

Most recent completion is configured similarly except that the Last aggregation is used instead of First.

Active Weeks

How many weeks did the learner complete something on? This measure works best with a date filter e.g. the last month. This is configured as shown below:

Reports

The measure above can be used in the following reports:

Completions over time

This report is shows the number of courses completed over time to give you insight into changes of usage. It is a Line chart using the Completion Count measure. It can be filtered to show just 1 course, a group or courses or all courses. Similarly, it can be filtered by people, groups and time periods.

Most active learners

This report shows which learners are most active. It is a Leaderboard using all of the measures defined above except person count (because person count per learner is always 1). It can be filtered to show just 1 course, a group or courses or all courses. Similarly, it can be filtered by people, groups and time periods.

Most completed content

The most completed content report gives you insight into what’s being completed the most. It is a heatmap using the Completion Count, Person Count and Active Weeks measures. Like the other reports, it can be filter by groups of people or courses and by time periods. For example, you might want to filter this card to show only the last month to see which courses have been most popular recently.