Jan 24, 2019


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. 

Why is this file there and what is it function? 

Anyone an idea?

Best regards,

25 Replies
Ashley Terwilliger-Pollard

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!

Brandon Harper

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"...

Rene Schutte

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.

Brandon Harper

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. 

Judi Wesser


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

Leslie McKerchie

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.


Can you explain the issue that you're running into and what you need some assistance with?

Ina Kruger

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.