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. In legacy Blueshift the customer_id is made up of a combination of the advantage customer number and email id. In the initial phase of Blueshift refactor onboarding you will want to remove this attribute from your custom events.

The refactored instance of Blueshift will be email centric meaning there will always be a one to one relationship with emails and profiles in Blueshift. The customer id in the your refactored 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.

You can read more about the vid2 parameter here.

MW Plugin Events

In order to enable the option to stop sending the retailer_customer_id in events that come from the MW plugin your website must be on version 1.28.12 or greater of the Middleware Auth plugin. Once you are on this version, to remove the retailer customer ID from the blueshift events you need to check the "Disable Email ID" option in the admin (Middleware 2 -> Integrations -> Blueshift Configuration):

Open