Firebase Cloud Messaging (FCM) is the new version of GCM. It inherits the reliable and scalable GCM infrastructure, plus new features! Hence, we have updated the guide to show steps for getting FCM Key
Guide to Create Firebase Cloud Messaging Sender ID and Server API Key
We are a believer in Transparency, at PushEngage. We wrote an article about how to achieve full vendor portability with Web Push Notifications here. For Push Notification to work, it needs the GCM key.
In order for you to export your subscribers successfully and to use them through another API, you will need to configure PushEngage (or for that matter any provider) with your own Firebase Cloud Messaging Sender Id. We wrote about this in our FAQ as well. Google/Firebase Cloud Messaging is a service that enables developers to send push notification messages between the client browser and serve them.
Note: This is a critical setting, so please make sure you make this in an email account that you or your company owns.
Steps to Create a Firebase project and FCM sender ID
Guide updated:07-September-2017 [ We will try to keep this guide current]. Currently, we using Wapid Key.
- In the Firebase console, at https://console.firebase.google.com/ select Create New Project. Supply a project name and click Create Project.
2. Select the gear icon next to your project name at top left, and select Project Settings.
3. Select the Cloud Messaging tab. You can find your sender ID in this page.
4. Copy these value in PushEngage Dashboard under Settings -> GCM/FCM Settings, and go live.
Here is the video to learn how to create and configure Firebase Cloud Messaging Sender ID and Server API Key:
If you are a HTTPS website, after updating the FCM key, you would need to download your manifest.json file again from Settings> Installation Settings > Step 2, and save it in the root folder.
For HTTP sites there is no extra step. However, do read our full portability guide for HTTP sites here.
That's it you are done with the FCM configuration. This is a crucial setting to make sure to Verify the setting in PushEngage.
Using your own FCM key is very important when you want to migrate push notification subscribers from one push notification platform to other.
If you have questions, write to us at care@pushengage.com or check the support section for PushEngage or through Contact Us.
Related Posts:
![Why should you use Web Push Notifications? [Infographic]](https://mk0peblog3xrj4fi9v3j.kinstacdn.com/wp-content/uploads/2018/03/Why-should-you-use-Web-Push-Notifications-150x150.jpg "Why should you use Web Push Notifications? [Infographic]")
[…] & you should create your GCM account. If you are not so tech savvy, you can ignore it. However using this documentation will make the process […]
[…] you are not so tech savvy, you can ignore it. However, using this documentation will make the process […]
[…] you are not so tech savvy, you can ignore it. However, using this documentation will make the process […]
Hello;
You guys should update this guide, that link goes to firebase on Google how do i get the details?
Good point. We have updated the guide with how to setup Firebase Cloud Messaging (FCM) Sender ID & Server Key
So i need to replace my manifest.json file?
Yes, after changing the FCM key, please update and save the manifest.json file.
To be honest you this article gives a good guide how to use APIs but being a nontech guy I find it a little bit tough! Do you have any video tutorials?
-Logical Nerds
The wordpress plugin still looks for a GCM key and wont accept any FCM key?
Please enter the FCM key from our dashboard.
you are not so tech savvy, you can ignore it. However, using this documentation will make the process
[…] you are not so tech savvy, you can ignore it. However, using this documentation will make the process […]
Amazing post, thanks for sharing this article, I am truly motivated by your blogging,
thanks again.
I have updated everything on my website. Do I need to upload manifest file again?
Yes after updating FCM, do upload the manifest again.