Difference between original and replicate data on Braze

Owned by Goncalves, Felipe
Last updated: Feb 02, 2024
4 min read

 

 

SOLUTION

The suggested solution is to change the status for the “replicated” users as “SUBSCRIBED”, while we maintain the real users that accepted the opt-in as “OPTED IN”.

It’s important to analyze the migrated data from Salesforce in which state the user is mapped. In case of “SUBSCRIBED”, we suggest to move into a deeper analysis of those profiles that could be mapped by the granularity of the data available (ex: loyaltyID)

ANALYSIS

Register the user by first time in PLK and replicate to BK

I created the user felipepg+braze45@ciandt.com on PLK STG

The first difference is that original there are many more information, and the name it is the same that the wrote in the field name, in the replicate it gets the first part of e-mail user.

Pasted Graphic 15-20240131-111147.png
Pasted Graphic 16-20240131-111249.png

In the same page, there are some differences in the inferior part.

On the second tab, there are more differences

On the third tab, there are more differences:

Register the user on BK after has the replication

Now, how it after create with the same email a register on BK

Register original of BK

In this case, both items stay with the same name in top of page, and some other attributes.

 

In the second tab it has the same data, maybe the item get the information of old register.

Analyze the first items of first register again

Now we will analyze how stay the old register, made the first register on PLK and with your replicate on BK

Don’t have difference

Second Tab:

Code

A suggest is to change the code of this file intl-user-service/scripts/utils/utils-users.ts in the getCommPrefsValue function.

This function captures the status of the email or push (unsubscribe, subscribed or opted in).

A possible solution is when the record is a replica and the email is equal to "opted in" we change it to “subscribed”, and to know if the record is a replica we can validate the "loyaltId" record when it is a replica this value is null.
So if the “loyaltId” is null and the email status is "opted in" we change its status to "subscribed"