Headless 360Intermediatedata-cloudanalyticseventsattribution
Connect headless channels to Data Cloud for unified analytics
Real World Scenario
Mobile app behavioral events sit in Firebase while web uses GA4. Marketing cannot attribute cross-channel journeys in Salesforce.
Expected Answer
• Stream mobile and web events to Data Cloud via Ingestion API with unified schema
• Shared identity keys linking anonymous and authenticated sessions
• Map events to Engagement DMO for journey analysis alongside Commerce orders
• Server-side event forwarding reducing client SDK data loss from ad blockers
• Consent flags attached at ingestion for analytics vs activation separation
• CRM Analytics dashboards consuming harmonized cross-channel datasets
• Validate event volume parity with source analytics tools weekly
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Stream mobile and web events to Data Cloud via Ingestion API with unified schema. Shared identity keys linking anonymous and authenticated sessions. Pick based on your integration pattern and team capability. Headless without unified analytics is flying blind—instrument events at architecture design phase, not post-launch. Balance speed of delivery with maintainability.
Architect Perspective
Headless without unified analytics is flying blind—instrument events at architecture design phase, not post-launch.