Data CloudIntermediatesegmentsactivationdebugging
Debug segment count mismatch between Data Cloud and activation platform
Real World Scenario
Marketer sees 850,000 members in Data Cloud segment but Meta audience sync reports 720,000; leadership questions data integrity.
Expected Answer
• Compare segment refresh timestamp vs activation job timestamp
• Activation may exclude records missing required match keys (email hash)
• Consent and opt-out filters applied only at activation explain gap
• Deduplication rules differ: household vs individual counts
• Review activation error logs for rejected records batch
• Reconcile sample of 100 IDs manually across systems
• Document expected shrinkage factors in runbook
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Compare segment refresh timestamp vs activation job timestamp Also consider: Activation may exclude records missing required match keys (email hash) In practice: Consent and opt-out filters applied only at activation explain gap Balance speed of delivery with maintainability.
Architect Perspective
Count mismatches are usually rule differences not bugs — document shrinkage pipeline explicitly.