The current implementation of visitor stitching relies on setting a unique identifier on an attribute for a visitor that never changes. So this is a 1 to 1 relation of a visitor with a unique identifier.
Sometimes a visitor has multiple different values for the same identifier. This would be a 1 to n relation of a visitor with a specific type of identifiers (phone numbers, email addresses, order ids, basket ids, session ids).
1. Multiple baskets filled without being a customer yet and the sale is completed through a channel that can't know another unique identifier for that basket, other than the basket ID (such as an abandoned email, sms, social, etc.)
2. Multiple email addresses for the same person.
3. Deduplication of customer IDs within a CRM.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.