A Skilljar integration allows you to add training activity to your customer journey. The integration uses Totango's JavaScript collector via code snippets added to your Skilljar theme.

You can stream usage data into Totango for the following Skilljar events:

• Course enrollment
• Course completion
• Path enrollment

Suggested uses

When a customer enrolls or completes a course, what workflows do you want to automate? Here are some ideas:

1. Trigger a team notification: Add a simple notification on the account record, or celebrate a milestone with all account owners.
   
2. Send customer communications: Automate reminders, CSAT surveys, and next course recommendations.
   
3. Aggregate data by customer segments: Perform calculations on individual and account-level enrollment / completion data.
   
4. Analyze impact to business processes: View trends on training impact to customer health, days in onboarding, adoption, risk, and more.
   

1. Capture the Totango Account ID per student

To bring user-level data into Totango via product instrumentation, your LMS must have a mechanism to pass the Totango Account ID associated with each LMS user (Skilljar student). You can store the Totango Account ID in Skilljar using a custom Sign Up field.

To pass a value to this field via SSO (e.g., students log into the LMS from your application), consult your Engineering team for assistance. You may need to provide them with the Sign Up field's ID, which you can find in Skilljar.

2. Prepare your code snippets

Once you are able to capture each Skilljar user's Totango Account ID, you can configure your code snippets.

Learn more about the Totango code snippets supported by Skilljar.

Totango tracking code (general tracking)

A JavaScript code snippet should go on every page of the application. If the LMS vendor has an area to modify global code within the </head> tag, that’s where you’ll want to insert this snippet (e.g., Global Head Snippet in Skilljar).

• Make sure you include your own Totango Service ID. 
• Choose the module name that you want to use to identify LMS data in Totango.
  • Example module name: Academy

  <!-- Totango Tracking-->
  <script>
  window.totango_options = {
  service_id: "SP-XXXXXX-01", // Replace with your Totango service code (tenant
  ID)
  module: "Academy", // Replace with the module name
  }
  if (typeof(skilljarUser) != 'undefined') {
  window.totango_options.user = // Start of the USER object
  {
  id: skilljarUser.email, // email address or other unique identifier of the user
  name: skilljarUser.name, // first and last name
  }
  window.totango_options.account = // Start of the ACCOUNT Array
  {
  id: skilljarUserSignupFields.valueOf()['accountid'].value, // Must correspond
  to Totango Account ID.
  }
  }
  (function() { var tracker_name=window.totango_options.tracker_name||"totango";window.totango_tmp_stack=[];window[tracker_name]={go:function(){return
  -1;},setAccountAttributes:function(){},identify:function(){},track:function(t,o,n,a){window.totango_tmp_stack.push({activity:t,module:o,org:n,user:a});
  return -1;}}; var e = document.createElement('script'); e.type = 'text/javascript';
  e.async = true; e.src = ('https:' == document.location.protocol ? 'https://'
  : 'http://') + 'tracker.totango.com/totango3.js'; var s = document.getElementsByTagName('script')[0];
  s.parentNode.insertBefore(e, s); })();
  </script>
  <!-- End Totango Tracking -->

Conversion code snippet

In addition to the ability to track any visits to the LMS website, we also want to track specific events for course and/or path enrollment. If the LMS vendor has a global area to trigger code on a “conversion” or “registration” event, that’s where this needs to go (e.g., Conversion Code Snippet in Skilljar).

• Skilljar allows you to track enrollments at the course level and/or path level
• Choose the activity name that you want to use to identify these events in Totango.
  • Example activity names: Enroll - <Course Name> | Enroll - <Path Name>

  <script>
  if (typeof(skilljarCourse) != 'undefined') {
  totango.track("Enroll - " + skilljarCourse.title);
  }
  </script>

  <script>
  if (typeof(skilljarPath) != 'undefined') {
  totango.track("Enroll - " + skilljarPath.title);
  }
  </script>

Course completion code snippet

Finally, we also want to track specific events for course completion. If the LMS vendor has a global area to trigger code on a “completion” event, that’s where this needs to go (e.g., Course Completion Code Snippet in Skilljar).

• Skilljar allows you to track completion at the course level. If you want to additionally track path completion, you can build that automation on the Totango side (see suggested SuccessPlays).
• Choose the activity name that you want to use to identify these events in Totango.
  • Example activity name: Complete - <Course Name>

  <script>
  if (typeof(skilljarCourse) != 'undefined') {
  totango.track("Complete - " + skilljarCourse.title);
  }
  </script>

3. Insert your code snippets into Skilljar

You will also see module and activity data in the Usage Monitor (Executive Console), on the Usage tab of each account profile, on the user profile, and in segmentation.

Learn more about analyzing user-level usage.

4. Configure automations within Totango

Everything beyond a usage stream must be manually configured. The most common practice for actioning usage data is to set a date attribute in Totango for when the first event occurred (e.g., enrollment in a course, completion of a course). Setting a date allows you to then build segments, campaigns, workflows, and KPIs based on attributes.

Here are some suggestions for building automations in Totango for Skilljar:

User attributes

Account attributes

Account attributes are not required, as you can filter most items based on the user attributes. However, you may consider adding the following for purposes of historical trend in KPIs.

SuccessPlays

SuccessPlays automatically set date attributes so that you can use them in segmentation engines. Consider the following series of SuccessPlays using different approaches to trigger criteria.

SuccessPlays set by usage data:

• Set Enrolled Date for <Path Name>
• Set Completed Date for <Path Name>*
• Set Enrolled Date for <Course Name>
• Set Completed Date for <Course Name>

*Skilljar usage data is not available for path completion events. Instead, set the criteria for this play to check for the completed date of every course within the selected path.

SuccessPlays set by presence in a segment based on "First" attribute:

• Course - Add First Enrolled Date at User Level
• Course - Add First Completed Date at User Level
• Course - Add First Enrolled Date at Account Level
• Course - Add First Completed Date at Account Level
• Path - Add First Enrolled Date at Account Level
• Path - Add First Completed Date at Account Level

Refer to the following examples:

User segments

Account segments

Scorecard