1. Home
  2. Knowledge Base
  3. Tin Canny LearnDash Reporting
  4. Tin Can Lesson/Topic Completion Tracking

Integration with LearnDash Mark Complete

By default, the Tin Canny LearnDash Reporting plugin disables the Mark Complete button on a lesson or topic page until all the Tin Can modules on that page have been completed. This global setting prevents users from skipping content presented via Tin Can modules.

The global setting that controls the Mark Complete button can be overridden at the lesson or topic level by changing the value of Restrict Mark Complete from “Use Global Setting” to “Yes” or “No”.

When the Tin Canny plugin captures a “completed”, “passed”, “failed”, or “answered” verb, the Mark Complete button on the lesson/topic page containing that module is enabled. If there are multiple Tin Can modules on a lesson/topic page, the Mark Complete button gets enabled when all modules have been completed. For H5P modules, the Mark Complete button gets enabled when any module on the page has been completed.

Overriding Completion Condition

You can further control when the Mark Complete button is enabled by specifying a different completion condition on individual lesson or topic pages. For example, for a Tin Can module that contains a quiz at the end, you may want to limit the Completion Condition to just “passed”.

This change will force the Mark Complete button to remain disabled until the user passes the quiz. You can even override the passing grade that was set when publishing in Storyline, Captivate, or iSpring. For example, entering “result > 60” in the Completion Condition field will change the passing grade to 60.

Note:

  • The completion of a LearnDash lesson/topic and that of a Tin Can module are independent of each other. How completion should be triggered in an e-learning module published from Storyline, Captivate, and iSpring is configured in the Publish settings in those programs. (The following example is from Storyline 2.) Articulate Rise and H5P don’t give the user these tracking options.
    storyline_publish_tracking
  • Mark Complete integration will only work if the module is launched in a web browser. Tin Canny does not communicate with mobile apps such as Articulate Mobile Player or iSpring Play.

Troubleshooting Mark Complete Issues

It’s unfortunately common for many of our users to experience issues with control over the Mark Complete button. Problems tend to occur in at least one of these areas:

  1. Access to the Tin Canny endpoint. H5P and uploaded modules must have unrestricted access to send anonymous communications to our the virtual endpoint that Tin Canny creates on your site. Maintenance plugins (and other plugins that redirect users across the site), security plugins, proxies (like Cloudflare) and similar tools can block the access that’s needed for your modules to pass data to Tin Canny.
  2. Stored verbs and other data are different than expected. Different authoring tools send different statements. If you set up a Mark Complete restriction on a “Completed” verb, but your module doesn’t send that verb, the Mark Complete button will never unlock.
  3. Javascript conflicts. These are less common, but in some cases other plugins may interfere and prevent the Mark Complete button from unlocking.

Here are some important steps to try when investigating Mark Complete unlock errors:

  1. Understand your data. Open 2 windows, one showing the Tin Can report and the other your module. As you go through the module, continually refresh the Tin Can report to see understand what statements are triggered when. Also make sure the completion condition you want to use is actually recorded properly.
  2. Start with simple conditions. Don’t jump right into something like “result>80”. Start with a single verb that you know is being passed.
  3. Make sure you test with a regular user, not an admin or someone that completed the module previously, and that the user is signed in and enrolled in the course.
  4. Clone to a Staging environment and disable other plugins (except LearnDash and Tin Canny). This can help to rule out a conflict. Try to see if things work as expected in that environment.
  5. Check the browser console on the module page by choosing View > Developer > Javascript Console in Chrome. Is anything in red? Are the warnings anything that can be resolved or things that might indicate a probably that would affect Tin Canny? Note here that if you see 403 errors it indicates a permissioning issue, and 500 errors often have associated entries in the web server error log that should be investigated.

If you continue experiencing issues that can’t be resolved, reach out to our support team for assistance.

Was this article helpful?