Data syndication integration

Prev Next

The following is a high-level overview of the data syndication integration process. Refer to the S2S Media Partner Onboarding and Activation Guide for more detailed information.

Overview

Lucid collects demographic information in its respondent screening process to qualify a respondent into a given survey opportunity and ensure compliance. The attributes generally include census type information such as age, gender, household income, occupation, location, and more. Partners can license this data for validating their first, second, and third-party targeting segments.

Considerations

The following must be taken into consideration prior to the kick-off call.

Explore user matching

  1. Identify sources of inventory for optimal user coverage:

    • Preferred matching method(s) cookie sync, device IDs, hashed emails/HEMs, IP address, direct offline user match.

    • Trackable inventory explores relevant domains, inventory, expected volume of users to maximize overlap.

    • Data storage hosts a match table with users tied to Lucid respondent IDs (RSIDs), it is recommended both Lucid and partner host a match table to maintain integration efficiency

  2. Identify countries of interest.

  3. Ensure user deletes can be supported, Lucid provides a weekly file with respondents (RSIDs) who have opted out.

Receiving demo data

Evaluate data fields and availability by market

Determine if file delivery requirements can be met including file content, cadence, and delivery method.

Lucid recommends partner-hosted AWS/S3

Process expectations

  1. Complete the considerations outlined above.

  2. Discovery/kick-off

    • Define use cases

    • Review specs

    • Determine feasibility

    • Ensure we can match/reach enough users

  3. Scope and design

    • Document integration details and timelines

  4. Development and testing

  5. Production release and validation