IMPORTANT UPDATE: Android apps integrated with Marketing Cloud Engagement MobilePush must be updated by June 2024.
What’s the change?
To remain compliant with Google Firebase Cloud Messaging changes, we’ve updated the authentication pattern for Android apps integrated with MobilePush.
What's the impact?
To continue to send push notifications to Android devices from MobilePush, customers must adopt the new authentication pattern by June 1, 2024.
What action do I take?
In order to continue sending push notifications to Android devices through MobilePush, upload the service account JSON file for your active Android apps by June 2024. You can take this action within the MobilePush Administration tab.
What happens if I take no action?
You won’t be able to send push notifications from MobilePush to Android devices after June 2024
How is Salesforce communicating this change?
Salesforce is scheduled to deliver to admins a Product and Service notification, which lists the impacted MID, Android App Name and ID.
Hey @Vyara Lambrinova — just seeing your question now (and it's a great question)! The JSON payload restructuring work was something that we (the MCE Product & Engineering) team had to do internally because we're connecting directly with the Google APIs. So no additional action required by Marketing Cloud customers on that front. The only additional guidance I'd provide is to make sure your push notifications do not include any custom keys that leverage the following Google reserved keywords:
alert
_m
sound
title
subtitle
_mediaUrl
_mediaAlt
_r
_sid
content-available
category
_od
_x
_mt
