When you are using both Voyado Product Discovery and Voyado Customer Engagement, you can unlock a new set of features. One of them is the ability to identify customers on a Product Discovery-powered site, using contact information from Customer engagement. This article explains how the two products link a visitor’s data and what that link means for privacy.
How Customer Engagement and Product Discovery identify the same visitor
One of the ways a retailer can benefit from connecting the two Voyado products, is advanced, cross-channel personalization and deeper understanding of the site visitor.
This is achieved by sharing and maintaining a synchronized unified identifier across both systems. Where the end-customer is cross-identified, data such as behavioral data, audiences and recommendations can be used across the two products to support Connected capability features.
The customerKey is the unique identifier for a visitor on the website and is required for every request to the Product Discovery API. In Voyado Customer Engagement, the corresponding identifier is the DiscoveryKey. The customerKey and DiscoveryKey represent the same value for the same individual.
For Connected capability purposes, the DiscoveryKey is used to link the same end-customer across Customer Engagement and Product Discovery. The ContactID is an identifier used inside Customer Engagement for the Contact record and may also be processed in connection with the linked end-customer profile where a DiscoveryKey/customerKey is present.
When are visitors cross-identified?
Cross-identification requires the visitor to be identified on your site. This can happen when a visitor:
- Logs in.
- Registers an account.
- Completes a purchase as a member.
- Clicks a link in a Customer Engagement email.
- Is recognized from a customerKey stored in a cookie.
When the link is made depends on your implementation and on when data is sent to each product. Either way, the contact record in Customer Engagement and the customerKey in Product Discovery must be linked. Once linked, the customerKey is connected to the ContactID, and pseudonymized behavioral data is synchronized with the identified person.
Processing of visitor data
Without cross-identification, Product Discovery stores a visitor’s behavioral data under a pseudonymized customerKey. This includes views, clicks, purchases, add-to-carts, search phrases, and session keys. Product Discovery alone cannot identify the visitor.
With cross-identification, this data is linked to Customer Engagement, where the visitor is identified, so the pseudonymized profile can be connected to a known person. Historical or in-store purchase data may also be transferred from Customer Engagement to Product Discovery and linked to the shared key. This expands the scope of data processing, because data that was pseudonymized in Product Discovery can now identify the person.
Read more
Go to Developer docs to read more about the technical side of this feature