...
opt-in in database
| Code Block |
|---|
(...)
"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"
}
}
}
]
} |
...
Open question: 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 or should ? (reusing mono-table or new table)
Should Braze look into a new indicator? Fisher, Luke
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 / Braze / Amplitude
to check:
connection with another mParticle
References:
...