Data CloudIntermediateweb-sdkidentitystitching
Troubleshoot web SDK identity not stitching anonymous to known session
Real World Scenario
Logged-in customers still appear as anonymous web profiles; browse history never attaches to unified individual after login.
Expected Answer
• Verify identity event fired on login with correct Id scheme
• Check cookie consent blocking SDK until acceptance
• Same domain and subdomain cookie scope configuration
• Login event must include stable Id matching CRM key
• Test Safari ITP and private browsing behavior
• SDK initialization order: consent then identify then page events
• Compare network tab SDK payloads staging vs production
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Verify identity event fired on login with correct Id scheme Also consider: Check cookie consent blocking SDK until acceptance In practice: Same domain and subdomain cookie scope configuration Balance speed of delivery with maintainability.
Architect Perspective
Anonymous-to-known stitch is highest-value web use case — test login flows not just page views.