Summary / TL:DR: In the Blueshift Data Refactor the data model will be email centric meaning we will no longer rely on the combination of the customer number and email id which make up the customer id in the legacy data model of Blueshift. The customer id is now a unique identifier that is generated in snowflake.
...
Custom Events Sent to Blueshift
In legacy Blueshift you may be sending events that include the retailer_customer_id or customer_id in the event payload so that event gets recorded to the correct profile.
The refactored instance of Blueshift will be email centric meaning the email address will be the main identifier for profile matching. The customer id will in the new instance is made up of the profile key which will be included by default as a URL parameter. This profile key (pk) is comprised of the affiliate id and email address which is MD5 hashed. The profile key can be passed back as the customer_id to tie an event back to a user profile with out needing to decode the vid2 value.
...
| Tip |
|---|
Wrap up |
| Info |
|---|
Still need help? We know this can be frustrating. To get further help open a Jira ticket. |
...
| Note |
|---|
Cannot find the article you’re looking for? Suggest a new article here! |