Data CloudAdvancedattributionmarketinganalyticsjourneys
Implement cross-cloud attribution with Data Cloud
Real World Scenario
CMO wants multi-touch attribution connecting ad impressions, email clicks, store visits, and purchases across channels already ingested.
Expected Answer
• Unified Individual as attribution entity with timestamped engagement events in Engagement DMO
• Define attribution model rules: first-touch, last-touch, linear, or data-driven in CI
• Resolve identity across devices for consistent journey stitching
• Ingest offline conversions via POS with loyalty match keys
• CRM Analytics or external BI consuming harmonized journey datasets
• Holdout control groups validating incrementality not just correlation
• Privacy-safe aggregation preventing individual-level export to unauthorized teams
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Unified Individual as attribution entity with timestamped engagement events in Engagement DMO Also consider: Define attribution model rules: first-touch, last-touch, linear, or data-driven in CI In practice: Resolve identity across devices for consistent journey stitching Optimize for scale and operational observability.
Architect Perspective
Attribution is identity plus timestamp quality—architects validate stitching before debating model sophistication.