This document details the process for integrating your mobile application with the Adobe Campaign platform. It does not provide information on how to create the mobile application or how to configure it for managing notifications. If you would like further information on this, refer to the official Apple documentation and Android documentation.
The sections below provide information that is specific to the mobile app channel.
For global information on how to create a delivery, refer to this section.
The Mobile App Channel lets you use the Adobe Campaign platform to send personalized notifications to iOS and Android terminals via apps. Two delivery channels are available:
An iOS channel that enables you to send notifications to Apple mobile devices.
An Android channel that enables you to send data messages to Android mobile devices.
Corresponding to those two channels there are two delivery activities in the campaign workflows:
Two transactional message templates are also available for transactional messaging.
You can define the application behavior for when the user activates the notification to display the screen that matches the application context. For example:
The NMAC opt-out management (mobileAppOptOutMgt) workflow updates notification unsubscriptions on mobile devices. For more information on this workflow, refer to the Workflows guide.
Adobe Campaign is compatible with both binary and HTTP/2 APNs. For more details on the configuration steps, refer to the Configuring a mobile application in Adobe Campaign section.
The following schemas detail the steps that enable a mobile application to exchange data with Adobe Campaign. This process involves three entities:
The three main steps of the notification process are: registration of the application in Adobe Campaign (subscription collection), deliveries, and tracking.
The mobile application is downloaded by the user from the App Store or from Google Play. This application contains the connection settings (iOS certificate and project key for Android) and the integration key. The first time the application is opened, (depending on configuration), the user can be asked to enter registration information (@userKey: email or account number for instance). At the same time, the application questions the notification service to collect a notification ID (push ID). All this information (connection settings, integration key, notification identifier, userKey) is sent to Adobe Campaign.
Marketers target application subscribers. The delivery process sends the connection settings to the notification service (iOS certificate and project key for Android), the notification ID (push ID) and the content of the notification. The notification service sends notifications to the targeted terminals.
The following information is available in Adobe Campaign:
The Adobe Campaign server must be able to contact the APNs server on the following ports:
2195 (sending) and 2186 (feedback service) for iOS binary connector
443 for iOS HTTP/2 connector
Starting Campaign 20.3 release, the iOS legacy binary connector is deprecated. If you are using this connector, you need to adapt your implementation accordingly. Learn more
To check that it works correctly, use the following commands:
If an iOS binary connector is used, the MTA and web server must be able to contact the APNs on port 2195 (sending), the workflow server must be able to contact the APNs on port 2196 (feedback service).
If an iOS HTTP/2 connector is used, the MTA, web server and workflow server must be able to contact the APNs on port 443.