Architecture AS-IS
The following architecture uses PLK ES DEV and BK ES DEV as example, but it should be interpreted for whitelabel-app independently of market and environment setup.
...
| Lucidchart | |||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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)
...
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
...
Platform | mParticle Key (DEV) (eu1-0c13f335900287438fd4103e7b18d850) | Braze API KEY (BK_ES - Development ) |
|---|---|---|
web | ***************************278a | 3e050cbf-2878-46ed-98c1-3365ea49278a |
Android | ****************************0fb6 | 3194745e-0038-449f-910a-170231fa0fb6 |
IOS | ****************************625e | 5a0dd8b1-65a2-452a-9722-d8126f47625e |
Solution Proposal*
*texts blue = impacts, text in red = no impact
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
...
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: marketing comms WL flags are true ( email and push attributes set to true)
Option 1: WL (PLK ES) needs to send the sign-up complete event (with mkt comms flags = true )for both mParticle instances PLK ES and BK ES. To do that, Sanity will need to have not only one field to store the mParticle instance, but a list. Then WL will fetch this list to propagate this event.
Option 2: PLK ES mParticle instance will also forward PLK ES sign-up complete event (with mkt comms flags = true ) events to BK ES
It will feed both Brazes (PLK ES and BK ES) with the same event data → PLK ES data (userId, …).
Without opt-in consent
Steps | Expected results |
|---|---|
Guest signs up with the PLK ES app and does not accept marketing communications from the sign in page |
|
condition: marketing comms=false ( email and push attributes set to false)
There is no need to propagate this event to BK ES mParticle / Braze.
Sign-up to TH
Not applicable
Unsubscribe
From an email
| Note |
|---|
Need to look into how to disable push from the email link. |
Steps | Expected results |
|---|---|
Guest receives a marketing email from PLK ES and clicks the unsubscribe link |
|
In principle, no impact to notify other brand Braze, since the link is specific to unsubscribe one brand only.
From the RBI app
Steps | Expected results |
|---|---|
Guest opens the communication preferences page on the PLK ES app and unchecks the “Email marketing communications & Push“ setting:  |
|
In principle, no impact to notify other brand Braze, since the app update comm. preferences update is specific to unsubscribe one brand only.
From the Admin Tool
Steps | Expected results |
|---|---|
Support staff unsubscribes a guest from email and push communications on the PLK ES Admin Tool |
|
Support staff unsubscribes a guest from email or push notifications separately on the PLK ES Admin Tool | Not possible, since the PLK ES app does now show opt in status separately for email and push. |
In principle, no impact
From Salesforce Service Cloud
| Note |
|---|
Item under discussion. As it stands, this is outside of RBI scope. |
Steps | Expected results |
|---|---|
Support staff unsubscribes a guest from email and push communications on Salesforce Service Cloud | Email and Push subscription status set to “Unsubscribed” on Braze for TH ES only and “Opted In” for all other brands |
In principle, no impact
Subscribe
Steps | Expected results |
|---|---|
Guest opens the communication preferences page on the PLK ES app and checks the “Email marketing communications & Push“ setting:  |
|
In principle, no impact
From the Admin Tool
Steps | Expected results |
|---|---|
Support staff subscribes a guest to receive email and push communications on the PLK ES Admin Tool |
|
Support staff subscribes a guest to receive email communications only on the PLK ES Admin Tool | Not possible, since the PLK ES app does now show opt in status separately for email and push. |
In principle, no impact
From Salesforce Service Cloud
| Note |
|---|
Item under discussion. As it stands, this is outside of RBI scope. |
Steps | Expected results |
|---|---|
Support staff subscribes a guest from email and push communications on Salesforce Service Cloud |
|
In principle, no impact
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 |
Impact in “Accepted updated agreement” event flow.
It should propagate the accepted updated agreement event with the mkt comms flags as true for all configured Brazes.
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 |
Impact in “Accepted updated agreement” event flow.
...
N/A scenario - T&C doesn’t provide the possibility for a guest opt-out, if he/she already opted-in.
Edge Cases
Opt-out during sign-up in another brand
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 |
The same guest signs up with the BK ES app and does not accept marketing communications from the sign in page | Email and Push subscription status in Braze set to “Unsubscribed” for PLK ES, BK ES and TH ES |
In principle, no impact. It should be covered with the sign-up flow. Tests are crucial here.
Opt-in during sign-up in another brand
Steps | Expected results |
|---|---|
Guest signs up with the PLK ES app and does not accept marketing communications from the sign in page | Email and Push subscription status in Braze set to “Unsubscribed” for PLK ES, BK ES and TH ES |
The same guest signs up with the BK 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 |
In principle, no impact. It should be covered with the sign-up flow. Tests are crucial here.
Re-subscribe
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 |
The same guest signs up with the BK 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 |
In principle, no impact. It should be covered with the sign-up flow. Tests are crucial here.
References:
/wiki/spaces/EGMT/pages/4151410932
...