and will not impact ongoing push activity.
Effective Planning: How Batch Helps You Ahead of the June 2024 Migration Deadline
As mentioned earlier, if you do not migrate from legacy FCM APIs to FCM HTTP API v1 before the June 2024 deadline, you will no longer be able to send push notifications on Android.
Good news: Batch has already successfully completed this migration with several clients, proving the effectiveness of our methodology.
Here's how Batch Teams will help you meet the June 2024 deadline without interrupting your push notifications:
picture
For Batch customers who benefit from a dedicated Customer Success Manager: they will be actively supported in the process with frequent reminders and all necessary assistance.
For Batch customers who do not have a dedicated updated mmxxiv mobile phone data Customer Success Manager: automated monthly email reminders will be sent.
In both cases, orange banners are displayed on the Batch Dashboard to remind our customers to update their push settings, as follows:
picture
Our teams will carry out all necessary monitoring to follow the migration and, if necessary, adjust the process to the context of each client, well before the June 2024 deadline.
From April 2024New Android Push Settings: How to successfully complete the mandatory migration to FCM HTTP API v1 before June 2024
What's new
Jan 3, 2024 Written by
Pierre Tam-Anh Le Khac
Firebase has announced that the legacy FCM APIs will be retired in June 2024. From that date, Android Push messaging will no longer rely on the legacy FCM API , making migration to the new FCM HTTP v1 API a high priority.
This is a critical update for any mobile CRM marketer who sends push notifications to Android devices: failing to complete this migration will result in an invalid push configuration. In other words, it will be impossible for your app to send push notifications using the old credentials.