- Adobe AEM Mobile account
- Adobe Analytics account (not Analytics Essentials)
- Adobe Mobile Marketing access (requires additional purchase through Digital Marketing Cloud)
- Android certificate for signing apps
- iOS certificates for signing apps and sending push notifications
Push messages are sent to mobile app users who have opted in to receive notifications. Push messages are useful for re-engaging passive users or conveying time-specific and location-specific information. Push messages appear outside of your app.
When you create an AEM Mobile app through On-Demand Services, you have two options for sending push notifications. You can use either the On-Demand Services Notifications feature or the Marketing Cloud. Using the On-Demand Services portal supports background push notifications (iOS) as well as text notifications (iOS and Android). For details, see Send push notifications for AEM Mobile apps.
Using the Marketing Cloud allows you to send push notifications to iOS and Android app users. Sending push notifications using the Marketing Cloud is available only if you have an Adobe Analytics account and access to the Adobe Mobile Marketing, available through a Digital Marketing Cloud purchase. Push messages sent through Marketing Cloud use Google Cloud Messaging (GCM) for Android apps and Apple Push Notification Service (APNS) for iOS apps. You can target push messages to users by specifying Analytics segments or custom segments.
You must perform several tasks before you can configure Push Messaging in applications. The steps are slightly different for iOS and Android.
- Obtain the Google server API key and google-services.json file.
- Configure the app for push services in Mobile Marketing dashboard (https://mobilemarketing.adobe.com)
- Build or edit the Android app in On-Demand Services and download the .apk.
- Use a script to enable Android push notification in the unsigned .apk file.
- Sign the .apk file and load it on devices for testing.
- Send a push notification from Mobile Marketing dashboard.
For iOS push notifications, you can use either On-Demand Services or Marketing Cloud to send push notifications, or both.
- Set up the app for push services in Mobile Marketing dashboard (https://mobilemarketing.adobe.com). This step requires you to upload your push notification certificate.
- Build or edit the iOS app in On-Demand Services. Download the .ipa file, sign it, and load it on devices.
- Send a push notification from Mobile Marketing dashboard.
In order to send notifications to your AEM Mobile app through Google Cloud Messaging, you need to use the Google Developer Console to configure the app. You will obtain a Server API key and download a .json file. This information ties together the AEM Mobile app, the Marketing Cloud push services, and Google Cloud Messaging.
When you configure the app in Mobile Marketing, you establish a connection between Mobile Marketing Push Services and either Google Cloud Messaging or Apple Push Notifications Services, or both.
To enable the Push Services feature, you must log in to the Mobile Core Service using an Adobe ID that is linked to your Adobe Analytics account. The Push Services option is not available if you log in using your existing Adobe Analytics account. (When you sign in using an Analytics account, you are prompted for Company Name, User Name, and Password. When you sign in using an Adobe ID, you are prompted for Adobe ID and Password).
Use an Adobe ID, not the Analytics account information that includes the Company Name.
If necessary, sign in using an Adobe ID that is not associated with an Analytics account, and link it to the Analytics account. You do so by signing in and clicking an active service such as Analytics. For details, see the "Account Linking" section in the Organizations and Account Settings article.
Google: Click Google. Copy the Server API Key value obtained in the previous set of steps and paste it into the API Key field. (Make sure that you get this API Key value from the Google console, not from the google-services.json file.) Click Save.
Apple: Click Apple. Drag and drop your private key and/or certificate. If your private key is password-encrypted, specify its password. If the .p12 does not include the certificate, drag and drop the certificate file (.cer) as well.
- In the Apple iOS Developer portal, make sure that your App ID is configured to enable push notifications.
- We recommend that you use production push certificates instead of development push certificates. To test production push notifications before submitting your app, you can use an Ad Hoc provisioning profile so that you can install the distribution app on a limited number of devices.
- For information about creating iOS certificates, see iOS Publishing Guide for AEM Mobile.
After you configure the app in Mobile Marketing, rebuild or create your app in On-Demand Services, as described next.
Before rebuilding or creating your app, wait at least one hour after creating the project to allow for the report data to propagate between AEM Mobile and Marketing Cloud.
For additional information, see the Marketing Cloud article Prerequisites to Enabling Push Messaging.
Now that you have configured Mobile Services and your app for push notifications, you can use the Mobile Marketing Dashboard to send messages to users.
After an app is launched, it takes approximately one hour for the app to register with the push services.
For details, see Create a push message.
Under Audience tab, select your intended audience. It should tell you approximately how many devices it would reach. Click Next.
For example, if you want to send the message to all app users who have allowed notifications, you can specify Launches ≥ 0.
To create a deep link that users can tap to open a specific article or collection, click Show Advanced Options, and specify the following information in the Payload text field. At this time, deep linking works only on iOS devices.
If you just want to deep link to a collection instead of an article, omit the article strings. Do not include the angle brackets (< >) in <collectionName> and <articleName>.
After you send the push notification, check the notification details to make sure that the number of target devices is greater than zero. If the number sent is 0, then you likely have the incorrect Google Cloud Marketing API key. Make sure that you get the API key from the Google console, not from the the google-services.json file, as described previously.
You can use Mobile Services to send a background push notification. At this time, background notifications are supported only in iOS apps. The steps for sending a background push notification is similar to the process for sending a push message. For a background notification, you need to specify Payload information that you construct from your project ID and other information.
- Following the previous set of steps to send a push message.
- In the Experience section, click Show Advanced Options, and then specify the appropriate information in the Payload field.