Cint Exchange Feed Opportunities and Respondent Outcomes FAQs

Feed (formerly known as on-time-supply or ots) is a next-generation API subscription that enables our supply partners to make faster, more accurate decisions, improving their brand and respondent experience in the Cint Exchange.

• Opportunities pushes survey information including, qualifications and quota data in near real-time for all surveys in an opportunity watch list.

• Respondent Outcomes in the Cint Exchange provides key data on the outcome of a respondent session, making it easy to track the performance of your integration and users.

Feed is most effective for customers who have an existing supply API integration with Cint or net-new customers who are open to completing an enterprise-level integration with Cint.

Customers who access the Cint Exchange through match or another type of integration should speak to their customer success representative to see if it is the right fit for them, or email info@cint.com if they aren’t sure who to speak to.

Feed does the hard work of pulling information from the Cint system, and pushing it to our partners in one message. This all happens in near real-time, allowing users to make faster, more accurate decisions for their audience and get them to the right surveys at the right time.

Feed is a free for all Cint supply customers.

By giving our partners more data, much quicker, feed empowers them to make more accurate decisions to put their users into better, more relevant surveys. This means their community of respondents will have a greatly improved survey experience.

Our developer docs can be viewed here. However, feed is only suitable for partners who have good technical resources, and are comfortable working with webhooks. If you aren’t sure if feed is right for you, reach out to your customer success representative, or email info@cint.com if you aren’t sure who to speak to.

Getting setup with feed can be done quickly and easily, but the timeline will vary depending on your situation. We recommend speaking to your customer success representative to get a personalized answer or contact us by emailing info@cint.com.

Our partners can discuss feed with their customer success representative. They will be able toadvise if feed is the right fit and help you get our partners set up.

Our integration consultants and customer success representatives will be available to provide any support you need.

If we cannot deliver a message or your server returns a non-2xx status code, our system will retry for up to 24 hours using an exponential back-off strategy.

• If we receive a successful response, you will be sent the latest available update.

• If delivery of a message remains unsuccessful after 24 hours, your subscription will be deleted, regardless of whether other messages were successfully delivered during that period.

In the unlikely event of a Cint system outage, once systems are restored, you will receive the last saved message for each survey ID.

For details on what happens if we are unable to deliver messages related to deactivated surveys before subscription deletion, please refer to the next section.

Acknowledge messages with a 2XX response immediately, prior to any post-processing you may do on your end. This will ensure that we do not think the message delivery failed.

No. If a subscription is deleted due to failed requests, any missed updates related to survey deactivations will not be resent. When you restart your subscription, you will only receive message bursts for active surveys that meet your subscription criteria.

You should deactivate any surveys for which you do not receive an update in your new stream. You can also identify active surveys—those allocated or with an entry link created—by calling our inventory endpoint. Additionally, we recommend implementing logic to automatically deactivate a survey in your database if you receive an initial (prescreener) status of 42 (survey closed) via your redirects or Respondent Outcomes subscription.

See overquotas terminations guide for more information.

No, at this stage suppliers can only create one subscription for opportunities and one for outcomes. However, multiple operators are available to build out complex and nested subscriptions.

There are several reasons why your webhook subscription might not be working. Below are common areas to troubleshoot. It is recommended to have an internal notification system in place to alert you when a message's status returns a non-2xx response.

• Validate your callback URL: Run a GET show an opportunity subscription or show an outcomes subscription request to confirm your callback URL is correct.

• Check SSL installation: Ensure your destination server has SSL installed.

• Review subscription filter criteria: Verify that your filter criteria is using the correct arguments and formatting. A member of your account team can assist with this.

• Confirm expected payload structure: Recheck the example payload in our API documentation to ensure your servers are correctly configured to process the information. If needed, your account team can provide an example response.

• Check for system filters blocking requests: Have you created any filters that could be rejecting messages? For example, if your system blocks surveys with a study_type of "recontact", but your subscription criteria does not explicitly exclude these, any messages containing recontact surveys will fail.

• Verify webhook security authentication: If implementing our authentication, ensure it is configured correctly and as per our documentation.

• Assess server capacity: Confirm that your servers can handle the frequency and size of incoming messages. For Opportunities, you can adjust survey data frequency, payload size, and the number of surveys received by configuring specific arguments in your subscription.

  • Surveys, especially in the US, may include large qualification or quota pre-code selections based on regional targeting (e.g. zip codes). These selections can result in the survey_quotas and/or questions model exceeding 10,000 rows. Ensure that your system is capable of handling these scenarios.

• Check for firewall restrictions: Ensure that firewalls are not blocking or delaying webhook requests.

• Review timeout settings: Make sure your system allows sufficient time to process incoming messages.

Below are some example subscriptions. These subscriptions are only a sample of the possibilities and represent some common use cases.

See the marketplace response codes and client response codes articles for more information.

1. If you would like to receive a message each time a respondent terminates on a Cint survey protection services or link manipulation response code or is reconciled, use this subscription:

{
  "callback": "https://www.supplier-delivery-endpoint.com/api/outcomes",
  "outcomes":
    [
      {
        "client_status": {"in": [11, 26, 28, 35, 38, 134, 135]},
        "marketplace_status": {"in": [3, 32, 37, 131, 238, 240, 241]}
      }
    ]
}

2. If you would like to receive a message each time a respondent is termed due to an overquota, is reconciled, or fails secure client callback, use this subscription:

{
  "callback": "https://www.supplier-delivery-endpoint.com/api/outcomes",
  "outcomes":
    [
      {
        "client_status": {"in": [40, 10, 26, 11, 28, 235]},
        "marketplace_status": {"in": [40, 41]}
      }
    ]
}

3. If you would like to receive a message for all session outcomes, use this subscription:

{
  "callback": "https://www.supplier-delivery-endpoint.com/api/outcomes",
  "outcomes": 
    [
      {}
    ]
}

No, we do not provide a PID (panelist_id) or MID (session_id) if the respondent terminates on Cint Exchange (marketplace) response code 236, which indicates the user opted out on the consent form. These values will also not be returned if they were not provided in the user's entry link into our system.

No. As the user navigates through the Cint Exchange, their session outcome may change, especially if they pass the prescreener checks and qualify for a survey. You should expect multiple messages related to a user's session and should store the last message received as the final outcome.

No, you will be receiving this information via Opportunities once you have created a subscription.

No, survey pricing will be returned in the opportunity message.

Yes, updates will be pushed for all live surveys where you have an allocation and meets the criteria specified in your subscription.

Click feed opportunities message reason to find out more.

Once your subscription is activated, Cint will send all surveys that are currently live on the Cint Exchange that meet your criteria. As this could be a large number of surveys, you may receive multiple messages over a period of time that represents this 'setup'.

You will also begin to receive messages for new surveys, then messages for surveys that have changed, meeting your criteria.

By default, each callback message will be delivered every 15 seconds and will contain up to 1,000 surveys, with a maximum data size of 8 MB. You can adjust the frequency of message delivery, the size of the payload, and the number of surveys each callback message contains by setting filters in your Opportunities subscription. For detailed instructions on creating these filters, please refer to the arguments section of the Opportunities documentation.

Please note, if you are receiving data for our high-demand countries and set the payload filters to their minimum values, this could impact your ability to stay current with survey updates. After making any filter adjustments, please review your integration performance to ensure the changes have not negatively affected it.

We don't currently have the ability for you to replay missed messages. You can relaunch your subscription to receive a fresh batch of data or simply wait for updates to appear.

Any changes to the data that is included in feed Opportunities models will trigger an event. There are no limits, so for every complete that occurs, it will trigger a new message.

Yes, you can adjust the frequency of message delivery, the size of the payload, and the number of surveys each callback message contains by setting filters in your Opportunities subscription.

See the arguments section of the Opportunities documentation for more information.

Please note, if you are receiving data for our high-demand countries and set the payload filters to their minimum values, this could impact your ability to stay current with survey updates. After making any filter adjustments, please review your integration performance to ensure the changes have not negatively affected it.

We always send the oldest surveys changes first, 1000 at a time. If a survey changes whilst it’s waiting the data is updated, but its place in the line is not, so the data in a packet is always the latest for a given survey. After a survey is sent if it changes again it goes to the end of the line. In practice after the initial burst, all changes get sent every 15 seconds. It is unusual to get over 1000 unique surveys that change in each 15 seconds interval.

No delays to the burst will occur. However, if the payload of qualification and quota data is very large, the batches will be broken up and sent more frequently than the 15 sec updates. If the data is still executing it will wait before sending the next batch.

Updates to qualification and quota data is the same as all other data, which is about a minute after the update is made.

Property names will move to snake_case and SurveyStatusCode and SurveyStillLive properties are being removed, these are shown on the quota call.

Once our existing customers confirm they are using the new qualification and quota feature, we will deprecate these endpoints.

The entire package of data is sent with each update.

Yes, qualifications and quotas are an optional data set, requiring opt-in. You will need to include filter “include\_quotas”: true to enable qualifications and quotas data

Optional. qualifications and quotas is an optional opt-in feature.