Retiring the QRTEngine

Dear QRTE users,

We are sad to announce that we have decided to retire the QRTEngine and support. The continuing and often unpredictable developments in the Qualtrics environment make it increasingly difficult to provide a stable QRTE platform.

In September last year we first noticed compatibility issues between Qualtrics’ newest Survey Engine (Jiffy) and the QRTEngine. Over several calls with Qualtrics’ engineering team we were unable to come to a satisfying solution in fixing the QRTEngine for the Jiffy engine, and were left with recommending users to revert to the old Qualtrics Survey Engine, for which we implemented a feature in the QRTEngine to automatically re-direct to the non-jiffy engine. However, it seems likely that the old Qualtrics Survey Engine will be retired at some point, which is a major threat to the method.

Unfortunately, several recent attempts to contact the Qualtrics team were not successful. So we do not know when the old Qualtrics Survey Engine will stop being supported. However, we got the impression that Qualtrics is not willing to support anything QRTEngine-related anymore. Repeated reports of sudden bugs in their engine were typically also not taken seriously, although they sometimes “spontaneously” disappeared, only then to resurface in new forms once again later on.

We also recently learned from users that the Qualtrics data handling platform will be moved to the so-called “Qualtrics Insight Platform”. Data output by this new platform seems not to be compatible with the QRTEParser, although – as one of you suggested at the forum – you can try to remove the 3rd row of your output csv file and see whether in that case the data is still parsed correctly.

Considering the minimal support we can expect from Qualtrics and the fact that our team is running this project in spare time without funding, we think that we are unable to continue the project in a sustainable way.

So our advice would be to finish up your projects running QRTEngine and start to look for alternatives – although we have to admit that we are not aware of any other free online experiment software yet that is easy to use without requiring extensive programming skills. Anyway, if you are a coder and like to integrate our code in another open survey environment, let’s try to team up and let us know at

In case you have support questions, please use the forum and ask the community for help. We will keep our site and the online parser alive at least until the end of 2016.

We still believe in online research and that this the way to go for future psychological research. We hope that the QRTEngine helped in getting your online research done. We thank you for your interest in our method and apologize for the QRTEngine coming to its end-of-life so suddenly.

Best regards,

The QRTEngine team

New parser available


We are happy to present you with a new option for parsing your QRTE data files. The parser webservice. It can be found at:

We noticed that most of the issues related to the parser are due to problems installing the required dependencies, and as such have decided to release this webservice, to increase the ease-of-use of the QRTEngine method.

We have taken a few security measures, aimed at minimizing the risk associated with file parsing, enumerated below.

  1. We generate a highly probably unique link for each file you upload, by generating a “Universally Unique Identifier” ( for each of them. This download link is only communicated to you through the e-mail you provide. This should prevent anyone from being able to successfully, randomly, guess the correct download url of a file.
  2. We delete any upload files, log files and parsed results that have been on our server for more than 24 hours. Both to prevent our hard disk from filling up, and to prevent as much as possible the accidental leakage of sensitive data on our end.

DISCLAIMER: we do not guarantee the safety of your data. This solution is aimed at data sets for which the leakage of it would not reveal any sensitive information regarding persons. For sensitive data we recommend reviewing the source code of the command line parser, and using that instead.

Offline (CLI) parser

As a result of releasing the new version of the webparser, we have also slightly updated the offline parser. We have made it clearer that it only runs on Python 2.7 (we never got the Python3 parser working properly on all data files) and have included instructions on how to run/install Python2.7 on your system, if it’s not already installed, in the

Also, older versions of the parser had the following error happening consistently:

builtins was required for Python2/3 hybrid support, but since the parser has been made Python-2 ONLY, builtins is no longer required, and as such this error should have been fixed.

Next to these changes, we have introduced two new variables in the output data file called “Parser[Version]” and “Parser[Type]”. Parser Version denotes the version of the parser that was ran, currently this is version 2. Parser Type denotes the method which was used to parse the file. “CLI” for the offline version, “WEB” for the webparser.

Best regards,

The QRTEngine team

v18 and the future of the QRTEngine

Dear QRTE users,

Introducing v18

As a result of the Qualtrics JFE (Jiffy) update in September, the QRTEngine has ceased to work properly, not just v16, but also, as we discovered recently, v15. For example we found that at the start of the trial a flash occurs where all objects can sometimes be shown briefly, Qualtrics server delays are accompanied by a Qualtrics swirl and stimuli are no longer vertically centered. Several attempts at fixing this have proven unsuccessful, because of unknown processes happening during the switch from one trial to the next.

Recently, one of you notified us of a way to turn off this new JFE Engine so that we can still work with version 16 (basically by adding ?Q_JFE=0 to the URL). We therefore launch a new version of the QRTEngine (v18) which is based on version 16, but it also automatically re-directs to a JFE disabled version of the survey by adding Q_JFE=0 as a GET parameter to the URL. We also made a few bug fixes (embedded data was not being stored in non-qrte questions, and we corrected pre-caching of images which seemed to work only intermittently before).

Version 18 is now available here:

The future of the QRTEngine

The problem with disabling the jiffy engine is that we’re back to our current situation, as soon as Qualtrics decides to cut support for their old survey engine (and the method with which we disable the jiffy engine). We will ask Qualtrics how long they are going to support the JFE disable option, but let’s hope it will be there for at least a couple of months.

We’ve come to the conclusion that fixing v15 (which would become v19) for this new JFE engine will be very difficult, also due to a major lack of time on Erwin’s part. In addition, Qualtrics needs to provide currently unimplemented javascript APIs to take care of the between-trial stuff that’s happening, and the timeline when these APIs will be released is currently unknown. In the past, support people from Qualtrics actually promised us that the introduction of the jiffy engine would solve issues of between-trial delays. However, the sad reality is that their update actually seems not have improved the timing between loops (trials) in a Loop & Merge block at all, and that it only improved the timing within a loop (which was handled by the QRTEngine already in the first place).

As such, there is no telling when v19 would be released, and whether this will be done at all (if you are interested in joining our team as a developer, please let us know). However v18 will work for the time being, and we recommend to stay tuned for news about v19. We are not planning any changes to the QRTEngine API, so surveys built for v18 should continue to work in v19 (barring changes to survey structure induced by Qualtrics).

Best regards,

The QRTEngine team

Temporary suggestion: Use v15_jfe_fix

Dear QRTE users,

As some of you have tried, and reported back to us, v15 of the QRTEngine seems to run fine on the new Qualtrics JFE engine. However, embedded data wasn’t stored when using this version. This issue has now been taken care of, and we suggest everyone to switch from v16/v17_jfe_fix to v15_jfe_fix. The js file can be found here:

Please let us know if there are any other issues with this version and look for notices on this website as we try and get the latest version of the QRTEngine, v16, working again in Qualtrics.

Thanks again for your understanding!

Best regards,

Erwin Haasnoot

QRTEngine Issue Tracker

Dear QRTE users,

As you may have noticed, fixing the QRTEngine has taken longer than originally planned, due to complexities involved in the recent the Qualtrics update.

There seem to be a myriad of different problems, and it’s hard to keep track of individual cases through comments/forums/posts. Therefore, we suggest any issues with the current version of the QRTEngine to be posted to our issue tracker on github, Make sure to include a description of the problem in the post and a link to related exported surveys (.qsf files). Or if uploading the .qsf is not an option, you can share the survey with me at ehaasnoot1[at] (make sure to mention the name of the survey in the issue you’ve created). Please note, this is the e-mail my Qualtrics account is registered to, I no longer have access to the mailbox.

The same goes for issues with the parser. It’s possible that due to recent updates in the Qualtrics Survey Engine, the file output structures changed, which would affect the parser as well.

I’m hoping to spend more time tonight, tomorrow night and over the weekend to tackle these issues, so hopefully we can get a broad range of issues in the tracker, which would allow me to test possible fixes as thoroughly as possible.

We are very sorry for any inconvenience caused by this and would like to thank you for your understanding.

Best regards,

Erwin Haasnoot

QRTEngine temporarily not working (update: temporary fix)

Dear QRTEngine fans,

In Qualtrics’ most recent update the Survey Engine now caches Loop & Merge questions (uses the new Javascript Form Engine;JFE or Jiffy for insiders). Although in the long run this will cause significantly better performance of surveys (much lower ITI delays), in the short run this means that the QRTEngine is temporarily no longer compatible with Qualtrics’ Survey Engine. Unfortunately, Qualtrics didn’t offer us a chance to test the QRTEngine against this new version of Qualtrics’ Survey Engine and there seems to be no way to temporarily load the old Qualtrics’ Survey Engine, so we now have to play catch-up. We will keep you updated on our progress, and hopefully have the QRTEngine working again by next week.

If there are programmers that want to be involved in getting the new QRTEngine running again, please let us know at

Thanks for your understanding.

Best regards,

The QRTEngine team

Update 13 Oct 2015 – Jonathan: 

Erwin has completed a first work-around that brings back the fundamental QRTE functionality:

The most recent additions – arbitrarily low ITI’s and the removal of a ‘white flash’ that sometimes occurs – are not available for now, we aim to fix that asap and will keep you informed!

Update 20 Oct 2015 – Henk:

Some of you indicated that version 15 still works fine with the new Qualtrics engine, so you might also try to use that version (also includes the ‘white flash’):

Of course, make sure you comment out the following line in this v15 as well, since Qualtrics still has not debugged their erroneous getChoiceValue API.



Qualtrics Bug Work-around

Hi everyone,

A lot of people have recently (for about a week) been having issues with the QRTEngine, regarding false positives in one of the survey validation functions. Specifically, an alert box popping up right at the start of a trial indicating ‘You need to define two answer form fields in the Exit questions!’ even though there are two answer form fields included in that question. We have investigated this issue and found that this is due to a bug recently introduced by Qualtrics in one of its JavaScript APIs called getChoiceValue. We have contacted Qualtrics to notify them of this issue, so hopefully it will be fixed soon.

The only work-around we can currently suggest is completely disabling the alert for now, by commenting it out. This implies that the engine is no longer checking whether the appropriate exit fields are defined, so if you do not do this correctly you may risk not acquiring the data correctly. So please be very careful and check your parsed data.

We have uploaded this temporary, version of the QRTEngine, that does this for you. So if you’re having issues with alerts being falsely thrown, please download the following QRTEngine source code and fully overwrite the QRTEngine version that’s currently included in your surveys.

Please note that this is actually version 16 of the QRTEngine in which we basically commented out the following line:

We are very sorry for any inconvenience caused by this issue.

Best regards,

The QRTEngine team

New QRTEngine parser in Python

Hi everyone,

We realise that a lot of issues arising in the QRTE method happen due to the workings of the java parser. Either the java parser doesn’t work at all on your system, it is buggy, or the input file is generated from a faulty survey and the parser doesn’t give a clear reason why it fails. For these reasons, we are in the process of creating a parser webservice, which can be found here:

Although the webservice is not yet finished, the parser we wrote for it is in a much better working condition than the java parser, and as such we will be retiring the java parser in favour of the new one written in Python, which seems to be de-facto language for much scientific software being written nowadays.

Please use the download instructions here:

We hope this will alleviate many of the issues many of you have been experiencing with the parser. Please stay tuned for a message in the coming weeks about the webservice being finished up.

Best regards,

The QRTEngine team