Private Exchange Feed integration guide

This article provides instructions for how to supply Private Exchange (formerly Private Marketplace) survey opportunities through a Cint Exchange Match (formerly Marketplace Supply Link) and/or API integration.

If your integration collects survey data from Feed (formerly OTS) Opportunities, please proceed to section "Identifying Private Exchange Demand For Partners Integrated with Feed Opportunities".  If your integration does not collect survey data from Feed Opportunities, but you are using one of our survey endpoints (e.g., List Marketplace Surveys, List Filtered Marketplace Surveys), please proceed to the section "Identifying Private Exchange Demand for Partners Integrated with Survey (offerwall) APIs".

Identifying Private Exchange Demand for Partners Integrated with Feed Opportunities

Suppliers using Feed Opportunities can identify Private Exchange buyers through the new “buyer_id” property.  While the “account_name” property will remain in the Opportunities model, “buyer_id” will become the preferred method for buyer identification across all aspects of the Cint Exchange.  Therefore any logic you have in place to identify buyers should be based on buyer_id.  Your Account Team will provide you with the relevant Private Exchange buyer IDs.

Additionally, we will be adding the “px_buyer_message” property to the Opportunities model. This field will allow Private Exchange buyers to communicate specific instructions regarding the project to a Supplier. Previously, this was referred to as meta data tag in the Cobra integration.  

Please Note: 

• The “revenue_per_interview” property will return the net value of the survey based upon your agreed rate card with the buyer.

• You are not required to recreate your subscription to see these new data properties

• The "px_buyer_message" property will be added to Feed Opportunities in June-25.

Properties in Feed Opportunities to support Private Exchange Delivery

Example Opportunities Model Response

{
      "survey_id": 12345678,
      "survey_name": "My Great Survey",
      "account_name": "Sample_Account",
      "buyer_id": 12345,
      "country_language": "eng_us",
      "industry": "other",
      "study_type": "adhoc",
      "bid_length_of_interview": 5,
      "bid_incidence": 50,
      "collects_pii": false,
      "survey_group_ids": [1258951],
      "is_live": true,
      "survey_quota_calc_type": "completes",
      "is_only_supplier_in_group": true,
      "revenue_per_interview": {
        "value": 1.35,
        "currency_code": "USD"
      },
      "total_client_entrants": 480,
      "total_remaining": 46,
      "completion_percentage": 0.15824915,
      "conversion": 0.39166668,
      "overall_completes": 188,
      "mobile_conversion": 0.28,
      "revenue_per_click": 0.35,
      "length_of_interview": 3,
      "termination_length_of_interview": 2,
      "relationship_type": "private",
      "respondent_pids": [],
      "message_reason": "new",
      "px_buyer_message": [
        "some-example-text",
        "another-tag"
      ],

Identifying Private Exchange Demand for Partners Integrated with Survey (offerwall) APIs

Suppliers using Survey (offerwall) endpoints can identify Private Exchange buyers through property “AccountName”. Your Account Team will provide the names of the Private Exchange buyers.  Please Note: the “RPI” property will return the net value of the survey based upon your agreed rate card with the buyer.

If you are collecting the meta data tag via your Cobra integration and require this information in the Cint Exchange, you will be required to integrate with our Feed Opportunities product in order to collect this information via the new data property “px_buyer_message”. This field will allow Private Exchange buyers to communicate specific instructions regarding the project to a Supplier.  If there is no agreement in place to collect the px_buyer_message data, you can manage Private Exchange inventory through your existing Cint Exchange integration using the AccountName property, as stated above. An integration with Feed Opportunities is not required at this stage.

Integrating with Feed Opportunities (if required)

To avoid delays, we recommend at a minimum using Feed Opportunities to replace the survey (offerwall) endpoint. This will allow you to collect information on new surveys, including Private Exchange demand. Opportunities includes all the data available in the survey endpoints, plus more.  

More Info: For more details on identifying Private Exchange inventory via the new data properties in Feed Opportunities, refer to the section "Identifying Private Exchange Demand for Partners Integrated with Feed Opportunities

Please contact your Integration Consultant if you have further questions related to integrating with Feed Opportunities, alternative please review our online material:

• Feed Opportunities Documentation

• Cint Exchange Feed Opportunities and Respondent Outcomes FAQs

Example Surveys Model Response

"Surveys": [
    {
      "SurveyName": "Asthma Sufferers",
      "SurveyNumber": 457751,
      "SurveySID": "26CB55E2-74CC-4E19-88E3-7F2F8D4DE74D",
      "AccountName": "Sample Company",
      "CountryLanguageID": 11,
      "LengthOfInterview": 12,
      "BidIncidence": 30,
      "Conversion": 1,
      "RPI": {
        "Value": 1.35,
        "CurrencyCode": "USD"
      },
      "FieldEndDate": "\/Date(1541000567000-0600)\/",
      "IndustryID": 30,
      "StudyTypeID": 1,
      "OverallCompletes": 5,
      "TotalRemaining": 995,
      "CompletionPercentage": 0,
      "SurveyGroup": null,
      "SurveyGroupID": null,
      "SurveyGroupExists": 1,
      "BidLengthOfInterview": 10,
      "TerminationLengthOfInterview": 6,
      "SurveyQuotaCalcTypeID": 1,
      "IsTrueSample": false,
      "SurveyMobileConversion": 0,
      "SampleTypeID": null,
      "CollectsPII": true,
      "IsOnlySupplierInGroup": false,
      "RelationshipType": "private",
      "RespondentPIDs": ["75530545", "30776758", "23180686"]
    }
  ]
}

Updating Integration Logic

If you have internal logic/processes built around Private Exchange data, you will need to make the relevant system adjustments, which may include: 

• Recommended for Feed Opportunities customers: migrate to using buyer_id from account_name

• Adjusting any internal survey selection or ranking logic which includes Private Exchange buyer identifiers to include the Cint Exchange buyer id or account name.

• Ensuring any internal processes connected to the data obtained from property px_buyer_message are continued.

Additional Requirements and Information for all Supply Partners

Tracking Private Exchange Sessions

You can track Private Exchange session outcomes in several ways:

• Supplier Redirects: Monitor respondent sessions via your supplier redirects.

• Feed Respondent Outcomes: Subscribe, if not already done so, to receive near real-time respondent session outcomes directly to your chosen webhook. The outcome response includes the buyer_id property, helping you identify Private Exchange sessions.

  • Additional Resource: Cint Exchange Feed Opportunities and Respondent Outcomes FAQs

• UI Reports: Use our reporting tools to extract session details. Refer to the reporting section of this article for more details.

Media Measurement

When respondents are sent to Private Exchange survey opportunities, Media Measurement functionality will be disabled, and users will not be intercepted.

Payment Process

Cint proactively pays Cint Exchange Suppliers for all completes in the Cint Exchange. As a result, suppliers do not need to invoice Cint to receive payments related to Private Exchange activity. Cint pays suppliers on a monthly basis per contract terms, and payments are made in US Dollars (USD).  

More Info: For more information, please see article Payment process for Cint Exchange suppliers

Reporting

Private Exchange activity is available to track in our Supplier Portal reports; simply use the Exchange Type slicer at the top of any report and select 'Private Exchange.' Private Exchange metrics are also available via UI reporting. The table below details how to identify Private Exchange data within each specific UI report. For same day monitoring, we recommend UI reporting, as Portal data carries a 24-hour delay.

Please note that Cint Exchange reporting does not indicate whether a session complete is either tentative or closed. Buyers on the Cint Exchange have until the 25th of the following month to finalize their reconciliation audit.  For example, if a complete occurred on July 1 or July 31, the buyer has until August 25 to complete the reconciliation audit.  After this period, sessions can no longer be adjusted, and the outcome status is locked in. Therefore, to view sessions tied to “closed” completes, please adjust the date range in your reports accordingly.