Identity resolution

Identity resolution attempts to recognize people across channels and devices to create one unified customer profile. Connecting the dots across omnichannel customer journeys is one of the biggest challenges that marketers face today. With unified profiles, you can gain deeper insights which will help you deliver more personalized messages and offers.

Events SDK feature identifies your website’s visitors as customers if they fill in the email or phone number field. We can identify if a customer is a visitor, prospect or existing customer by tracking their online behaviour.

1. If cookie is created on device and collected add new Customer in Customer API as visitor
2. If same customer has new cookie on new dev ice it is treated as new visitor in Customer API until we match it with existing Prospect or Customer
3. If cookie has a new registration with no purchases or fills contact form, it is defined as prospect in Customer API
4. If prospect purchase is identified as event, we turn it into customer
5. If we identify new visitor with existing customer, we match the new cookie and delete a new visitor. 

Note:

• Customers who don't have transactions are still CUSTOMERS
• People who bought something on e-shop but haven't registered are CUSTOMERS
• Visitors who left any id (email or phone number) are PROSPECTS
• Visitors who didn't leave any id (email or phone number) are VISITORS
• Prospects who didn't give consent are PROSPECTS
• Prospects who gave consent are PROSPECTS