Firebase Cloud Messaging (FCM) is a cross-platform messaging solution that lets you reliably deliver messages at no cost.
An FCM implementation includes two main components for sending and receiving:
- A trusted environment such as Cloud Functions for Firebase or an app server on which to build,
target, and send messages.
Click Here to get started with Firebase Cloud Messaging.
By default, the FCM used for all our customers is iZooto’s default ID.
Updating FCM Details
In order to update your FCM details, iZooto’s default FCM project number and API key needs to be replaced. This can be done from Settings >> General Settings >> Chrome Project Key
After clicking on Submit request for updation, you'll be asked to enter your FCM details - Sender ID and Server Key. After you submit the details, the Sender ID and Server Key would be verified by iZooto post which it would be updated for your website and you would be able to build your subscriber base on it.
Updating FCM post subscriber acquisition
We recommend that you update your FCM details right after integrating the iZooto pixel. This will ensure that from day 0 (or atleast day 1), you build your subscriber base on your own FCM. Updating the FCM details post subscriber acquisition would lead to:
- Losing the earlier subscribers mapped to iZooto’s FCM details
- Maintaining two sets of subscribers and pushing notifications to them separately.
- You don't need to update the FCM details if you have an HTTP website because the consents are taken on the third party domain, therefore, by default third-party FCM details are used.
Q1. What is FCM and how can I use it?
Ans. FCM stands for Firebase Cloud Messaging, it is a cross-platform messaging service. You can start using FCM by signing up on the FCM console using your Gmail ID. Here is a Blog that talks about FCM in great detail.
Q2. How to migrate to a different push notification service?
Ans. Once you have finalized the new service provider, here is what you need to do –
- Check the file name of the old service worker
- Rename the service worker file of the new provider
- Update the service worker js
Please go through this Blog that brilliantly covers and explains all the possible scenarios that occur during the migration process.