The goal of this FAQ is to educate our Cint Exchange feed (formerly known as Marketplace supply API) partners about client (in-survey) terminations and how to minimize them.
Client terminations
What are client terminations?
Terminations that occur once the respondent enters the client survey. Respondents that enter the client survey will have a marketplace response codes of 3. If a respondent does not pass prescreener checks, their client response codes will be –1. See Cint Exchange pre-screener terminations FAQs for information on how to decrease Cint Exchange (prescreener) terms.
What are the different client termination response codes and their definitions?
Find this information in the client response codes article.
Why should I reduce client terminations?
Your integration performance will improve and responder satisfaction will rise when you reduce client side terminations.
How can I track client terminations?
Client session outcomes can be tracked either via a Respondent Outcomes subscription and/or the value returned by the ClientStatus redirect URL parameter. Additionally, in the supplier marketplace API dashboard report, section "buyer survey terms" allows you to get a breakdown of your client termination rates by category. You may also access the yield management dashboard to view your performance at the survey level. These reports are an excellent resource for pinpointing areas of deficiency that need improvement.
Please note: terminations 301, 302 and 303 will not trigger a redirect, so can only be tracked via respondent outcomes.
How can I reduce client terminations?
Follow our recommendation below on how to address the different client side terminations.
Drops
Client response code: 1
This status is given to respondents who have either left the survey or are still participating. If a respondent hasn't returned to your platform after 2x the survey's median LOI (or if LOI isn't available, use BidLOI), we advise classifying them as a "drop" . Update your database with the returned session outcome data if they later return.
How to reduce this termination:
Making sure the messaging provided to a respondent prior to their entry into the Cint Exchange adequately prepares them of what to expect.
Utilize the strategies described in our yield management best practices guide to:
Throttle send to surveys with high drop rates
Track performance at a buyer level and deprioritize send to those buyers who have a history of high drop rates
Term and Overquota
Client response code: 20 and 40
These terminations typically occur when a respondent doesn't meet the additional qualifying questions and/or quotas set by the buyer. These question and quota requirements are not created in the marketplace and are not exposed in our API data.
To reduce these terms, we recommend applying the best practices outlined in the yield management best practices guide. These principles will enable you to create an effective survey filtering and ranking algorithm that prioritizes high-quality surveys and shuts out underperforming ones.
Additionally, we recommend filtering out surveys that have qualifying rules embedded late into the survey. By collecting the “termination_length_of_interview” data via the feed opportunities model, you can identify surveys with late terms. Stopping send to these surveys will help improve performance and respondent satisfaction.
Speeding
Client response code: 33
Under “Section Five: User Management” in the security best practices, we provide guidance on addressing user speeding.
Link Manipulations
Client response code: 35, 134, 135
See link manipulation to understand how to handle and reduce these terminations.
Concurrent session terminations
Client 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.
Please note: this termination will not trigger a redirect, so can only be tracked via Respondent Outcomes.
Cookie session expired terminations
Client 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 client 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.
Please note: this termination will not trigger a redirect, so can only be tracked via Respondent Outcomes.
Session timeout terminations
Client 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.
Please note: this termination will not trigger a redirect, so can only be tracked via Respondent Outcomes.