Alias activities can be used to handle the case when a customer updates their global identifier.
- user may update their email to be their work instead of personal
- user entered the wrong email in a website form
To solve this problem we use an aliasing activity.
An aliasing activity will update a customer's global identifier to a new global identifier.
You need to create an activity transformation where the:
anonymous_customer_idis the old customer value
customeris the new customer value
Then under processing config, advanced configuration, check Process as an Aliasing Activity
SELECT u.id as activity_id , u.updated_at as ts , u.email as customer , case when a.customer is not NULL then 'customer' END as source , a.customer as source_id , 'updated_email' as activity , NULL as feature_1 , NULL as feature_2 , NULL as feature_3 , NULL as revenue_impact , NULL as link from db.users u left dw.activity_stream a on (a.activity = 'updated_email' and a.activity_repeated_at is NULL) where a.customer is null or a.customer <> u.email
Our data team is here to help! Here are a couple ways to get in touch...
💬 Chat us from within Narrator
💌 Email us at [email protected]