Once the package is installed, you can define your iOS app settings in Adobe Campaign Classic.
To learn how to configure your app for Android and how to create a delivery for Android, refer to this section.
For iOS, the iOS HTTP/2 connector sends notifications to the HTTP/2 APNs.
To configure this connector, follow these steps:
Go to Administration > Platform > External accounts.
Select the iOS routing external account.
In the [!UICONTROL Connector] tab, fill in the [!UICONTROL Access URL of the connector] field with the following URL:
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
Click [!UICONTROL Save].
Your iOS connector is now configured. You can start creating your service.
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.
Go to the [!UICONTROL Profiles and Targets > Services and subscriptions] node and click [!UICONTROL New].
Define a [!UICONTROL Label] and an [!UICONTROL Internal name].
Go to the [!UICONTROL Type] field and select [!UICONTROL Mobile application].
The default [!UICONTROL 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 [!UICONTROL Target mapping] field of the service. For more on creating target mapping, refer to the Configuration guide.
Then click the [!UICONTROL Add] button to select the application type.
Create your iOS Development and Production applications. For more on this, refer to this section.
After creating your service, you now need to create your iOS application:
From your newly created service, click the [!UICONTROL Add] button to select the application type.
The following window appears. Select [!UICONTROL Create an iOS application] and start by entering the [!UICONTROL Label].
As an option, you can enrich a push message content with some [!UICONTROL 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.
The [!UICONTROL Subscription parameters] tab allows you to define the mapping with an extension of the [!UICONTROL 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.
The [!UICONTROL Sounds] tab allows you to specify a sound to play. Click [!UICONTROL Add] and fill [!UICONTROL Internal name] field which must contain the name of the file embedded in the application or the name of the system sound.
Click [!UICONTROL Next] to start configuring the development application.
Make sure the same [!UICONTROL 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 [!UICONTROL Integration key] is fully customizable with string value but needs to be exactly the same as the one specified in the SDK.
Select one of the out-of-the-box icons from the [!UICONTROL Application icon] field to personalize mobile application in your service.
Select the [!UICONTROL Authentication mode]. Note that you can always change your authentication mode later on in the [!UICONTROL Certificate] tab of your mobile application.
Adobe recommends using [!UICONTROL Token-based authentication] for your iOS configuration since this authentication mode is more secured and not bound to certificate expiration.
You can click [!UICONTROL Test the connection] to be sure it is successful.
Click [!UICONTROL Next] to start configuring the production application and follow the same steps as detailed above.
Click [!UICONTROL Finish].
Your iOS application is now ready to be used in Campaign Classic.
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.
Go to [!UICONTROL Campaign management] > [!UICONTROL Deliveries].
Click [!UICONTROL New].
Select [!UICONTROL Deliver on iOS (ios)] in the [!UICONTROL Delivery template] drop-down. Add a [!UICONTROL Label] to your delivery.
Click [!UICONTROL To] to define the population to target. By default, the [!UICONTROL Subscriber application] target mapping is applied. Click [!UICONTROL Add] to select our previously created service.
In the [!UICONTROL Target type] window, select [!UICONTROL Subscribers of an iOS mobile application (iPhone, iPad)] and click [!UICONTROL Next].
In the [!UICONTROL Service] drop-down, select your previously created service then the application you want to target and click [!UICONTROL Finish].
The [!UICONTROL Application variables] are automatically added depending on what was added during the configuration steps.
Edit your rich notification.
Check the [!UICONTROL Mutable content] box in the edit notification window to allow the mobile application to download media content.
Click [!UICONTROL 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.