New Cint Exchange Prescreener Response Codes
Concurrent Sessions (Cint Exchange prescreener response code: 301)
Respondents will be restricted from opening multiple survey sessions simultaneously within the same browser. If they attempt to do so, our system will prompt the user on the second session to select a single survey to continue with, as illustrated below. Initially, our concurrent sessions blocking feature will only be initiated on respondents entering through the consent page (i.e., those who have not yet consented). We plan to extend this functionality in the future to include sessions from consented respondents.
The following options display:
“I want to complete this survey” – If selected, the respondent will continue with this session. The other session will be closed and recorded with a 301 prescreener outcome. For the session not selected, a modal will appear with the message: “This session was ended.” The user will be required to close the tab.
“I want to continue with the other survey” – If selected, the respondent will be immediately redirected to a landing page informing the respondent the session is finished, where they will be required to close the tab. In this scenario a session has not started, so no session and outcome data is recorded in our system. The respondent can then continue with their original survey session.
Session Cookie Expiration (Cint Exchange prescreener response code: 302)
We will be expiring a respondents survey session cookie, either due to inactivity or by closing and reopening a browser. If the user reengages with the survey and wishes to continue, they can, but we will be terminating the original survey on a 302 prescreener response code (no redirect triggered) and a new session will be created for them.
Session Timeouts (Cint Exchange prescreener response code: 303)
We are introducing a session timeout threshold on our platform. If a respondent remains inactive for a defined period of time, their session will be closed automatically. The respondent will then be recorded with a 303 prescreener response code.
How to track these terminations
For each of these new prescreener response codes you can track these session outcomes programmatically through a Respondent Outcomes subscription or manually by extracting the data from our Supplier Breakdown Report . A redirect back to the Supplier is not triggered in any of these scenarios.
How to reduce these terminations
Please refer to our Cint Exchange Pre-screener Terminations FAQs article for more guidance on how to reduce these types of terminations.
Updates to Entry Link Hash Validation
We are implementing changes to how entry link hash failures are handled and recorded, with outcomes varying depending on when the failure occurs in the Cint Exchange prescreener. As a result of this change, Suppliers may see a reduction in the number of 131 prescreener outcomes recorded.
What’s Changing
Now, if the entry link hash validation fails at the start of the user experience, no session data will be recorded in our UI or Supplier Portal reporting. The respondent will be terminated and redirected to our standard error page: “Oh no! Something’s gone wrong,” and will be required to close the session. In this case:
The respondent will not be redirected back to the Supplier.
No message will be sent via Respondent Outcomes.
This change has been implemented to help ensure that Supplier reporting data contains sessions verified by our link security. It also aims to remove instances where individuals — not originating from the supplier panel or platform — gain access to their survey inventory, and trigger a hash termination session. This can skew a supplier's reporting as no entry will have been recorded in their system.
What’s Staying the Same
If a user bypasses the initial stages and enters the Cint Exchange later in the experience (not expected behavior) with a missing or incorrect hash signature, the respondent will be terminated and a session will be created. As before, these sessions will be recorded with a 131 prescreener status code. In these cases:
Sessions will continue to appear in the UI and Supplier Portal reporting.
The respondent will not be redirected back to the Supplier.
A message will be sent via Respondent Outcomes.
More Info: For guidance on how to reduce these types of terminations, please refer to our Cint Exchange Pre-screener Terminations FAQs article. Otherwise, if you need assistance validating whether a session was terminated due to an entry link hash failure, please reach out to your Account Team.