Architecture AS-IS

The following architecture uses PLK ES DEV and BK ES DEV as reference, but it should be interpreted for whitelabel-app independently of market and environment setup.

Mapping of email and push attributes in whitelabel-app

• If customer sets the mkt comms checkbox, the following should be set for all brands for the app country:

  • marketingEmail=true ( true/false) → aligned with Sanity

  • email_subscribe=opted_in ( unsubscribed / subscribed / opted_in ) → aligned with Braze

  • marketingPush=true ( true/false) → aligned with Sanity

  • push_subscribe=opted_in ( unsubscribed / subscribed / opted_in ) → aligned with Braze

Mapping of email and push attributes in database (dynamodb)

• aws-rbi-dev-plk

• aws-rbi-dev-bk

Does a customer who sign-up in PLK ES DEV get registered in BK ES DEV (dynamodb) too?

• No.

What about other brands mParticle/Braze?

• Yes.

Mapping of email and push attributes in mParticle

https://app.eu1.mparticle.com/

• to check connection with another mParticle

  • https://dev-plk-es-whitelabel-cms.rbi.tools/desk/ctgConfigs;frontEndConfiguration

  • 

    Findings: Just changing this value is enough to point to another mParticle instance and propagate mParticle info → Braze.

    • Tests done in PLK ES DEV pointing to BK PT DEV / BK ES DEV

    • Way-forward option 1: Work with multiple instances:

      • Iberia: PLK ES and BK ES

      • currently mParticle init is just for one instance

    • Way-forward option 2: Propagate events from PLK ES mparticle instance to BK ES Braze (filtering events)

      • No impact on WL. Only mParticle configuration.

  • The above mParticle config is related to:

    • mParticle PLK ES DEV WEB.

  • In sanity, there is no config related to:

    • mParticle PLK ES DEV Android.

    • mParticle PLK ES DEV IOS.

  • Check if Android and IOS input config make sense

    • Configuration is defined in capacitor

Mapping of email and push attributes in Braze

• to check connection with another braze .

  • maybe it’s not being used since initialization doesn’t require an explicit API key ( reference ). Most probably it’s loading based on mParticle UI config.

  • 

Braze configuration

https://dashboard-02.braze.eu/

• Per brand, country and environment:

• Target audience based on brand, country and environment:

In Braze, it’s possible to create campaigns targetting the same customer (say raphaelg@ciandt.com) , but with different users in the platform:

However, this is not what we expect to have. Example of Expectation : Have a PLK ES customer userId in BK ES Braze.

Connection Mapping PLK ES DEV

Connection Mapping BK ES

Solution Proposals

Option 1 - Changing WL to forward Sign up complete/accepted agreement (mkt comms = true) events to another mParticle instance Brand and then to the corresponding Braze Brand

Option 2 - Configuring mParticle instances to forward filtered Sign up complete/accepted agreement (mkt comms = true) events to another braze brand

Attention: There may be limitation of just 1 Braze instance per enviroment as discussed here: https://rbidigital.slack.com/archives/C04TQFZ4A73/p1696543169788919

Option 3: Sync events between Brazes

Braze PLK ES and Braze BK ES

• 

  Checking feasibility with New Markets Setup team :

  • “As far as I'm lead to believe, each market and each environment has their own braze workspace.”

Option 4: Propagate events through backend

export CROSS_BRAND_MPARTICLE_SQS_QUEUE_URLS to have other brands mParticle queues in intl-user-service.

Read it in intl-packages when logging the crm event into the queue(s).

Sign up to a brand that uses the RBI app

With opt-in consent

• Condition:

  • Sign-up complete event

  • marketing comms WL mkt comms flags are set as opted_in

Terms and conditions

Opt-in during acceptance

Condition:

• T&C update agreement modal

• marketing comms WL mkt comms flags are set as opted_in

5.2. Opt-out during acceptance

N/A scenario - T&C doesn’t provide the possibility for a guest opt-out, if he/she already opted-in.

All other scenarios described in Cross-Brand Opt-In are not applicable

References:

/wiki/spaces/EGMT/pages/4151410932

Feature - Push notifications

/wiki/spaces/EGMT/pages/4016373809

https://docs.mparticle.com/integrations/braze/event/#user-attributes