Cint Exchange Match integration FAQ

Cint proactively pays suppliers for all completes sold in the Cint Exchange (formerly Lucid Marketplace), including OTC completes. as a result, Cint Exchange suppliers do not need to invoice Cint to receive payments.

Cint pays on a monthly basis per contract terms, and payments are made in US dollars (USD). payment process for Cint Exchange suppliers

You can login to the Lucid Marketplace to review the "sample sold report". it will show you a quick summary of the monthly revenue. however, please note that the monthly payment amount is not finalized until the month-end reconciliation adjustments are completed.

See sample sold report for more information.

Any revenue from OTC activity will be included in your monthly Cint payment, consolidated with your revenue from Cint Exchange activity.

Lucid Measurement is Lucid's ad-effectiveness product. it intercepts the user flow to show them a short survey if Cint detects the presence of a specific cookie. after completing the survey, the user will be redirected to the intended survey and then back to your platform normally. Lucid Measurement payment is separated from normal Cint Exchange sample sold so it is shown as an additional amount on top of your monthly payment.

You can read more about the product here and find more details on tracking and reporting of Lucid Measurement completes: working with Lucid Measurement.

Please contact accounting@luc.id and your CSM to update it accordingly.

To help you test your integration, we've created specific test surveys that allows you to test the user-flow and redirects. to target these test surveys you'll need to append the "**tar**" parameter to the entry link accompanied by the appropriate country-language value.

More details on how to test can be found here: Cint Exchange Match implementation guide.

We don't offer a sandbox environment for Match integration.

As a **match** supplier you are exposed to the same inventory as all the other **exchange** suppliers. there is no limitation on the number of completes you can achieve on the platform, the only limitation may come from the number of completes available in certain smaller markets. sometimes a buyer will set a supplier **allocation** directed to one of a few partners, this constitutes a small percentage of traffic in the Cint Exchange and is used in a few circumstances:

• When buyers want to get a certain number of completes from a partner, usually based on pre-existing relationships.

• as **OTC**, when a number of completes at a certain cost is agreed between the parties prior to the setup.

• **Trackers** where buyers need to target a similar user-base over a period of time.

Any completes with no allocation, or where you are in the allocated group will be available to you through your **match** integration.

We recommend limiting the number of times users can attempt Cint Exchange **match** sessions on a daily basis, especially for newly registered users, recently reconciled users, and users who have already been terminated that day.

More best practices are within our Cint Exchange Match implementation guide. please also read through our best practices for **supply quality** here: strategies and best practices for supplier quality.

We recommend you map to *at least* the critical qualifications for each country-language pairing for which you will be sending respondents, and ensure that you are profiling your respondents on the qualifications for which you are mapped to the Cint system. we generally see increased success and performance when suppliers are able to map to more than the **critical qualifications** and encourage you to map to our entire **qualification library** if you have the **bandwidth**.

here is more information about our **standard qualifications** and a list by country-language.

Our current system only supports a single **URL** that is used to redirect the respondent and communicate the final status of their session, we are unable to support the **server-to-server postback** at the same time.

There are a few possibilities as to why you might be getting hashing errors. you can use our hashing validation tool to check if you are using the correct hashing. make sure you include the entire **URL**, including the trailing '**&**'. we also recommend you check that you are using your correct hashing **secret key** and the **hash** is placed at the end of the **URL**.  

The following study types are blocked:

• 2 - diary

• 5 - IHUT

• 8 - community build

• 9 - face to face

• 11 - recruit - panel

Please contact your dedicated **customer success manager** to update your redirects.

Cint makes reporting available to you through the Lucid Marketplace. the best place to start to understand the status of individual users is the supplier breakdown report which is used to track all user sessions and their associated status within a specified date range. supply reporting field definitions will also help you to better understand the field definitions within that report and all other supplier reports.

Your **CSM** will also share **dashboards** on a regular basis and can walk you through how to read and use that reporting.

For **match** customers, **respondent outcomes** is limited to programmatically tracking reconciliation **client response codes** (11, 26, 28, 38). it cannot be used to track broader session activity. **API credentials** are required to access this product; please contact your **account team** for assistance.

Demographic information is stored by Cint for up to thirty days when it is passed within the entry links or answered by respondents in the Cint **pre-screener**. if the information is passed, Cint will not re-ask the questions in the **pre-screener**. however, once a respondent enters the client side survey, Cint has no control over the visibility into what happens in the client side survey. if a question is re-asked in the client side survey, it is likely due to the buyers' specific data and analysis requirements or for verification purposes.

Many of our suppliers use **third party services** to detect a respondent's geo-location **IP address**. beyond that there may be further inferences that could be made by looking at the respondent's **browser language** or the location they report to be in via profiling.  

We are aware there are some discrepancies among surveys. this is because Cint is a marketplace which consists of so many different buyers (**and** supply partners) which causes variations of quality. one of Cint's top priorities is to improve and maintain consistency of survey quality. Cint has built a **content audit team** to test surveys to ensure proper set-up **and** content, as well as provide feedback to buyers to improve their quality. due to the sheer volume of surveys on the platform we are unable to test every single survey, but Cint monitors **new buyers** **and buyers** who are flagged for **survey quality issues**.

Please flag any problematic surveys to our **support team** (support@cint.com) **and** copy your **CSM**.

Buyers may change the status of a respondent session after a survey has closed. this is known as the **reconciliation process**. your respondents can be reconciled from **term** to **complete** (positive reconciliation) or **complete** to **term** (negative reconciliation). acceptable reasons for **negative reconciliations** are **straight-lining**, **speeding**, **inappropriate open-ends**, etc. you can read more about our reconciliation policy

Buyers have until the last day of the month following the original **complete date** to reconcile a respondent; **supply partners** are not paid for respondent sessions that are reconciled to **term**. partners with a **reconciliation rate** ten percentage points greater than the **platform average** will be put on the partner improvement program. continued inclusion in the **PIP** can lead to removal from the Cint Exchange. you can obtain **reconciled sessions** from:

• The self-serve ID reconciliation report

• a daily **email** subscription to the security termination and reconciliation CSV report. ask your Cint **account team** to set-up a subscription.

• a respondent outcomes subscription. receive programmatic **notifications** to your **callback URL** regarding reconciled users. for **match** suppliers, this service is only available for tracking reconciliation **response codes**. **API credentials** are required to access this product; please contact your **account team** for assistance.

See respondent experience article under section “concurrent sessions” for the answer.

Cint has inventory in over 90 countries around the world. our top markets are the united states, united kingdom, germany, france, canada, australia, india, china, brazil, japan **and** mexico. if you are considering expanding into a **new market** or region please reach out to your **CSM** for more information.