Show Menu
TOPICS×

Configuring the mobile application in Adobe Campaign

You can find below a configuration sample based on a company which sells online holiday packages. His mobile application (Neotrips) is available to its customers in two versions: Neotrips for Android and Neotrips for iOS. To configure the mobile application in Adobe Campaign, you need to:
  • Create a Mobile application type information service for the Neotrips mobile application.
  • Add the iOS and Android versions of the application to this service.
  • Create a delivery for both iOS and Android.
Go to the Subscriptions tab of the service to view the list of subscribers to the service, i.e. all people who have installed the application on their mobile and agreed to receive notifications.

Configuring the mobile application with iOS

The application must have been configured for Push actions BEFORE any integration to Adobe Campaign SDK.
If this is not the case, please refer to this page .

Step 1: Installing the package

  1. Access the package import wizard from Tools > Advanced > Package import... in the Adobe Campaign client console.
  2. Select Install a standard package .
  3. In the list that appears, check Mobile App Channel .
  4. Click Next , then Start to start the package installation.
    Once the packages are installed, the progress bar shows 100% and you can see the following message in the installation logs: Installation of packages successful .
  5. Close the installation window.

Step 2: Configuring iOS external account

For iOS, two connectors are available:
  • The iOS binary connector sends notifications on the legacy binary APNS server.
  • The iOS HTTP/2 connector sends notifications to the HTTP/2 APNS.
To choose which connector you want to use, follow these steps:
  1. Go to Administration > Platform > External accounts .
  2. Select the iOS routing external account.
  3. In the Connector tab, fill in the Access URL of the connector field:
    For iOS HTTP2: http://localhost:8080/nms/jsp/iosHTTP2.jsp
    You can also configure it as follow https://localhost:8080/nms/jsp/ios.jsp but we advise you to use version 2 of the connector.
  4. Click Save .
Your iOS connector is now configured. You can start creating your service.

Step 3: Configuring iOS service

  1. Go to the Profiles and Targets > Services and subscriptions node and click New .
  2. Define a Label and an Internal name .
  3. Go to the Type field and select Mobile application .
    The default Subscriber applications (nms:appSubscriptionRcp) target mapping is linked to the recipients table. If you want to use a different target mapping, you need to create a new target mapping and enter it in the Target mapping field of the service. For more on creating target mapping, refer to the Configuration guide .
  4. Then click the Add button to select the application type.
  5. The following window appears. Select Create an iOS application and start by entering the Label .
  6. As an option, you can enrich a push message content with some Application variables if needed. These are fully customizable and a part of the message payload sent to the mobile device. In the following example, we add mediaURl and mediaExt to create rich push notification and then provides the application with the image to display within the notification.
  7. The Subscription parameters tab allows you to define the mapping with an extension of the Subscriber applications (nms:appsubscriptionRcp) schema.
    Make sure that you do not use the same certificate for the development version (sandbox) and the production version of the application.
  8. The Sounds tab allows you to specify a sound to play. Click Add and fill Internal name field which must contain the name of the file embedded in the application or the name of the system sound.
  9. Click Next to start configuring the development application.
  10. Make sure the same Integration key is defined in Adobe Campaign and in the application code via the SDK. For more on this, refer to: Integrating Campaign SDK into the mobile application . This integration key, which is specific to each application, lets you link the mobile application to the Adobe Campaign platform.
    The Integration key is fully customizable with string value but needs to be exactly the same as the one specified in the SDK.
  11. Select one of the out-of-the-box icon from the Application icon field to personalize mobile application in your service.
  12. Click the Enter the certificate... link then select the authentication certificate and enter the password that was provided by the mobile application developer. You can click Test the connection to be sure it is successful.
    Apple requires different certificates for Development and Production versions of a same mobile application. You will need to configure the two separate applications in Adobe Campaign.
  13. Click Next to start configuring the production application and follow the same steps as detailed above.
  14. Click Finish . Your iOS application is now ready to be used in Campaign Classic.

Step 4: Creating an iOS rich notification

With iOS 10 or higher, it is possible to generate rich notifications. Adobe Campaign can send notifications using variables that will allow the device to display a rich notification.
You now need to create a new delivery and link it to the mobile application that you created.
  1. Go to Campaign management > Deliveries .
  2. Click New .
  3. Select Deliver on iOS (ios) in the Delivery template drop-down. Add a Label to your delivery.
  4. Click To to define the population to target. By default, the Subscriber application target mapping is applied. Click Add to select our previously created service.
  5. In the Target type window, select Subscribers of an iOS mobile application (iPhone, iPad) and click Next .
  6. In the Service drop-down, select your previously created service then the application you want to target and click Finish . The Application variables are automatically added depending on what was added during the configuration steps.
  7. Edit your rich notification.
  8. Check the Mutable content box in the edit notification window to allow the mobile application to download media content.
  9. Click Save and send your delivery.
The image and web page should be displayed in the push notification when received on the subscribers' mobile iOS devices.

Configuring the mobile application with Android

Step 1: Installing the package

  1. Access the package import wizard from Tools > Advanced > Package import... in the Adobe Campaign client console.
  2. Select Install a standard package .
  3. In the list that appears, check Mobile App Channel .
  4. Click Next , then Start to start the package installation.
    Once the packages are installed, the progress bar shows 100% and you can see the following message in the installation logs: Installation of packages successful .
  5. Close the installation window.

Step 2: Configuring Android external account

For Android, two connectors are available:
  • The V1 connector which allows one connection per MTA child.
  • The V2 connector which allows simultaneous connections to the FCM server to improve throughput.
To choose which connector you want to use, follow these steps:
  1. Go to Administration > Platform > External accounts .
  2. Select the Android routing external account.
  3. In the Connector tab, fill in the JavaScript used in the connector field:
    For Android V2: https://localhost:8080/nms/jsp/androidPushConnectorV2.js
    You can also configure it as follow https://localhost:8080/nms/jsp/androidPushConnector.js but we advise you to use version 2 of the connector.
  4. For Android V2, one additional parameter is available in the Adobe Server configuration file (serverConf.xml):
    • maxGCMConnectPerChild : Maximum limit of parallel HTTP requests to the FCM initiated by each child server (8 by default).

Step 3: Configuring Android service

  1. Go to the Profiles and Targets > Services and subscriptions node and click New .
  2. Define a Label and an Internal name .
  3. Go to the Type field and select Mobile application .
    The default Subscriber applications (nms:appSubscriptionRcp) target mapping is linked to the recipients table. If you want to use a different target mapping, you need to create a new target mapping and enter it in the Target mapping field of the service. For more on creating target mapping, refer to the Configuration guide .
  4. Then click the Add button to select the application type.
  5. Select Create an Android application .
  6. Enter a Label .
  7. Make sure the same Integration key is defined in Adobe Campaign and in the application code via the SDK. For more on this, refer to: Integrating Campaign SDK into the mobile application .
    The Integration key is fully customizable with string value but needs to be exactly the same as the one specified in the SDK.
  8. Select one of the out-of-the-box icon from the Application icon field to personalize mobile application in your service.
  9. Enter the application's connection settings: enter the project key that was provided by the developer of the mobile application.
  10. As an option, you can enrich a push message content with some Application variables if needed. These are fully customizable and a part of the message payload sent to the mobile device.
    In the following example, we add title , imageURL and iconURL to create rich push notification and then provides the application with the image, title and icon to display within the notification.
  11. Click Finish then Save . Your Android application is now ready to be used in Campaign Classic.
By default, Adobe Campaign saves a key in the User identifier (@userKey) field of the Subscriber applications (nms:appSubscriptionRcp) table. This key enables you to link a subscription to a recipient. To collect additional data (such as a complex reconciliation key), you need to apply the following configuration:
  1. Create an extension of the Subscriber applications (nms:appsubscriptionRcp) schema and define the new fields.
  2. Define the mapping in the Subscription parameters tab.
    Make sure the configuration names in the Subscription parameters tab are the same as those in the mobile application code. Refer to the Integrating Campaign SDK into the mobile application section.

Step 4: Creating an Android rich notification

You now need to create a new delivery and link it to the mobile application that you created.
  1. Go to Campaign management > Deliveries .
  2. Click New .
  3. Select Deliver on Android (android) in the Delivery template drop-down. Add a Label to your delivery.
  4. Click To to define the population to target. By default, the Subscriber application target mapping is applied. Click Add to select our previously created service.
  5. In the Target type window, select Subscribers of an Android mobile application and click Next .
  6. In the Service drop-down, select your previously created service then application and click Finish . The Application variables are automatically added depending on what was added during the configuration steps.
  7. Edit your rich notification.
  8. Click Save and send your delivery.
The image and web page should be displayed in the push notification when received on the subscribers' mobile Android devices.