Qualtrics RelevantID Replacement June 15, 2025
Posted: 2025-06-12 15:06:35 Expiration: 2025-10-05 15:06:35
On June 11, 2025, Qualtrics notified us that they are making changes to RelevantID. The RelevantID feature is used for detecting duplicate survey respondents in Qualtrics surveys. On June 15, 2025, Qualtrics will deprecate the current 3rd party integration and you may need to make changes to surveys if they currently rely on RelevantID.
What is changing?
Qualtrics will be migrating to a new system for detecting fraudulent survey respondents, deprecating the current third-party integration with RelevantID. This change will happen June 15, 2025. Here is what to expect:
- 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 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 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 15, 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 questions you can contact the Qualtrics Customer Support team. For information on how to open a support ticket see UW-Madison Qualtrics - Log-In to Qualtrics Support.
-- Qualtrics: Admin Qualtrics