NOTICE: On June 3, 2025 Qualtrics® will be migrating to a new system for detecting fraudulent survey respondents, deprecating the current third-party integration with RelevantID. You may need to adjust some of your existing workflows due to this change. The existing RelevantID embedded data fields (Q_RelevantIDDuplicate, Q_RelevantIDDuplicateScore RelevantID, Q_RelevantIDFraudScore, Q_RelevantIDLastStartDate) will start using default values instead of calling the third-party to compute a score. Any branch logic dependent on a non-zero score will no longer take effect. Survey Options will now include two toggles for detecting duplicate respondents: One will configure browser cookie detection used by “Prevent Multiple Respondents” feature, which will continue to function as before, allowing survey creators to determine the behavior when the survey is first loaded by a respondent who has that cookie. A new “Detect duplicate respondents” toggle will be added to configure the behavior for likely duplicates, as detected by running a proprietary algorithm when the survey ends. This toggle can be further customized with the option to either flag the response with embedded data or screen it out. Surveys that previously enabled “RelevantID” will automatically enable this toggle and be configured to flag responses that are likely duplicates
A new embedded data field called Q_DuplicateRespondent will be added to responses after they are submitted, with a “true” value to flag responses detected as a likely duplicate under this new system. This embedded data field will not be available for branching logic within the survey in order to improve the accuracy of detecting duplicate respondents. This embedded data field is only added if you decide duplicate responses should be kept, not screened out.
What action do I need to take? If you have any configurations in Qualtrics based on the existing RelevantID embedded data fields (Q_RelevantIDDuplicate, Q_RelevantIDDuplicateScore, Q_RelevantIDFraudScore, Q_RelevantIDLastStartDate), we recommend replacing these by June 30, 2025. Configurations could include branch logic, workflows, data filters, and reports filters. The new system is already available and flagging responses using “Q_DuplicateRespondent”. Filters depending on the existing fields will still be functional for old responses, but newly recorded responses will not be included in such filters. Consider updating any filters used to detect duplicate responses with the old “Q_RelevantIDDuplicate” flag to also check for the new “Q_DuplicateRespondent” flag to detect duplicate responses detected by both the previous and the new implementation. Please note that the “Fraud Detection” score is being deprecated and will not be recorded for new responses.
What if I have questions? If you have a question about RelevantID, please visit the Fraud Detection support page. It’s also always worth checking the XM Community to see if any other users have the same question. If you’d rather speak to a specialist, our Support Team is always ready to assist. To contact them, please file a support request from your Customer Success Hub. Thank you, Qualtrics |
|---|
NOTICE: On June 3, 2025 Qualtrics® will be migrating to a new system for detecting fraudulent survey respondents, deprecating the current third-party integration with RelevantID. You may need to adjust some of your existing workflows due to this change. The existing RelevantID embedded data fields (Q_RelevantIDDuplicate, Q_RelevantIDDuplicateScore RelevantID, Q_RelevantIDFraudScore, Q_RelevantIDLastStartDate) will start using default values instead of calling the third-party to compute a score. Any branch logic dependent on a non-zero score will no longer take effect. Survey Options will now include two toggles for detecting duplicate respondents: One will configure browser cookie detection used by “Prevent Multiple Respondents” feature, which will continue to function as before, allowing survey creators to determine the behavior when the survey is first loaded by a respondent who has that cookie. A new “Detect duplicate respondents” toggle will be added to configure the behavior for likely duplicates, as detected by running a proprietary algorithm when the survey ends. This toggle can be further customized with the option to either flag the response with embedded data or screen it out. Surveys that previously enabled “RelevantID” will automatically enable this toggle and be configured to flag responses that are likely duplicates
A new embedded data field called Q_DuplicateRespondent will be added to responses after they are submitted, with a “true” value to flag responses detected as a likely duplicate under this new system. This embedded data field will not be available for branching logic within the survey in order to improve the accuracy of detecting duplicate respondents. This embedded data field is only added if you decide duplicate responses should be kept, not screened out.
What action do I need to take? If you have any configurations in Qualtrics based on the existing RelevantID embedded data fields (Q_RelevantIDDuplicate, Q_RelevantIDDuplicateScore, Q_RelevantIDFraudScore, Q_RelevantIDLastStartDate), we recommend replacing these by June 30, 2025. Configurations could include branch logic, workflows, data filters, and reports filters. The new system is already available and flagging responses using “Q_DuplicateRespondent”. Filters depending on the existing fields will still be functional for old responses, but newly recorded responses will not be included in such filters. Consider updating any filters used to detect duplicate responses with the old “Q_RelevantIDDuplicate” flag to also check for the new “Q_DuplicateRespondent” flag to detect duplicate responses detected by both the previous and the new implementation. Please note that the “Fraud Detection” score is being deprecated and will not be recorded for new responses.
What if I have questions? If you have a question about RelevantID, please visit the Fraud Detection support page. It’s also always worth checking the XM Community to see if any other users have the same question. If you’d rather speak to a specialist, our Support Team is always ready to assist. To contact them, please file a support request from your Customer Success Hub. Thank you, Qualtrics |
|---|
NOTICE: On September 3, 2024 Qualtrics authentication was changed from Shibboleth to “Azure ID” for the university effectively enabling Single Sign-on (SSO) However, for survey owners/authors, when the current SSO connection is turned off (Shibboleth) then the SSO authenticator in the survey will stop working and pulling in user attributes from the SSO connection. It will also not update to the new connection automatically. Users will need to go in and manually change the connection and republish their surveys in order to bring in the attributes from the new SSO connection (Azure ID). |
Qualtrics Overview
Qualtrics offers over 100 question types (the most in the industry.) This allows for many different types of research besides the standard “survey” research. Qualtrics offers 4 levels of survey logic. Qualtrics is also provides multiple levels of randomization, piped text from data files, heat map question types, meta information capabilities, and page timing. Qualtrics provides collaboration, which is particular to Qualtrics. This allows researchers to share surveys and projects while maintaining secure credentials. Along with the interface, Qualtrics provides an extensive reporting engine along with subgrouping, graphing options, cross tabulation, and raw data downloads into SPSS.
Qualtrics provides a secure tool and claims that users will meet SAS 70 requirements, any and all IRB standards, HIPAA regulations. Qualtrics also claims to meet US and European Safe Harbor regulations and is FERPA compliant.
Qualtrics optimizes with a smart phone, iPad, blackberry, or Android for the respondents end and the survey administrator’s end. Qualtrics also provides QR codes to be generated to take surveys. Qualtrics is the only survey solution that provides multiple levels of anonymity. Researchers can choose to track responses with respondents, completely strip all identifying information (including IP addresses), or allow sections of the survey to be anonymous while other parts are tracked.
Qualtrics is known as a “research suite” because it claims it can handle experimental research, data collection in the medical area, securing PHI data, marketing research, assessment, evaluations, testing/scoring for the classroom setting, along with survey research.
Qualtrics is the only survey vendor that has scheduled updates and release every 6 weeks.
Access
Qualtrics is licensed for all current SU faculty, Students and Staff. Login is achieved through a secure process in which your credentials are never given to Qualtrics. Due to licensing restrictions
ESF faculty, staff and students are unfortunately not eligible to use this instance of Qualtrics.
Our license dos not cover alumni access. The process for requesting temporary access is to work with the professor and/or home department and make a request asking them to provide you with a "Sponsored" guest account for the duration of the project. Sponsored accounts are an option for folks that are somehow affiliated with the school or university.
Get Started Now!
Support & Training
Qualtrics Support & Training
Qualtrics Security and Compliance
Platform Security
Qualtrics Trust Center
Security Statement, October 26, 2022
Data Protection & Privacy
Qualtrics Security White Paper LITE May 2019
Qualtrics