---
schema_version: "1"
id: 63376c8b38ad1f65665c72670508fc6dd543a8e0f8b2f6d0697c28a5ab8991ca
title: Complete Mobile Push Setup
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_pers_mobile_campaign_push_setup.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_pers_mobile_campaign_push_setup.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e9484dcdf5c7330edcf65fef788681a0538d9f6fb462953f77014c3c64114641
description: Before you publish a Mobile Push campaign, you must generate and upload a certificate for Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM). If you enter credentials for both APNs and FCM, you must pick one when you add the app to a Mobile Push campaign. To prevent duplicate notifications, Personalization only sends to one platform.
products:
  - Marketing
  - Salesforce Personalization
release: "264"
---
# Complete Mobile Push Setup

Before you publish a Mobile Push campaign, you must generate and upload a certificate for Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM). If you enter credentials for both APNs and FCM, you must pick one when you add the app to a Mobile Push campaign. To prevent duplicate notifications, Personalization only sends to one platform.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Premium Edition</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d18223e54">Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d18223e54 ">To create and upload APNs and Firebase credentials for a mobile
              app:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d18223e54 ">A role with Administrator permissions</td>

          </tr>
        </tbody>
      </table>

1. Complete APNs and Firebase configuration before uploading APNs and Firebase credentials in the push notification setup.
2. In the **Channels & Campaigns** section of the main navigation, select **Mobile**.
3. In the **Mobile App Setup** section, select your existing Personalization-enabled mobile app.
4. Click **Mobile Push Setup**.
5. Enter or upload the credentials.
    - For Android/iOS apps using FCM, upload your private key JSON file to the FCM field. For more information, see [Push Notifications (Android)](https://developer.salesforce.com/docs/marketing/personalization/references/personalization-android-sdk/push-notifications.html).
        
        For information on generating a private key file in Firebase, see [Provide credentials manually](https://firebase.google.com/docs/cloud-messaging/migrate-v1#provide-credentials-manually) in the developer documentation for Firebase Cloud Messaging.
        
        ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_personalization-264-0-0-production-enus/16bf1f60-f44c-4260-a56e-f052cfe515a3/images/icon_note.png)
        
        Note The default service account is assigned a role that provides more access than necessary. To limit access and enhance security, we recommend creating a service account with only the [Firebase Cloud Messaging API Admin](https://gcp.permissions.cloud/predefinedroles/firebasecloudmessaging.admin) role.
        
        ![image showing the place to upload the private key for Firebase Cloud Messaging](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_personalization-264-0-0-production-enus/16bf1f60-f44c-4260-a56e-f052cfe515a3/mc_personalization/images/mc_pers_mobile_push_setup_fcm.png)
    - For iOS apps using APNs, upload the .p12 file for each sandbox or production certificate. For more information, see [Push Notifications (iOS)](https://developer.salesforce.com/docs/marketing/personalization/references/personalization-ios-sdk/push-notifications.html).
        
        ![image showing the place to upload production and sandbox certificate files for APNs](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_personalization-264-0-0-production-enus/16bf1f60-f44c-4260-a56e-f052cfe515a3/mc_personalization/images/mc_pers_mobile_push_setup_ios_apns.png)
6. For iOS apps, if you've entered credentials for both APNs and GCM, choose the platform under **Platform Selection** to which notifications will be exclusively sent.
    
    ![image showing the platform selection option](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_personalization-264-0-0-production-enus/16bf1f60-f44c-4260-a56e-f052cfe515a3/mc_personalization/images/mc_pers_mobile_push_setup_select_platform.png)
7. Click **Save**.