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.
Key steps are:
You will then be able to create a push notification for iOS devices.
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 Connector tab, fill in the Access URL of the connector field with the following URL:
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 SDK.
If this is not the case, please refer to this page.
Go to the Profiles and Targets > Services and subscriptions node and click New.
Define a Label and an Internal name.
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.
Then click the 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, create your iOS application in Campaign. Follow the steps below:
From your newly created service, click the Add button to select the application type.
The following window appears. Select Create an iOS application and start by entering the Label.
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.
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.
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.
Click Next to start configuring the development application.
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 this page. 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.
Select one of the out-of-the-box icons from the Application icon field to personalize mobile application in your service.
Select the Authentication mode. Note that you can always change your authentication mode later on in the Certificate tab of your mobile application.
Adobe recommends using Token-based authentication for your iOS configuration since this authentication mode is more secured and not bound to certificate expiration.
You can click Test the connection to be sure it is successful.
Click Next to start configuring the production application and follow the same steps as detailed above.
Your iOS application is now ready to be used in Campaign Classic.