Field notes · 13 March 2026
Identifiers that keep journeys readable
Why consistent customer identifiers matter more than adding another chart when apps share a journey.
Cross-channel analytics fails quietly when each service app invents its own way to recognize a person. Guest checkouts, temporary session IDs, and reissued loyalty numbers all create parallel stories that never meet.
Start by listing every identifier already in use: account ID, phone, email, membership number, booking reference. Note which ones survive a password reset, a device change, or a desk override. Fragile identifiers produce fragile journey histories.
Privacy and retention rules belong in the same conversation. A durable ID is useful only when your policies allow joining records across apps for the purpose you intend. Measurement design and policy design should travel together.
Once a stable join key exists for the journeys you care about, charts become easier to trust. Until then, treat multi-app funnels as provisional and label them as such for decision makers.