Using your own FCM ID

Understanding How FCM Works

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.

  • An iOS, Android, or web (JavaScript) client app that receives messages
Click Here to get started with Firebase Cloud Messaging.

Configure your own FCM

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. Since the subscriptions are taken on a third party domain, by default the third-party FCM details are used.

    Did this help answer your question?


    Thanks for the feedback! 🙏🏽

    Help by drift