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.
...
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 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
...
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
...