...
...
...
...
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.
| Lucidchart | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Lucidchart | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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:
marketingPushmarketingEmail=true ( dynamodb and mparticle)marketingEmail=true(dynamodb and mparticle)true/false) → aligned with Sanity
email_subscribe=opted_in ( unsubscribed / subscribed / opted_in (dynamodb and mparticle)) → aligned with Braze
marketingPush=true ( true/false) → aligned with Sanity
push_subscribe=opted_in ( dynamodb and mparticle)
...
unsubscribed / subscribed / opted_in ) → aligned with Braze
Mapping of email and push attributes in database (dynamodb)
...
Does a customer who sign-up in PLK ES DEV get registered in BK ES DEV (dynamodb) too?
...
No
If not, should whitelabel register it in the database of another brand? (reusing mono-table or new table)
Not necessarily
What about mParticle → Braze?
Most probably yes.
Should Braze look into a new indicator?
No. To check if app can point to another brand mParticle as:
.
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
...
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 .
6dbb415a-80e8-4f47-b1d4-d5442c388f43
Can we have multiple Braze instances?
...
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
Platform | mParticle Key (DEV) - (eu1-df5f1ea3d94b4644aac0895306f38db0) | Braze API KEY (PLK_ES - Development ) |
|---|---|---|
web | ****************************5780 | d4c670dc-2ffb-40bb-a892-14f58e3f5780 |
Android | ****************************3c67 | e61cea8a-1678-41ed-b240-a8a0610a3c67 |
IOS | ****************************1ee5 | 7bc7c394-19c0-4612-bb60-dbd951c01ee5 |
Connection Mapping BK ES
Platform | mParticle Key (DEV) (eu1-0c13f335900287438fd4103e7b18d850) | Braze API KEY (PLKBK_ES - Development ) |
|---|---|---|
web ? | ***************************278a | 3e050cbf-2878-46ed-98c1-3365ea49278a |
Android? | ****************************0fb6 | 3194745e-0038-449f-910a-170231fa0fb6 |
IOS? | ****************************625e | 5a0dd8b1-65a2-452a-9722-d8126f47625e |
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
...
Read it in intl-packages when logging the crm event into the queue(s).
Discussion: https://rbidigital.slack.com/archives/C04FJ3LUNP4/p1697673525644479
Sign up to a brand that uses the RBI app
With opt-in consent
Steps | Expected results |
|---|---|
Guest signs up with the PLK ES app and accepts marketing communications from the sign in page |
|
Condition:
Sign-up complete event
marketing comms WL mkt comms flags are set as opted_in
Terms and conditions
Opt-in during acceptance
Steps | Expected results |
|---|---|
Guest signs up with the PLK ES app and accepts marketing communications from the sign in page | Email and Push subscription status in Braze set to “Opted In” for PLK ES, BK ES and TH ES |
Guest receives a marketing email from BK ES and clicks the unsubscribe link | Email and pushsubscription status in Braze set to “Opted In” for PLK ES and TH ES, but “Unsubscribed” for BK ES |
Guest receives a marketing email from TH ES and clicks the unsubscribe link | Email and pushsubscription status in Braze set to “Opted In” for PLK ES and “Unsubscribed” for BK ES and TH ES |
During a second login to the PLK ES app, guest is presented with updated T&C for acceptance. Guest accepts marketing communications | Email and Push subscription status in Braze set to “Opted In” for PLK ES, BK ES and TH ES |
Condition:
T&C update agreement modal
marketing comms WL mkt comms flags are set as opted_in
5.2. Opt-out during acceptance
Steps | Expected results |
|---|---|
Guest signs up with the PLK ES app and accepts marketing communications from the sign in page | Email and Push subscription status in Braze set to “Opted In” for PLK ES, BK ES and TH ES |
During a second login to the PLK ES app, guest is presented with updated T&C for acceptance. Guest does not accept marketing communications | Email and Push subscription status in Braze set to “Unsubscribed” for PLK ES, BK ES and TH ES |
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
/wiki/spaces/EGMT/pages/4016373809
...