Database Tutorials

1. Go to http://widener.qualtrics.com
2. From the login page, click on Don’t have an account?
3. Then enter a Valid Widener Email address.  Note: An access code is not required.
4. Qualtrics will automatically send an email to your Widener Email account, with the following message "Hello,Thanks for registering with Qualtrics!  Please confirm your registration by verifying your email address."
5. Click on Verify my Email.
6. Finally, complete the enrollment form that appears.  Note that your username will be your Widener Email address.  Create a password that you will remember and select Create account.

1. Once you have logged into Qualtrics, click on the Create a New Project button.

*Notice that the home screen will list recently viewed surveys that you have created.

2. On the next screen, under Create a project, click on Survey.

3. On the next screen, click on the Get Started Button.

4. The next screen gives you the opportunity to name your project and decide how to start your survey. Name your project and use the default: Create a blank survey project. Then select Create project.

5. The next screen gives you the opportunity to start creating questions. To create additional questions, click on the Add new question link. Make note of the ExpertReview score which rates the useability of your survey. The current score is Great, but click on the button to learn how to improve it.

6. Click on the button to view more information about survey useablity.

Features of the ExpertReview:

• First it will repeat the rating, in the case Great appears on the top. On the left side it will indicate any problems with survey questions and include numbers relating to the following:
  • Severe
  • Moderate
  • Minor
  • Suggestion
  • Passed

On June 30, 2025, Qualtrics® migrated 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.

Email Widener's Qualtrics Brand Administrator, Jill Borin at jmborin@widener.edu 

Follow these steps to get to a support representative:

1. Click on the  icon at the top right hand side of the screen.
2. You can select support for the following by selecting the following links::
   • homepage overview
   • shared project
   • survey platform
   • projects
   • folders
   • create a project
3. Click on the Contact Support link, notice that it states that support is offered through chat, phone or email
4. It will bring you to the Customer Success Hub
5. Select the Survey Platform & XM Directory tile
6. It opens the Qualtrics Support AI Assistant which allows you to ask questions and receive detailed answers. "The AI Assistant states: "Hello! I’m the Qualtrics AI Assistant, and I can help you with questions about Survey Platform & XM Directory. If I can’t find the answer you need, I’ll connect you to a member of the support team. What can I help you with?"
7. If the AI answer does not satisfy you, follow the directions for Chat, phone or email support,