Exclusions
Exclusions
Section titled “Exclusions”Clients may choose to exclude certain respondents from a project for various reasons, such as data diversity or quality. Respondent exclusions are defined in the opportunity cells. An opportunity with attribute: 28
and a kind: static-invites-collection
, and negate: true
denotes respondent exclusions. Respondents excluded from an opportunity will be disqualified.
[ { "tag": "d559212d-7984-4239-89c2-06c29588d79e", "attribute_id": 28, "negate": true, "operator": "OR", "kind": "STATIC_INVITE_COLLECTIONS", "invite_collections": [ "28_2171139" ] }]
Partners can avoid unnecessary terminations by filtering out excluded respondents from the opportunity altogether. To retrieve the list of respondent IDs
, partners must get the IDs in the invite_colLections
array from the static-invite-collection
.
{ "invite_collections": [ "28_2171139" ]}
Then use the invite_colLection IDs
to call the /download-invite-collection
endpoint.
POST /download-invite-collectionHost: https://registry.rex.dynata.comdynata-access-key: partner_access_keydynata-expiration: request_expirtationdynata-signature: signature
{ "id": "28_2171139"}
If successful, the endpoint will respond with a list of invite notifications for each exclusion in CSV
format. Each row contains an id
, collection_id
, respondent_id
, expiration
, created
, and modified
columns.
id,collection_id,respondent_id,expiration,created,modified1,28_2171139,respondent1234,2025-03-21T00:55:32.344Z,2024-03-21T18:16:12.189727Z,2024-03-21T18:16:12.189727Z2,28_2171139,respondent5678,2025-03-21T00:55:32.344Z,2024-03-21T18:14:45.694610Z,2024-03-21T18:14:45.694610Z3,28_2171139,respondent9101,2025-03-21T00:55:32.344Z,2024-03-16T13:13:51.891820Z,2024-03-16T13:13:51.891820Z