Skip to main content
Version: 2025-05-27

How to remove interlocked profiles from a launched target group

This guide explains how to convert an existing interlocked quota configuration in a live non-draft target group back into individual, non-interlocked quotas. This provides greater flexibility for fieldwork by easing potential complexity caused by highly specific interlocked segments.

While interlocked quotas offer precise control, they can sometimes limit feasibility or slow down fieldwork if the combined segments are too restrictive. Removing interlocks allows you to broaden your targeting for individual profiles without disabling the quotas entirely, which helps optimize fieldwork progress.

For more information on understanding interlocked quotas, check out our guide: Understanding interlocked quotas.

Steps to remove an interlocked quota​

Follow these steps to convert an interlocked quota into individual, non-interlocked profiles:

Step 1: Get the ID of the interlocked profile​

You'll need the unique ID of the specific interlocked profile you want to remove.

  • Action: Make a GET call to the Get profiles endpoint for your live target group.
    • GET https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/profiles
  • Purpose: This request returns a list of all profiles associated with your target group. Look for an object with an interlocked_profile structure or an individual profile that has an interlock_id field.
  • Outcome: Identify and cache the id of the interlocked profile you intend to remove. This ID will typically be found within the interlocked_profile object itself, or individual profiles will point to it via their interlock_id field.

Example response snippet from GET /profiles showing an interlocked ID:

{
  "data": [],
  "interlocked_profile": {
    "id": "01JP2K4BKAAVS6RFRZ8NXMR3CA", // This is the interlocked profiler ID you need
    "name": "AGE, GENDER",
    "quotas_enabled": true,
    "depends_on_questions": [42, 43],
    // ... (rest of interlocked profile details)
  },
  "profiles": [
     {
       "id": "01JP2JKW9ZC2VHR9WKYP9SD4KV", // Individual Age profile
       "interlock_id": "01JP2K4BKAAVS6RFRZ8NXMR3CA", // Points to the interlocked ID
       // ...
     },
     {
       "id": "01JP2JKW9ZC2VHR9WKYP9SD4KZ", // Individual Gender profile
       "interlock_id": "01JP2K4BKAAVS6RFRZ8NXMR3CA", // Points to the interlocked ID
       // ...
     }
  ]
}

Step 2: Send the request to remove interlocks​

Make a POST request to the Remove interlocks endpoint, specifying the ID of the interlocked profile you want to dissolve.

  • API endpoint: POST https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/interlocked-profiles/remove
  • Path parameters: Include your account_id, project_id, and target_group_id in the URL.
  • Request headers: Include your API key and the Cint API version.
  • Request body: This should be a JSON object containing the interlocked_profile_id.

Example request body:

{
  "interlocked_profile_id": "01JP2K4BKAAVS6RFRZ8NXMR3CA"
}
  • interlocked_profile_id (string, required): The unique ID of the interlocked profile you obtained in Step 1.

Example cURL request for Remove interlocks: This example demonstrates removing an interlocked age and gender quota with ID 01JP2K4BKAAVS6RFRZ8NXMR3CA from a target group in a paused state.

curl -X POST \
  'https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/interlocked-profiles/remove' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <YOUR_JWT_TOKEN>' \
  -H 'Cint-API-Version: 2025-05-27' \
  -d '{
    "interlocked_profile_id": "01JP2K4BKAAVS6RFRZ8NXMR3CA"
  }'
  • Outcome: A successful POST request will return an HTTP 200 OK status code. The response body will contain the updated target group profile structure.

Example response from Remove interlocks: The response will show the individual profiles (e.g., age and gender) now present in the data array, each with is_interlocked: false, and the interlocked_profile object will no longer be present or will be null. Their quotas_enabled will remain true unless you explicitly disable them.

{
  "data": [
    {
      "id": "01JP2JKW9ZC2VHR9WKYP9SD4KV", // Individual Age profile
      "legacy_id": "246353061",
      "question_id": 42,
      "name": "AGE",
      "quotas_enabled": true, // Quotas remain enabled
      "description": "What is your age?",
      "conditions": { /* ... */ },
      "quotas": { /* ... */ },
      "is_interlocked": false // Now a non-interlocked profile
    },
    {
      "id": "01JP2JKW9ZC2VHR9WKYP9SD4KZ", // Individual Gender profile
      "legacy_id": "246353063",
      "question_id": 43,
      "name": "GENDER",
      "quotas_enabled": true, // Quotas remain enabled
      "description": "Are you...?",
      "conditions": { /* ... */ },
      "quotas": { /* ... */ },
      "is_interlocked": false // Now a non-interlocked profile
    }
  ]
}

Result: Your live target group will now contain multiple non-interlocked profiles for each question that was previously part of the interlocked section. Each of these individual profiles will have its quotas enabled by default.

Troubleshooting​

  • HTTP 404 Not Found: The account_id, project_id, or target_group_id in your URL, or the interlocked_profile_id in the request body, is incorrect or doesn't exist.
  • HTTP 400 Bad Request:
    • Ensure the interlocked_profile_id provided in the request body is valid and corresponds to an active interlocked profile within that target group.
    • Verify that the target group is in a non-draft (live) status.
  • Quotas still active: If you intended to disable the quotas completely, remember that removing the interlock only dissolves the combination. You must perform separate steps to disable the individual quotas if that's your goal.