Cint Exchange pre-screener terminations FAQs

Terminations that occur in the pre-screener and before the respondent enters the client survey. If a termination occurs whilst the respondent is in the survey, this is logged as a client response code termination.

You can find that information in our Cint Exchange (Marketplace) response codes.

By reducing these terminations and increasing the survey entry rate, it will not only improve your performance but also increase respondent satisfaction.

These session outcomes can be tracked via:

• Feed respondent outcomes subscription. The value returned in the property "marketplace_status"

• The value returned by the `InitialStatus` redirect URL parameter.

Please note: terminations 131, 301, 302 and 303 will not trigger a redirect, so can only be tracked via respondent outcomes.

In addition, you can view a breakdown of your Cint Exchange terminations via the terminations tab in the supplier portal marketplace API dashboard report. This dashboard is a great resource for identifying areas of deficiency that need improvement. Where you have high terminations, use the section below to identify steps to take.

Below we have provided our recommendation on how to address the different Cint Exchange termination types.

Standard qualification terminations

Cint Exchange (Marketplace) Response Code: 23

Please view our standard qualifications to understand how to reduce these terminations.

Custom qualification terminations

Cint Exchange (Marketplace) Response Code: 24

• Dynamically profile respondents on custom qualifications: Since buyers infrequently use custom qualifications, avoid including these questions in your static profiling. Instead, follow the recommended steps below to profile dynamically.

  • First, your system must detect the qualification question that has not been previously mapped to a user.

  • Once identified, your system will need to call the show question text and the show question options API endpoints to collect the question information.

  • Next, your application will need to present this question to the user ahead of entering the survey to determine if they qualify:

    • If they are qualified, send them into the survey opportunity and include the qualification information on the entry link to avoid the user being presented with the question in the pre-screener.

    • If the respondent is not qualified, try to find another opportunity for them. Your system should store and use that information to effectively identify the next survey opportunity for the user.

• Make sure you are refreshing qualification data regularly enough: This means updating your tables with the latest qualification data provided via your feed opportunities subscription.

Overquota terminations

Cint Exchange (Marketplace) Response Code: 40, 41, 42

See the overquotas terminations guide to understand how to reduce these terminations.

Survey group terminations

Cint Exchange (Marketplace) Response Code: 138, 139, 230

• Make sure you’re not sending a respondent to more than one survey in each survey group: To do this, ensure you’ve applied the logic outlined in part 4 of the getting survey data section of the integration guide.

• Make sure you are refreshing survey group data regularly enough: this means updating your tables with the latest survey group data provided via your feed opportunities subscription.

Duplication security terminations

Cint Exchange (Marketplace) Response Code: 30, 31, 35, 36

Each type of duplication may require different precautions to reduce its effects. Your account team can assist in identifying which portion of the duplication can be attributed to the following.

• Internal duplication from the same user: A supplier repeatedly sends a respondent to the same survey. This type of duplication can be resolved by taking precautions to prevent respondents from entering the same survey twice.

• Internal duplication from different users: A single individual exists as multiple unique users in the supplier’s system and is allowed to attempt the same survey for this reason. This type of duplication can be resolved by taking precautions to prevent individuals from creating multiple accounts within their system.

• External duplication: occurs when a respondent enters the same survey from two different suppliers. This type of duplication can be reduced by analyzing the termination patterns of duplications. Evaluating downstream supply sources can help identify sources for which the duplication appears to be concentrated. If the analysis indicates that duplication is concentrated around particular sources, that information can be provided to the sources as feedback, used to prioritize or deprioritize sources within your system, and to inform new user acquisition strategies.

Encryption (hashing) terminations

Cint Exchange (Marketplace) Response Code: 131

We will handle entry link hash terminations in two ways:

• 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 these cases:

  • The respondent will not be redirected back to the supplier.

  • We will not send a message to any respondent outcomes subscription confirming the session outcome.

• If a user bypasses the initial stages and enters the Cint Exchange later in the experience (which is not expected behavior) with a missing or incorrect hash signature, the respondent will be terminated and a session will be created. These sessions will be recorded with a 131 prescreener status code. In these cases:

  • Sessions will appear in the UI and supplier portal reporting.

  • The respondent will not be redirected back to the supplier.

  • A message will be sent to any respondent outcomes subscription confirming the session outcome.

To help identify entry link hash failures that result in a session not being created, you can look for users for whom your system has recorded an entry, but not received session outcome information. This can be reviewed via the supplier breakdown report or programmatically through respondent outcomes (specifically when subscribed to all outcomes and no session message is received). Alternatively, please reach out to your account team who can help validate whether a user's session was terminated due to a failed entry link hash signature.

To avoid hash failures, please follow the guidance below.

• Make sure you include a hash signature on the entry link, and that it is the last parameter in the URL.

• Make sure you’ve followed the guidelines outlined in our SHA-1 hashing article, applied the code provided in our hashing tool, and used the hash key sent by your account team. The hashing tool can be used to validate your SHA-1 hashing.

• When hashing the URL, make sure you include the entire URL, including a trailing &.

• If you've confirmed that you are hashing correctly and these errors still appear, it could suggest tampering with the entry link. Make sure you mask entry links in your system. Monitor the respondent's activity closely, applying survey opportunity restrictions in accordance with your security and quality rules.

Consent declines

Cint Exchange (Marketplace) Response Code: 236

This outcome occurs when a user declines our terms and conditions on the consent page. If a user declines, we do not block them; instead, the next time they return, they will be presented with the consent page again. If a user consistently declines consent, we recommend including messaging that reminds the respondent that accepting the terms is necessary for survey participation. If opt-outs persist, it is advisable to block their access to Cint inventory.

Load errors

Cint Exchange (Marketplace) Response Code: -1

Here are a few recommendations for investigating and reducing load errors:

• Make sure the PIDs and MIDs being passed in on entry links do not contain any special characters other than an underscore or a dash, and that they do not exceed the character limits indicated in the Generating API Entry Links article.

• Make sure respondents are clearly informed of their path before entering the survey.

• Analyze affected respondents for patterns to begin isolating the cause.

Drop outs

Cint Exchange (Marketplace) Response Code: 1

This status applies to respondents who are still in the pre-screener or who have dropped out. Typically, if the respondent hasn’t returned on a redirect after 2x the median LOI of the survey (or the BidLOI if LOI is not available), this represents a drop.

• Make sure the messaging presented to a respondent prior to entering the pre-screener clearly prepares them with what to expect.

• Use the approaches outlined in our yield management guide article to quickly close down surveys with high drop rates.

• Analyze affected respondents for patterns to begin isolating the cause.

Cint Survey Protection Services terminations

Cint Exchange (Marketplace) Response Code: 32, 37, 238, 240, 241, 242

For information on how to identify and handle respondents terminated on one of our survey protection measures, please reference article Cint's security and quality measures found in the security documentation section of the Cint Supplier Portal . If you do not have access to the Cint Supplier Portal, please contact a member of your account team to have your login activated.

Concurrent session terminations

Cint Exchange (Marketplace) Response Code: 301

This termination occurs if a respondent attempts to open multiple survey sessions simultaneously in the same browser. To reduce these terminations, please inform your respondents on your survey platform(s) that they should attempt only one survey at a time.

Cookie session expired terminations

Cint Exchange (Marketplace) Response Code: 302

This termination occurs when a respondent survey session has expired, 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 terminate the original survey with a 302 prescreener response code (no redirect triggered), and a new session will be created for them.

To help reduce these terminations, we recommend clearly messaging respondents before they enter the survey that they should remain engaged and complete it within an appropriate timeframe.

Session timeout terminations

Cint Exchange (Marketplace) Response Code: 303

This termination occurs when a respondent remains inactive for an extended period, and we automatically close the session.
To help reduce these terminations, we recommend clearly messaging respondents before they enter the survey that they should remain engaged and complete it within an appropriate timeframe.