Provisioning ensures that users receive push messages from your app. The first step in provisioning is to retrieve the Legacy server key and Sender ID for your app so that you can put this information into Marketing Cloud.

As of September 2016, Google changed where you go to retrieve the Legacy server key and Sender ID. Now, you retrieve them in Firebase. Follow the instructions for the scenario that applies to your situation.

Existing Project – Before September 2016

Note: If you already enabled Firebase for a reason other than provisioning an app, this deactivates the existing GCM key for your app. You need to retrieve a new server key and sender ID on Firebase and re-register your app in Marketing Cloud.

  1. Log into the Google API Developers Console.

  2. Select your project.

  3. Go to Library.

  4. Select Google Cloud Messaging. Then you are redirected to Firebase.

  5. Click Go to Console.

  6. Click through the get started information.

  7. Navigate to Cloud Messaging under Settings.

  8. Make note of the Legacy server key and Sender ID.

  9. Use the Legacy server key and Sender ID to register your app in Marketing Cloud.

Existing Project – After September 2016

  1. Log in to Firebase.

  2. Select your project.

  3. Navigate to Cloud Messaging under Settings.

  4. Make note of the Legacy server key and Sender ID.

  5. Use the Legacy server key and Sender ID to register your app in Marketing Cloud.

New Project

  1. Create a new project for your app in Firebase

  2. Navigate to Cloud Messaging under Settings.

  3. Make note of the Legacy server key and Sender ID.

  4. Use the Legacy server key and Sender ID to register your app in Marketing Cloud.


Next steps to register your app in Marketing Cloud: