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
(...) "communicationPreferences": { "L": [ { "M": { "id": { "S": "loyalty" }, "value": { "S": "true" } } }, { "M": { "id": { "S": "orderStatus" }, "value": { "S": "true" } } }, { "M": { "id": { "S": "marketingEmail" }, "value": { "S": "true" } } }, { "M": { "id": { "S": "email_subscribe" }, "value": { "S": "opted_in" } } }, { "M": { "id": { "S": "rewardsEmail" }, "value": { "S": "true" } } }, { "M": { "id": { "S": "Email Opt In" }, "value": { "S": "true" } } }, { "M": { "id": { "S": "marketingPush" }, "value": { "S": "true" } } }, { "M": { "id": { "S": "push_subscribe" }, "value": { "S": "opted_in" } } }, { "M": { "id": { "S": "rewardsPush" }, "value": { "S": "true" } } } ] }
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)
Should Braze look into a new indicator?
If the customer already exists in BK ES too, should we just update the BK ES attributes ?
to check:
connection with another database
connection with another cognito user pool
opt-in in mParticle
to check connection with another mParticle
opt-in in Braze
to check connection with another braze .
Do we have multiple Braze instances?
References:
/wiki/spaces/EGMT/pages/4151410932
/wiki/spaces/EGMT/pages/4016373809
https://docs.mparticle.com/integrations/braze/event/#user-attributes
Add Comment