Share via

Dynamics Push Notifications Customer Insights

Rachel Blake 0 Reputation points
2025-12-19T07:15:10.4233333+00:00

Hi,

I'm trying to get push notifications (from Microsoft Dynamics) working as expected on Android when the app is in the background or quite state. Dynamics sends a data only payload for Android, which means I'm using the setBackgroundMessageHandler, to schedule a notification. This works by accident sometimes, and I believe is limited by the fact that Dynamics send a notification with a 'normal' priority, rather than the 'high' priority required for this solution to work. Can you tell me if there is any way to change the priority setting for Customer Insights - Journeys push notifications from Dynamics? Or whether there is another way we can appropriately handle the notifications when the app is in the background or quit state?

Microsoft 365 and Office | Development | Other

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Flora-T 11,775 Reputation points Microsoft External Staff Moderator
    2025-12-19T10:05:14.0033333+00:00

    Hi Rachel Blake

    Thank you for reaching out to the Microsoft Q&A forum and for sharing your experience with getting push notifications from Dynamics 365 Customer Insights - Journeys to work reliably on Android.

    On Android, data‑only FCM messages (the type commonly used when relying on setBackgroundMessageHandler) may be delayed or dropped when the app is in the background or in Doze mode unless the message is sent with high priority.

    For reference, here are the related articles:

    Please note that Microsoft Dynamics 365 is not officially supported on the Microsoft Q&A forum. The guidance provided here is limited to publicly available Microsoft documentation, and moderators do not have access to backend systems or engineering‑level tools to review Dynamics configurations.

    My apologies for redirecting you, but given these limitations, posting your scenario in the Microsoft Dynamics 365 Community Forum will ensure you receive faster and more accurate assistance from specialists.

    This issue involves Dynamics 365 Customer Insights - Journeys, Firebase message behavior, and how your application processes notifications, the Dynamics community will be best equipped to provide deeper, product‑focused guidance for this type of configuration.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
  2. Q&A Assist
    2025-12-19T07:15:21.1433333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To change the priority setting for push notifications in Customer Insights - Journeys, you can set the priority on individual notifications. However, the context provided does not specify a direct method to change the priority from 'normal' to 'high' for notifications sent by Dynamics.

    The priorities available for push notifications are:

    • High: Important notifications that must be delivered immediately, such as VoIP calls or critical alerts.
    • Medium: Notifications that are not urgent but should run in the background.
    • Low: Notifications that only make sense when the user is actively using the device.

    Since the priority is set on a per-notification basis, you may want to ensure that your application is configured to send high-priority notifications when necessary. For handling notifications when the app is in the background or quit state, you should implement the setBackgroundMessageHandler correctly to ensure that notifications are processed as intended.

    For more detailed guidance on handling notifications and their settings, you might want to refer to the documentation on push notifications setup and user mapping for push notifications in Customer Insights - Journeys.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.