Push_subscribe sync

Testing of the Push has not been done so far. BK ES APK is existing but the Firebase configuration will be pending until the swap from the previous vendor. And firebase is essential to be linked with Braze BK ES workspace to send push.

SCENARIO: When a user is replicated receives push notification.

This scenario is not possible to be developed due to the missing “Device token” from the replicated user: the user doesn’t have the application and, by consequence, he can’t receive any notification.

We noted that push_subscribe attribute is not synchronized by Braze as happens with emails (email_subscribe attribute). And the reason for that, is that Braze sees each user (even users that has a different email) as an user associated with a different device. Therefore the sending of push respects this logic.