Project - Migrate Braze users to native opt-in attributes

Context 

Why is this happening?

The marketingEmail and marketingPush attributes were created in the RBI platform a long time ago. In the meantime Braze created their own attributes to accomplish the same purpose. They recommend using these instead. Furthermore, this aligns with the project aims of the data plan optimisations which are in progress.

What's the impact?

At the moment, there is no impact. Our process to transition to these new attributes consists of supporting both the old and new attributes for a while, so that each market has time to take action without any side effects.

What are the next steps?

RBI will run a script that ensures the Braze native attributes are populated with the same values as marketingEmail and marketingPush custom attributes, respectively. This ensures that we do not lose any opted in settings for guests who have signed up before the new Braze attributes were available. This bulk update has already been completed for numerous markets.

Please see the respective pages below for Popeyes Spain and Burger King Portugal indicating the number of user accounts in Braze that will be updated:

What do we need to do?

Once you receive confirmation from Luke Fisher that the migration is completed, you will need to ensure that references to marketingEmail and marketingPush are replaced with Braze native attributes. This is necessary in:

• Any Braze campaign filters (also past campaigns)

• Any Braze segment created to target opt-in users  

• Any integrations that might rely on the marketingEmail and marketingPush attributes

Once the above steps have been taken, we will be able to remove the marketingEmail and marketingPush custom attributes to avoid ambiguity.