LinkedIn Learning Hub: LMS Integration and Content Integration (IT - Enabled) Guide

Learning Hub Overview

This document aims to guide HRIT teams on how to integrate external data from an LMS or Content Partner into LinkedIn Learning Hub. The two use cases outlined below illustrate how LinkedIn Learning's Technical Consulting team partners with your team to determine the optimal integration design for your organization.

Benefits

This integration brings in content from LMS-hosted resources (e.g. assignments, courses, events, and so on) and Content Partners into LinkedIn Learning Hub. It drives learner engagement and offers learners a single, intuitive platform to discover content most relevant to their needs and goals.

Use Case 1

You (the admin) send the raw CSV files via an automated method to the LinkedIn Learning Hub SFTP endpoint. Learning Hub then transforms the raw data on a continuing basis per the Hub ingestion schema.

learning-hub-mapping-layer-flow-chart

The Mapping Layer in the above diagram transforms raw data into data as per LinkedIn Learning Hub's ingestion schema.

Use Case 1 Description

You need to send the raw data from the your organization's infrastructure to the LinkedIn Learning SFTP endpoint, from which Learning Hub ingests the data and transforms it. As an admin, you automate the data drop mechanism.

Use Case 1 Process

To automate the transformation of your system's data into Learning Hub, take the following steps:

  1. Extract the raw data from your LMS/Content Partner while referring to the ingestion schema as guidance.
  2. Drop the raw data to the LinkedIn Learning SFTP endpoint on a daily cadence basis.
  3. Once the raw data is sent to the SFTP end point, the configuration-based mapping layer in the Learning Hub transforms the data into the ingestion schema before ingestion occurs.

Use Case 1 Roles & Responsibilities

Customer Admin's Responsibility LinkedIn Learning's Responsibility
- Availability of IT resources for automation, SFTP handshake, allowing access to LinkedIn IPs, and so on. - Scoping to get the data to LinkedIn Learning Hub SFTP endpoint
- Data extraction from the LMS/Content Partner - Transformation of the files once they are pushed to the Learning Hub SFTP endpoint by the customer
- Customers would need to be able to provide us a quality sample (fake data) of what their actual data may look like in order for us to be able to ensure the mapper has the correct output - Ingestion of transformed data
- Testing SFTP connectivity - Validating script transformations and content sync
- Validating data transfer to Learning Hub per Learning Hub SFTP documentation - Troubleshooting content sync issues (if they occur)
- Troubleshooting of issues related to data extraction from the LMS/Content Partner

Field By Field Mapping Exercise (Use Case 1 only)

  • The LinkedIn Learning Technical Consulting Team requests a field-by-field document from customers, on which files will be sent to us and which fields (and their format) each file will contain. Please refer to the sample format below as a guidance.
Field Description Type Required Default Constraints Comments
Language Language of the content String Yes en_us en_us, es_es, fr_f Format is locale
  • LinkedIn Learning and customers align on ContentType mapping, i.e., which incoming content type is mapped to which LinkedIn Learning content type. The customer and the LinkedIn Learning Technical Consulting Team decide what types should map to which LinkedIn Learning content types. Please refer to the sample below for guidance. The customer approves the ContentType mapping process.
Source Content Type Learning Hub Content Type
Curriculum COURSE
Event EVENT
External Training EVENT
Material DOCUMENT
Note DOCUMENT
Online Class EVENT
Session EVENT
Video VIDEO
  • Once LinkedIn Learning has the customer's file format documentation, the Technical Consulting Team creates a field-by-field mapping table so the team can evaluate how the mapping script matches each customer field to a standardized template.

  • The customer provides the LinkedIn Learning Technical Consulting Team quality dummy data, which resembles the customer's Production data, so LinkedIn Learning can validate its transformation scripts with it.

  • Once the Technical Consulting Team knows which fields (and formats) the customer expects, how each field is mapped to the standardized template, and which customer content type is mapped to the LinkedIn Learning content type, the Technical Consulting Team codes and tests the mapping script.

Use Case 2

The customer transforms the data as per the Learning Hub ingestion schema, and sends the transformed data to the Learning Hub SFTP endpoint for ingestion.

learning-hub-automated-data-transformation-process

Use Case 2 Description

The customer transforms the data as per Learning Hub ingestion schema and automates the transformed data drop mechanism to the Learning Hub SFTP endpoint for ingestion.

Use Case 2 Process

  1. The LinkedIn Learning Account Team passes the Learning Hub ingestion schema file to the customer.
  2. The customer extracts the raw data from the LMS/Content Partner based on ingestion schema.
  3. The admin transforms the raw data into the expected ingestion schema format.
  4. The admin automates sending the transformed data to the LinkedIn Learning Hub SFTP endpoint on a daily cadence basis.

Use Case 2 Roles & Responsibilities

Customer Admin's Responsibility LinkedIn Learning's Responsibility
- Availability of IT resources for transformation, automation, SFTP handshake, allowing access to LinkedIn IPs, and so on - Scoping to get the data to Learning Hub SFTP endpoint
- Data extraction from the LMS/Content Partner - Ingestion of transformed data
- Data transformation as per ingestion schema - Validation of data transformations once the customer pushes the files to the Learning Hub SFTP endpoint, and content sync
- Automation of the transformed data drop to the Learning Hub SFTP endpoint - Troubleshooting content sync issues (if they occur)
- Testing SFTP connectivity
- Validating data transfer to Learning Hub as per Learning Hub SFTP documentation
- Troubleshooting issues related to data extraction from the LMS/Content Partner
- Troubleshooting issues related to data transformation

FAQs

Q.: What data do you need?

A.: Please refer to our latest ingestion schema to determine what data needs to be pulled.

  • For LMSs there are three CSVs that are required for ingestion:

    • Content
    • Assignment
    • Progress Data
  • There is only one Content CSV for Content Integrations (IT - Enabled), and Content Partner Integrations.

Q.: How does LinkedIn Learning handle and protect the data exports we provide as part of Learning Hub?

A.: Review the points below to understand how LinkedIn protects PII and maintains the confidentiality of sensitive information:

  • LinkedIn Learning's Data Processing Agreement covers how we process and protect personal information (PII). The "CONFIDENTIAL INFORMATION" provision in the LinkedIn Subscription Agreement covers how LinkedIn Learning keeps the information confidential.

  • As a current LinkedIn Learning customer, your organization has already agreed to these terms.

Q.: How does LinkedIn keep Learning Hub data secure?

A.: LinkedIn keeps data ingested for Learning Hub secure via the following standards:

  • Review full information about LinkedIn’s Information Security Program.

  • In summary:

    • LinkedIn is SSAE16 SOC 2, ISO 27001, and PCI DSS certified.
    • LinkedIn maintains a robust and extensive security program with policies and detailed security requirements that guide the program's execution. The objective of this program is to maintain the confidentiality, integrity and availability of all computer and data communication systems while meeting necessary legislative, industry, and contractual requirements.
    • LinkedIn policies, procedures, and standards are based on International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC) "27001" requirements.

Q: What are your SFTP details?

A.: Please refer to the LinkedIn Learning Hub SFTP Guide.

Q.: What happens if I don’t see data in Learning Hub that should be there?

A.: If the data does not surface in ~ 24 - 48 hours in the Learning Hub after the data has been dropped to the SFTP endpoint, please reach out to your LinkedIn Learning Account Team to flag this issue for troubleshooting.

Q.: How does data updating work? Is it snapshot or delta?

A.: LinkedIn Learning requires that you always provide the entire snapshot data to our SFTP endpoint. LinkedIn Learning is investing in delta sync capabilities.

Q.: How many Content Partners can I include in the integration if I have multiple Content Partners plugged in to my LMS?

LinkedIn Learning recommends limiting Content Partners to no more than five (5) in the LMS integration. This guideline helps you avoid overwhelming learners with too many Content Partners in their search filters.

Q.: How do you handle locales as part of the data schema?

A.: LinkedIn Learning Hub manages locales via the following data schema conditions:

  • LinkedIn Learning ingests the locales for Title, Description, SubTitle, and ShortDescription per our ingestion schema; as a map, as they are multi-locale fields. LinkedIn Learning shows appropriate locales to users based on their language selection. If a user's language selection locale is unavailable, we default to PrimaryLocale.

  • PrimaryLocale is a part of the ingestion schema.

  • LinkedIn Learning recommends providing the PrimaryLocale explicitly. If the PrimaryLocale is not provided, LinkedIn Learning assumes the first locale is the PrimaryLocale.

Q.: Is the data transfer mechanism via "Push" or "Get"?

A.: The customer should push the CSV files via SFTP to the LinkedIn Learning Hub SFTP endpoint for Learning Hub to ingest them.

LinkedIn’s Privacy and Data Security Policy

https://www.linkedin.com/legal/privacy-policy

LinkedIn Security Contacts

If you have any security questions or you would like to report a security issue, write to us at security@linkedin.com.

Back to Top