Qualtrics RelevantID Replacement

Tags Qualtrics

What’s changing?

Qualtrics is retiring its current fraud detection tool, RelevantID, on June 30, 2025. After this date, RelevantID will no longer provide scores or flag potentially fraudulent or duplicate responses. Instead, Qualtrics has introduced a new, built-in system for identifying duplicate respondents. Please note that the "Fraud Detection" score is being deprecated and will not be recorded for new responses.

How do I know if I’m using the old RelevantID?

You might be using RelevantID if you are using branch logic, workflows, data filters, and have turned on the setting to prevent multiple submissions.

To find settings, search in:

  1. Survey settings menu and use the Qualtrics Fraud Detection Guide to find the appropriate settings.
  2. Survey Flow and use the Qualtrics guide on where to look for the Fraudulent Detection Fields to the Survey Flow.

How do I update my settings on my survey?

You should update any part of your survey setup or analysis (like filters or workflows) that relied on the old method to use the new Q_DuplicateRespondent instead.

This change means that while the old method’s checks will still work for past survey responses, they won’t apply to new ones after June 30, 2025.

  1. Go to Survey Options and open the Security section to look for two toggles for detecting duplicate respondents:
    1. Find the "In Survey: Prevent multiple submissions" option and toggle it on. 
    2. Find the "Post-survey: Prevent multiple submissions with Duplicate Detection" option and toggle it on to analyze device and browser metadata to identify respondents attempting to take your survey multiple times.
      Read Qualtric's guide about enabling duplicate detection at: https://www.qualtrics.com/support/survey-platform/survey-module/survey-checker/fraud-detection/#DuplicateDetection

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.

Print Article