Logo Help Portal
  • Getting Started

    Introduction

    • Onboarding overview
    • Project Initiation
    • Email compliance
    • Account Administration

    Data

    • Data exchange
    • Data onboarding
    • Web data collection

    Channels

    • Email onboarding
    • Smart Insight
    • Predict
  • Training
    • Online Self Learning
    • Onboarding Videos
    • Instructor Led Training
    • Webinars
    • Seminars
  • User Guides

    Strategy

    • Personalization
    • Automation
    • Data Monitoring

    Channels

    • Email
    • Mobile Apps
    • Web
    • Ads

    Add-ons

    • Smart Insight
    • Predict
    • Incentive Recommendation
    • AIM
  • News & Support

    News

    • What’s New in the Emarsys Platform
    • Pilot features
    • Articles on Data Protection and GDPR
    • Release notes - archive

    Support

    • Help and Support at Emarsys
    • Managing your user profile
  • |
  • Developers
  • System Status
Need help? Submit a request
English Deutsch Español Français Русский Türkçe 简体中文
Sign in
  • Documentation_-Execution_- Mobile Apps
  • Mobile Engage
  • 0 Documentation_-Execution_- Mobile Apps Mobile Engage

In this section:

  • Mobile Engage - Overview
  • The Mobile Engage Data Flow Model
  • The Mobile Engage SDK
  • Mobile Engage Onboarding
  • Importing Previous Push Audiences to Mobile Engage
  • Mobile Engage End-User Guide
  • Mobile Engage - Advanced Features
  • Creating a Trackable Deep Link for Mobile in Email
  • Obtaining Certifications and Tokens for Sending Push Messages
  • Mobile Engage Glossary
  • See more

in Emarsys42

    Expand all

    Obtaining Certifications and Tokens for Sending Push Messages

    Updated: January 12, 2018 08:48

    In order to be able to send push messages to your app, you need to have certifications from Apple Push Notification service (APNs) and/or Google's Firebase Cloud Messaging (FCM).

    Contents:

    • Obtaining a certificate for Apple Push Notification Service
    • Obtaining Firebase Cloud Messaging credentials

    Obtaining a certificate for Apple Push Notification Service

    Step 1: Select the type of certificate

    Log in to your developer account at https://developer.apple.com, and navigate to Add iOS Certificate. In the window displayed, select Apple Push Notification service SSL (Sandbox & Production) as the type of certificate.

    Step 2: Add the App ID

    Select the App ID you would like to use the certificate for.

    Click Continue.

    Step 3: Create and upload the Certificate Signing request

    In order to generate the certificate manually, you will need a Certificate Signing Request (CSR) file from your Mac. In the window displayed, click Continue to create a CSR file using Keychain Access.

    In Keychain Access, select Certificate Assistant and then Request a Certificate From a Certificate Authority.

    When your certificate request has been created on your hard disk, click Done to move to the next step.

    Add the certificate information for the Certificate Authority (CA). Add the User Email Address, the Common Name and the CA Email Address.

    As the Request is: option is Saved to disk, by clicking Continue, you have to locate and select the CSR file on your disk.

    By clicking Save, the CSR file is created. With this, a public and private key pair is automatically generated, with the private key stored on your computer and the requested certificate being the public half of the key pair. The private key can be found in the login Keychain and can be viewed in the Keychain Access under "Keys".  

    To upload the CSR file, locate it on your hard drive and click Continue.

    Step 4: Download and install the certificate

    When your certificate is ready, download it on your hard drive.

    Make sure to create a backup copy of the certificate at a secure location.

    For more information, read the relevant chapters in the App Distribution Guide.

    To install the certificate in your Keychain, double click on the downloaded file and click Add.

    Step 5: Export the certificate as a .p12 file

    The .p12 file is needed so that Mobile Engage can use the certificate to send push messages to your app. To export the certificate in a .p12 file, right click on the certificate and select Export.  

    You should export a .p12 file for Sandbox and another for Production.

    We recommend password protection of the .p12 file, too, which is also available as an option at the export.

    Obtaining Firebase Cloud Messaging credentials

    Step 1: Log in

    Log in to your developer account at the Firebase Console.

    Step 2: Create project

    If you already have a project, proceed to Step 3. If you do not have a project, click Add project. 

    Fill in the fields with the appropriate information, and then click Create Project.

    Step 3: Find credentials

    In the Project Settings, locate the Cloud Messaging tab.

    Copy the Server key token to your clipboard.

    Step 4: Add the tokens to your app in Mobile Engage

    In Mobile Engage, locate the Apps tab and click Edit by the required app.

    In the Platforms section, click Edit again to enter the Android Platform settings.

    In the window displayed, add the Server key to the Google Cloud Messaging API key field and click Confirm.

    Was this article helpful?

    Have more questions? Submit a request
    Return to top

    You may also be interested in:

    Related articles

    • The Mobile Engage SDK
    • Mobile Engage - Advanced Features
    • Mobile Engage End-User Guide
    • Creating a Trackable Deep Link for Mobile in Email
    • Mobile Engage - Android Oreo Notification Channels
    Copyright © 2019 Emarsys eMarketing Systems. All rights reserved
    Legal Notice Privacy Policy Master Services Agreement Anti-spam Policy
    test new search