How to exclude respondents within the same project

This guide explains how to configure a target group to automatically exclude respondents who have already completed a survey within the same project on the Cint Exchange. Excluding respondents helps maintain sample quality, prevents over-surveying the same individuals, and ensures data independence across your project.

Prerequisites:

• None. You can only adjust the Exclude within this project setting during the draft stage.

---

Excluding respondents within the same project is controlled by a simple boolean value set value:

Step 1: Add the exclusion object to your request

You can alter the Exclude within this project boolean using one of the following endpoints:

• Create a target group in draft status
• Update a target group in draft status

Example success response:

{
  "id": "01JX2X0N5RTR012AYDTA83QWTW",
  "name": "My Excluded target group",
  // ... other target group details
  "exclusion": {
    "enabled": true,
    // ...other fields
  },
  // ... other fields
}

On a successful response, all future respondent's entering your survey who've taken other surveys within the same project will be denied access.

important

Make sure to set enabled to true otherwise your target group won't have Exclude within this project enabled. You can only alter this value when your target group is in draft status.

Step 2: Verify exclusion settings (optional)

After a successful API call, verify that the exclusion settings are correctly applied to your target group by calling the Retrieve a target group in draft status endpoint.

Example success response:

{
  "id": "01JX2X0N5RTR012AYDTA83QWTW",
  "name": "My Excluded target group",
  // ... other target group details
  "exclusion": {
    "enabled": true,
    // ...other fields
  },
  // ... other fields
}

---

Troubleshooting

• HTTP 400 Bad Request:
• Check for typos in parameter names or incorrect data types (true/false for booleans).
• Ensure all required fields for target group creation/update are present.
• 401 Unauthorized: Your token is either missing, invalid, or expired.
• 403 Forbidden: You don't have the necessary permissions to perform this action.
• 404 Bad Request: Check that the IDs located in the path and body are correct.
• 409 Conflict: Another job is already running for this target group.
• Respondents Still Qualifying After Completing Other TGs:
• Double-check that enabled is set to true on the target group you are trying to protect: Ensure the other target groups are within the same project as the target group where you enabled exclusion.