Respondent Exclusions FAQ

Respondent exclusions allow you to prevent respondents who have participated in any project or Target Group from being re-invited into related work across other projects within the same account. This ensures that respondents who have already completed specific studies are dynamically blocked from entering new, related surveys in real time.

• Simplified setup: Define all respondent-based rules in one view, whether excluding respondents from different projects or from other Target Groups within the same study.

• Increased efficiency: Provides a dynamic alternative to manual ID management, allowing the system to automatically resolve exclusions based on respondent participation history while maintaining support for manual ID blocklists for legacy or external data.

• Dynamic enforcement: The system performs real-time checks against respondent history in addition to static, pre-built ID lists.

• Data quality: A default rolling 90-day exclusion period for completes protects both the respondent experience and the integrity of your data.

You can do both:

• Exclude projects: Expand the "Exclude projects" section and click "Add" to search for and select entire projects. All Target Groups within those projects will be included in the rule.

• Exclude individual Target Groups: Search for specific Target Groups by entering their IDs (separated by commas, spaces, or other special characters).

A single Target Group can exclude a combined total of up to 100 projects and Target Groups per rule. Once added, your selections will appear in a manageable list for review.

Each Target Group supports up to 100,000 combined Respondent IDs (RSIDs) and Response IDs (RIDs). Additionally, you can upload a maximum of 100,000 Access Respondent GUIDs, providing a total permanent exclusion capacity of 200,000 IDs per Target Group.

Yes. Changes are allowed while a Target Group is live, but they apply to future respondents only. Edits will not remove people already in‑survey or already completed; those respondents remain as they are.

The current changelog does not capture exclusion rule changes.

Yes, when a Target Group is cloned, the respondent activity exclusions for both projects and Target Groups are copied to the new group.

Individual ID exclusions (uploaded CSV lists) are treated separately and are not included in the duplication.

No. Exclusions are account-bound. You can only exclude projects and Target Groups that exist within the same account.

1. Create a Target Group.

2. Navigate to Advanced Settings and select Respondent exclusions.

   This window contains streamlined controls for all exclusion types, including project-based and ID-based exclusions.

3. Expand Exclude projects and click Add.

   

4. Search and select the Projects to exclude.

   

5. To exclude participants from other projects, expand the Exclude projects section and click Add. This opens a search interface to find and select the projects you want to exclude.

6. As the projects are selected, they will be added to a Selected projects list at the bottom, allowing you to easily review your choices before adding them to your exclusion rule.

   

1. Create a Target Group.

2. Navigate to Advanced Settings and select Respondent exclusions.

3. Expand Exclude target groups.

4. Search and select individual Target Groups to exclude, even if they sit in other projects.

   

5. Search for one or multiple Target Groups at once by entering their IDs, separated by commas, spaces, or other special characters.

   

6. Once added, your selected projects and target groups will appear in a clear, manageable list.

   The system now has all the information it needs to enforce your cross-project and cross-TG exclusion rules in real-time.

For completed (historical) projects or Target Groups, the system applies a fixed, non-configurable 90-day exclusion period for any respondent with a Complete status.

• If a respondent completed an excluded survey less than90 days ago, they are blocked.

• If it has been > 90 days, the exclusion has expired, and they are eligible to enter (assuming no other rules apply).

If a respondent is currently "in client survey" in an excluded Target Group, they are blocked from entering another mutually exclusive Target Group.

No. Respondent exclusions work alongside ID-based exclusions.

• Respondent ID Exclusions: Ideal for permanent blocklists where you know exactly which respondents should never enter.

• Respondent exclusions: Dynamic and time-bound (90 days), based on project activity.

Marketplace users typically manage exclusions via Survey Groups.

In Cint Exchange, the Project is the container, and Target Groups are the individual surveys.

With respondent exclusions, you will now:

1. Use Respondent exclusions between projects/Target Groups for future work.

2. Use Respondent ID Exclusions with Marketplace IDs as a bridge for any legacy surveys where you need exclusion continuity.

Exclusion Groups are being deprecated. The new unified endpoint allows you to pass Project IDs and Target Group IDs directly in a single, atomic call. We recommend migrating to the newest API versions to take full advantage of this feature.