Hi Masters,
We've configured push notifications in an Android app. We can send notifications using both the Assurance push test and the AJO Campaign. My question is related to the denylisted field in the (xdm:) pushNotificationDetails.
As per [1], "The token can be denylisted for various reasons, like the user has uninstalled the app or the user has disabled push messaging for the app."
However, we have conducted multiple tests by disabling app notifications from the Android settings, but the denylisted field in the AEP profile (pushNotificationDetails.0.denylisted) for the user is always set to false. My question is: when is the denylisted field updated? Does the app need to call any API method to update this field?
Furthermore, in [2], it is stated that denylisted "Indicates whether the push token is blocked by the push provider," which seems like a different definition compared to [1].
So, is it best practice to use the denylisted field to check if a profile (user) has allowed push notifications in their app? This question also relates to user consent/preferences, which I find somewhat confusing.
Any tips would be appreciated! Thanks!
[1] https://experienceleague.adobe.com/en/docs/experience-platform/assurance/view/push-debug-view#profil...
[2] https://github.com/adobe/xdm/blob/master/docs/reference/fieldgroups/profile/profile-push-notificatio...
Kind regards,
