You can use Intelligent Translations when learners access Go1 content through another learning platform. This works whether your platform receives content through a Go1 integration or you export Go1 content as SCORM files.
To play eligible content in a learner's preferred language, Go1 needs to receive that learner's language when the content launches or have the language saved on the learner's Go1 profile.
Intelligent Translations are available for eligible Go1 content and supported languages. If a suitable translation is unavailable, Go1 loads the content in its original language.
Learn more about Intelligent Translations and our supported languages.
Choose how to provide the learner's language
You can provide the learner's language at playback time or save it on their Go1 profile.
Option 1: Provide the language when SCORM content launches
Go1 content exported as SCORM is available in SCORM 1.2 format. Other SCORM versions are not available for exported Go1 content.
SCORM 1.2 includes a learner language preference field:
cmi.student_preference.language
If your LMS makes the learner's language available in this field when it launches the Go1 SCORM package, Go1 uses that value to select the playback language.
Ask your LMS administrator or provider to confirm that the LMS can:
Read each learner's preferred language.
Make that language available through
cmi.student_preference.languagewhen the content launches.Send a valid language tag, such as
fr,de,fr-CA, orpt-BR.
Language values should use a valid BCP 47 language tag and match a language in Go1's supported languages.
Note: The language supplied through SCORM applies to that launch. Go1 does not save it as the learner's persistent profile language. If the learner changes their language in your LMS, Go1 can use the new value the next time the content launches.
Learn more about the format in What is a SCORM?.
Option 2: Save the language on the learner's Go1 profile
Providing a language through SCORM is optional. If your LMS cannot supply cmi.student_preference.language, you can instead keep the learner's language preference updated on their Go1 profile.
You can manage profile languages using:
Single Sign-On (SSO): Recommended when available. SSO can update the learner's language each time they sign in.
SCIM: Provision and update learner profile information from your identity provider.
Go1's public API: Create or update learner accounts with a language preference.
CSV import: Import learner profile updates through Go1.
Whichever method you use, make sure it updates the same Go1 learner account used to play the content.
See Set up learner profiles to power personalisation in Go1 for guidance on keeping profile information current.
Developers and integration teams can also review Enable translated content.
What happens when the content launches?
The learner launches Go1 content from your LMS, HRIS, or other learning platform.
Go1 checks for a language supplied for that launch. For a SCORM 1.2 export, this is the value in
cmi.student_preference.language.If no playback-time language is supplied, Go1 uses the language saved on the learner's Go1 profile.
If the content is available in that language, Go1 loads the translated version automatically.
If an exact regional translation is unavailable, Go1 may use the base language. For example,
fr-CAmay fall back tofr.If no suitable translation is available, Go1 loads the content in its original language.
A language supplied at playback time takes priority over the language saved on the learner's Go1 profile for that launch.
Troubleshooting
Content opens in its original language
Check that:
Your LMS supplies
cmi.student_preference.languagewhen it launches the SCORM package, or the learner has a language saved on their Go1 profile.The value is a valid language tag.
The language is included in Go1's supported languages.
The selected content is available in that language.
Your LMS provider may need to confirm whether its SCORM player supports the learner language preference field.
Content uses a different language from the learner's Go1 profile
Check whether your LMS is supplying a language at playback time. A value supplied through cmi.student_preference.language takes priority over the saved Go1 profile language for that launch.
A learner changed their LMS language, but the content did not change
Confirm that your LMS supplies the updated language each time it starts a new SCORM launch. The language from a previous SCORM launch is not saved as the learner's Go1 profile preference.
Playback is translated, but titles and descriptions remain in the original language
Playback language and catalogue metadata are managed separately. Ask your integration team to review how to sync translated content metadata.
Frequently asked questions
Do I need a native Go1 integration to use Intelligent Translations?
No. Intelligent Translations can work with an integration or with Go1 content exported as SCORM, provided Go1 receives or already knows the learner's preferred language.
Which SCORM version does Go1 export?
Go1 exports content as SCORM 1.2. Other SCORM versions are not available for exported Go1 content.
Is the SCORM language field required to launch Go1 content?
No. The field is optional. If no language is supplied and no supported language preference is saved on the learner's Go1 profile, Go1 loads the content in its original language.
Does Go1 save the language sent through SCORM?
No. Go1 uses the value for the current launch. To save a persistent preference, update the learner's Go1 profile through SSO, SCIM, the public API, or CSV import.
What happens if the requested translation is unavailable?
Go1 may fall back from a regional language to its base language. If no suitable translation exists, the content opens in its original language.
How do I make the translated metadata available on my LMS/HRIS?
This guide explains how to play Go1 content in the learner's preferred language. If you wish to import translated content metadata to your LMS/HRIS, follow this guide: Sync content to your system.