In addition to Marketplace survey opportunities, respondents may also be eligible for Lucid Measurement opportunities. Lucid Measurement surveys support ad effectiveness studies and are conducted in real time. Respondents are selected based on prior media exposure, demographics, and other profile attributes, giving Supply partners additional monetization opportunities.
Respondent flow
Survey takers that are identified as being exposed to an ad enter and answer questions related to the brand lift survey before entering the main survey.
At the end of a Lucid Measurement software survey, respondents receive a “Thank you!” message before being sent to the originally intended survey.
A respondent who does not meet the survey criteria (e.g., qualifications, quotas) of the Lucid Measurement opportunity will be sent directly to the originally intended survey.
Lucid Measurement respondent flow
Maximizing Lucid Measurement opportunities with identity data
As the advertising space is moving away from cookies, Cint is focused on building an ecosystem of direct and first-party integrations with a variety of ad platforms and media companies and integrating universal ID frameworks. By utilizing unique identifiers such as hashed email addresses (HEMs) and mobile ad IDs (MAIDs), Cint ensures the continuity of Lucid Measurement opportunities while reducing reliance on cookies. This identity data enhances respondent targeting for media measurement studies.
How to pass identity data to Cint
To transmit these identifiers to the Cint Exchange, append the MAID and cint_email parameters to each respondent’s entry link.
Key requirements
Parameter Name | Parameter Requirements |
|---|---|
maid | GUID format. If the MAID value is not available for a respondent, the 'MAID' parameter should be omitted from the entry links for that respondent. |
cint_email | Respondent's email address Only real respondent emails must be used — no dummy, placeholder, or test emails are permitted. Before hashing, the email must be cleaned (see below). The cleaned email must then be UTF-8 encoded to ensure consistent handling across all character sets, including non-ASCII characters. The encoded email is then hashed using SHA-256 function, and the resulting hash hex-encoded as a 64-character lowercase hexadecimal string. Correct sequence: Email → Clean → UTF-8 Encode → SHA-256 → Hex Encode Email cleaning Cleaning normalizes the email so that the same address always produces the same hash, regardless of how it was originally entered. To clean an email:
a) Remove all dots (.) from the local part (before the @). b) Remove the plus sign (+) and all subsequent characters from the local part. Both "ExaMplE@Cint.com" and " example@cint.com " clean to the same value, example@cint.com, and therefore produce an identical hash. Cleaning must always be applied before hashing — without it, the same person's email can produce different hashes and will fail to match across the supply chain. Examples (note that all inputs clean to example@cint.com and yield the same hash):
|
For detailed guidance on generating and formatting entry links, refer to our resources:
Feed (formerly API) integrated partners: generating API entry links
Match (formerly Link) integrated partners: entry link section of the Cint Exchange Match implementation guide
Tracking Lucid Measurement activity
Lucid Measurement surveys are tracked using a unique set of response codes in Cint Exchange reports and on redirect urls: a 70 for a complete interview, an 80 for a terminated session or -1 if the respondent is not eligible based on survey qualification criteria. A set of 6 variables are auto-appended to your redirect URLs whenever a respondent touches a Measurement survey.
The ProofCPI variable is only appended in the event of a complete, and can be used to reward a respondent.
Lucid Measurement session outcomes can also be tracked through Feed Respondent Outcomes v2, using the study_type property to identify this activity, and the proof_cost_per_interview property to determine the gross CPI (in USD) for a completed Measurement survey.
Variables included on redirects
Variable | Description | Possible values/data type |
&ProofStatus | Identifies if a respondent completed or termed | complete = 70 term or opt-out = 80 not eligible = -1 |
&Proof | Identifies if a respondent was taken to a Lucid Measurement survey | 1 |
&ProofFormat | This is a legacy field that is no longer actively used | Integer |
&ProofSessionLOI | Identifies the amount of time a respondent spent in a Lucid Measurement survey (minutes) | Integer |
&ProofSurveyNumber | Identifies the survey number associated with a Lucid Measurement survey. The unique number is associated with a survey. | Integer |
&ProofCPI | Identifies the gross CPI in USD for the complete on the Lucid Measurement survey. The value is based on the Proof Pricing Grid. The ProofCPI variable is only appended in the event of a complete, and can be used to reward a respondent. | Float |
Reporting and invoicing
Marketplace suppliers will receive a monthly Lucid Measurement Statement from the Cint Accounting Team detailing Lucid Measurement activity and payment. This statement is sent to suppliers at the beginning of the month (typically by the end of the first full week of the month) and reflects the activity of the most recent hard-closed month.
The amount to be paid out for Lucid Measurement activity will not appear in any other Cint financial reporting. However, you can use the Supplier breakdown report to break out earnings by user PID. The final amount will be included in your net-90 payments.
Please note that revenue for Measurement activity is not currently reflected in the Sample sold report, which should only be used for non-Lucid Measurement financial reporting.