The easiest way to bring third-party content into Bridge is by using one of our existing integrations with the following providers:

• OpenSesame
• Udemy
• LinkedIn Learning

These integrations require minimal setup. OpenSesame allows you to choose which courses to bring into Bridge, while Udemy and LinkedIn Learning import their entire catalog by default.

By default, these integrations send an anonymous identifier ("Bridge User") to the SCORM engine, as content is hosted via our third-party provider, Rustici. However, if you prefer to pass the learner's first and last name (with no additional personal data), our Support team can enable this option upon request.

Bridge supports the following content standards:

• SCORM 1.2 & SCORM 2004
• AICC

Additionally, Bridge offers open API's that allow you to automate the process of adding and managing content.

Below is a breakdown of supported file types, followed by further explanations for each one.

SCORM 1.2 & 2004 or AICC: DOWNLOAD & UPLOAD

Another option that requires no development work is to download SCORM-compliant ZIP files from your content provider and upload them directly into Bridge.

SCORM Package Replacement: Key Considerations

Replacing a SCORM package in Bridge helps you maintain learner data and course integrity. Here's how it works:

• Completed learners: Completion records remain intact whether you replace the SCORM file or archive the course and create a new one.
• In-progress learners: Progress resets, and they will start the new version of the course.
• Not-started learners: Will automatically access the new content once the SCORM package is replaced.

Replacing a SCORM package (instead of creating a new course) also ensures that course reporting remains consistent, preserving reporting history tied to the original course_id.

SCORM 1.2, SCORM 2004, and AICC: API Integration

Bridge provides open APIs that allow you to automate workflows related to SCORM and AICC content (also known as dispatches). The following actions are supported via API:

• Fetch
• Show
• Create
• Update
• Delete
• Download

These API endpoints can be used to streamline the upload and management of SCORM/AICC packages, reducing manual effort and supporting bulk or frequent content updates.

xAPI is a delivery format that allows learning content to be launched outside of an LMS while still sending learning records back to a Learning Record Store (LRS). For this to work effectively and register completions in the LMS, three key components must be in place:

1. The LMS must send xAPI statements
2. The LRS must receive and store them
3. Both systems must communicate securely

While Bridge does not natively support xAPI, we do offer custom integration services that can support this type of workflow. However, this requires technical effort, including scoping, solution design, and delivery, typically provided as a paid service.

Considerations Before Committing to xAPI or Advanced Integrations

Before moving forward, we recommend evaluating the complexity and value of the integration by asking:

• What volume of content will learners consume from the third-party provider?
• How frequently does the provider update or add new courses?
• Do you expect learners to have full access to the provider’s content, with Bridge serving as the source of truth for all completions?
• What is the value of the transcript to the learner and to administrators?
• Does your organization use business intelligence (BI) tools for deeper reporting?

Alternative Option: Shell Courses via API

It is technically possible to use Bridge’s open API to create shell courses and then send completions into Bridge from a third-party system. However, this approach is typically:

• Highly complex
• Resource-intensive
• Fragile, prone to breaking if either system changes

We recommend pursuing this only if the above questions indicate strong business value, and if your team has the technical capacity to maintain such a workflow.

“We’ll place the SCORM URL into the course so the learner can go take the content in the other system.”

• Not a reliable record: Embedding a SCORM URL into a Bridge course does not track actual completion. Learners can still click "Complete" in Bridge regardless of whether they took the external training, making transcripts unreliable.
• Creates friction: Learners must log in again to access the third-party content, which disrupts the user experience.
• Administrative burden: Admins must return to the third-party system to validate completions, defeating the purpose of centralized tracking.

“We want the learner pathways to come over from the third-party content provider.”

• Manual recreation required: If tracking of pathways is required, each unit of the third-party pathway must be created in Bridge and structured into Programs and/or Journeys.
  • Programs can be built via API.
  • Journeys cannot be automated and require manual setup.
• Alternative option: If using shell courses, completion of a third-party pathway can trigger a single course completion in Bridge, reducing the need to bring over each individual component.

“We want all the third-party content to live in Bridge.”

• Content volume impact: High volumes of third-party content, even as shell courses, can clutter the Bridge authoring environment, impacting usability for internal authors and admins.
• No direct ID mapping: Bridge content IDs cannot be manually set to match third-party IDs.
  • However, Bridge Support can enable an External ID field in the authoring interface.
  • This can be populated manually or via API to reflect the third-party provider’s unique content ID for better tracking and mapping.

“We want a source of truth for all learner training.”

• Bridge can serve as a central source of truth, particularly when historical completions and third-party training are logged via:
  • Historical uploads
  • Shell course completions via API
  • Program/Journey completions
• For more advanced needs, many customers export Bridge data to external BI tools such as Power BI or Tableau to consolidate and analyze learner training records across systems.