I've updated Articulate Storyline to the latest version (3.24.177330.0) And when i publish a course to HTML or SCORM i see a file analytics-frame.html in my output folder.
Great question! We recently discovered a bug that caused the referring URL to be present within the header of the anonymous analytic event that is sent to Articulate when learners launch a course. This URL can be verbose, especially when the course has been published for xAPI, and it creates the false appearance that Articulate is collecting more information than we need.
Even though the referring URL isn’t saved anywhere on Articulate’s servers, we wanted to force the referring URL to be less detailed. We weren’t able to prevent the event from including the domain that referred it, but we cut it down to only the domain (not the full URL). The analytics-frame.html file is what allows us to do this.
If you'd like to see more details on the data we collect, how it's used, and how to opt out, please review this article.
Please let us know if you have any other questions. Thanks!
Mark- I am glad you asked. This is also popping up for me too.
I use Storyline to create resources. I publish as web and then import them into our Microsoft Sharepoint site. It works well within our call center as agents can quickly locate information in this file type.
Now that this file publishes this way, it is creating a bit of an issue for me. Trying to figure out how to address with our IT is "fun"...
Brandon, I had problems with the file in our SharePoint as well as it kept wanting us to save or download when trying to play our programs causing the program to fail. We just deleted the file and everything started running perfectly.
I ended out doing the same. I haven't run into any issues yet, so I figured it will do. Just been crossing my fingers since. Glad to hear this worked for you. Gives me some hope :-)
Since this update I cannot publish as Web to my LMS. After uploading the Zip-package, opening the file results in loading the analytics-frame.html and stops loading anything else. If I upload as LMS-file it works fine, but I do not need LMS for all my projects.
Also changing the privacy-setup in the 360-app did not solve this. The suppressAnalytics in the Story html5 file was set to true. Only thing that worked was to delete the analytics-frame-html file from the package.
Hello, Can staff verify that it is okay to delete the analytics-frame-html file from the package as stated in Brandon and Rene's posts above? The same thing is happening to me, and I am following their advice. Just want to be sure this doesn't affect anything else down the road?
It's not a setting we can offer support for, so I can't say exactly what would happen or how it'll behave. Perhaps Brandon or Rene can share more details on how this is working for them.
I am having the same issue, and when I remove the analytics-frame.html file the published file works perfectly in our LMS.
I was wondering -- are you still experiencing good results using published files without the analytics-frame.html file? Have any issues developed over time?
It's been working just fine. We have not had any negative issues since we have been removing it. It's an annoying step to have to do this each time we update our files, but it works. I wish they would stop publishing the files this way. It is a "fix" that doesn't really seem to be fixing anything; just causing more headaches than anything.
Our developer told me our LMS is looking for a story file, so we fixed our problem by publishing the course in Storyline, then editing the HTML Path in the HTML Archive from anyalytics-frame.html to story.html. It works great all the time now.
I'm not sure what you are asking, but here is what happened and how I fixed it.
When I upload a Storyline file to our LMS (see image below) and if I leave the path to first page blank, or if I type in story.html, and then Save Changes, it automatically assigns the path to first page as analytics-frame.html.
Courses wouldnt open up our LMS, so my fix is to upload the course file to the LMS, Save Changes. Then go in an edit the course file in the LMS and manually change the path to first page to story.html, then Save Changes.
Thanks for popping in to share the solution that worked for you, Judi.
It looks like your email signature came through when you replied via email. You can remove that if needed by clicking ‘Edit’ beneath your response. Here’s a quick Peek video if you need help.
Cathya,
Can you explain the issue that you're running into and what you need some assistance with?
Hi I was trying to edit it out all my info at the bottom of my post as you mentioned, and I accidentally hit Report. so I think it removed my post. Thought I'd mention it.
I am feeling really despondent today. My RISE lesson contains many Storyline blocks. The SCORM file was edited, but now none of the Storyline blocks are playing Is there a connection or should I look for another reason?
So sorry you're hitting a roadblock! Tell me more about how the SCORM file was edited. Did someone edit the published output file?
Would you be willing to share the published output file for our team to take a look? If that works for you, you can send it to us privately by clicking here.
Thanks Alyssa! The LMS admin has tweaked the file again by deleting the files one by one and tested it. The Storyline blocks are showing now, apart from the Certificate block. Could it be because I copied the same lesson each time and just changed it inside to reflect the different module it applies to? If that is the case, what should I change inside the lesson? Each certificate has a unique name and is published as a unique item in the repository. I sent you the file.
25 Replies
Hi Mark,
Great question! We recently discovered a bug that caused the referring URL to be present within the header of the anonymous analytic event that is sent to Articulate when learners launch a course. This URL can be verbose, especially when the course has been published for xAPI, and it creates the false appearance that Articulate is collecting more information than we need.
Even though the referring URL isn’t saved anywhere on Articulate’s servers, we wanted to force the referring URL to be less detailed. We weren’t able to prevent the event from including the domain that referred it, but we cut it down to only the domain (not the full URL). The analytics-frame.html file is what allows us to do this.
If you'd like to see more details on the data we collect, how it's used, and how to opt out, please review this article.
Please let us know if you have any other questions. Thanks!
Mark- I am glad you asked. This is also popping up for me too.
I use Storyline to create resources. I publish as web and then import them into our Microsoft Sharepoint site. It works well within our call center as agents can quickly locate information in this file type.
Now that this file publishes this way, it is creating a bit of an issue for me. Trying to figure out how to address with our IT is "fun"...
Brandon, I had problems with the file in our SharePoint as well as it kept wanting us to save or download when trying to play our programs causing the program to fail. We just deleted the file and everything started running perfectly.
I ended out doing the same. I haven't run into any issues yet, so I figured it will do. Just been crossing my fingers since. Glad to hear this worked for you. Gives me some hope :-)
Since this update I cannot publish as Web to my LMS. After uploading the Zip-package, opening the file results in loading the analytics-frame.html and stops loading anything else.
If I upload as LMS-file it works fine, but I do not need LMS for all my projects.
Also changing the privacy-setup in the 360-app did not solve this.
The suppressAnalytics in the Story html5 file was set to true.
Only thing that worked was to delete the analytics-frame-html file from the package.
Hello, Can staff verify that it is okay to delete the analytics-frame-html file from the package as stated in Brandon and Rene's posts above? The same thing is happening to me, and I am following their advice. Just want to be sure this doesn't affect anything else down the road?
Hi Judi,
It's not a setting we can offer support for, so I can't say exactly what would happen or how it'll behave. Perhaps Brandon or Rene can share more details on how this is working for them.
Okay, thank you, I will check with our developer too.
Judi Wesser
After deleting this, we have have not experienced any negative impacts. If we upload the published filed with it, then we have an issue.
I am having the same issue, and when I remove the analytics-frame.html file the published file works perfectly in our LMS.
I was wondering -- are you still experiencing good results using published files without the analytics-frame.html file? Have any issues developed over time?
Thank You.
Judi Wesser
It's been working just fine. We have not had any negative issues since we have been removing it. It's an annoying step to have to do this each time we update our files, but it works. I wish they would stop publishing the files this way. It is a "fix" that doesn't really seem to be fixing anything; just causing more headaches than anything.
Thanks for your update!
Judi Wesser
Just to clarify, removing the analytics-frame.html file caused no issue with playback?
I just published another file like this about 5 minutes ago. Still haven't seen any issues after deleting this file.
Our developer told me our LMS is looking for a story file, so we fixed our problem by publishing the course in Storyline, then editing the HTML Path in the HTML Archive from anyalytics-frame.html to story.html. It works great all the time now.
@Judi Wesser : what was the modification you use in story.html?
Hello,
I'm not sure what you are asking, but here is what happened and how I fixed it.
When I upload a Storyline file to our LMS (see image below) and if I leave the path to first page blank, or if I type in story.html, and then Save Changes, it automatically assigns the path to first page as analytics-frame.html.
Courses wouldnt open up our LMS, so my fix is to upload the course file to the LMS, Save Changes. Then go in an edit the course file in the LMS and manually change the path to first page to story.html, then Save Changes.
The courses work normally after that.
Judi Wesser
Thanks for popping in to share the solution that worked for you, Judi.
It looks like your email signature came through when you replied via email. You can remove that if needed by clicking ‘Edit’ beneath your response. Here’s a quick Peek video if you need help.
Cathya,
Can you explain the issue that you're running into and what you need some assistance with?
Hi I was trying to edit it out all my info at the bottom of my post as you mentioned, and I accidentally hit Report. so I think it removed my post. Thought I'd mention it.
Judi Wesser
Haha! I got you, Judi. Your post is back in action if you'd like to edit it now :)
Hi,
Are you also capturing analytics with the RISE 360 modulesl?
If so, is there a file similar to analytics-frame.html being used?
Thanks,
Martin
Hi, Martin. We are not capturing any learner usage data from Rise courses.
Please let us know if you need anything else!
I am feeling really despondent today. My RISE lesson contains many Storyline blocks. The SCORM file was edited, but now none of the Storyline blocks are playing Is there a connection or should I look for another reason?
Hi Ina,
So sorry you're hitting a roadblock! Tell me more about how the SCORM file was edited. Did someone edit the published output file?
Would you be willing to share the published output file for our team to take a look? If that works for you, you can send it to us privately by clicking here.
Thanks Alyssa! The LMS admin has tweaked the file again by deleting the files one by one and tested it. The Storyline blocks are showing now, apart from the Certificate block. Could it be because I copied the same lesson each time and just changed it inside to reflect the different module it applies to? If that is the case, what should I change inside the lesson? Each certificate has a unique name and is published as a unique item in the repository. I sent you the file.
This discussion is closed. You can start a new discussion or contact Articulate Support.