The following is a high-level overview of the Lucid Measurement integration process.
Overview
Lucid offers server-to-server data collection to measure advertiser media exposures as an alternative implementation option to pixel-based tracking. This is facilitated through direct partner integrations.
This option offers a more sustainable solution to measurement by ensuring a complete, accurate, and compliant data collection process between Lucid and the integrated partner. Further, complete, accurate, and compliant data improves survey performance and drives smarter decisioning for end-customers, which benefits both Lucid and the integrated partner.
Considerations
The following must be taken into consideration prior to the kick-off call.
Explore User Matching
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 Lucid hosts match table with users tied to Lucid respondent ids (RSIDs).
Identify countries of interest.
Ensure user deletes are considered and Lucid accepts weekly files for any users that may have opted-out via the partner consent process.
Provide Impression Data
Evaluate required campaign impression data fields necessary for integration.
Establish partner to Lucid campaign impression mapping process.
Ensure file delivery requirements can be met including file content, cadence, and delivery method (Lucid AWS/S3 bucket)
Process Expectations
Complete considerations outlined above.
Discovery/Kick-off
Define use cases
Review specs
Determine feasibility
Ensure we can match/reach enough users
Scope and Design
Document integration details and timelines
Development and Testing
Production Release and Validation