Opt-in whitelabel

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

  • marketingPush=true (dynamodb and mparticle)

  • marketingEmail=true(dynamodb and mparticle)

  • email_subscribe=opted_in(dynamodb and mparticle)

  • push_subscribe=opted_in(dynamodb and mparticle)

opt-in in database

aws-rbi-dev-plk

aws-rbi-dev-bk

Does a customer who sign-up in PLK ES get registered in BK ES 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:

  • 

opt-in in mParticle

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

    • A test was done in PLK ES DEV pointing to BK PT DEV

  • 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

opt-in in Braze (used by mparticle/braze libs)

• 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

• Per brand, country and environment:

  • 

• Target audience based on brand, country and environment:

  • 

Connection Mapping PLK ES DEV

Connection Mapping BK ES

References:

/wiki/spaces/EGMT/pages/4151410932

Feature - Push notifications

/wiki/spaces/EGMT/pages/4016373809

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