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:
- Survey settings menu and use the Qualtrics Fraud Detection Guide to find the appropriate settings.
- 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.
- Go to Survey Options and open the Security section to look for two toggles for detecting duplicate respondents:
- One will configure browser cookie detection used by the "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 second "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.