ÃÛ¶¹ÊÓƵ

[Also applies to v8]{class="badge positive" title="Also applies to Campaign v8"}

Get started with mobile app channel about-mobile-app-channel

The Mobile App Channel lets you use the ÃÛ¶¹ÊÓƵ Campaign platform to send personalized push notifications to iOS and Android terminals via apps.

Two delivery channels are available:

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 list of technical workflows.

ÃÛ¶¹ÊÓƵ Campaign is compatible with HTTP/2 APNs. For more details on the configuration steps, refer to the this section section.

¹ó´Ç°ùÌý²µ±ô´Ç²ú²¹±ôÌý¾±²Ô´Ú´Ç°ù³¾²¹³Ù¾±´Ç²ÔÌý´Ç²ÔÌý³ó´Ç·ÉÌý³Ù´ÇÌý³¦°ù±ð²¹³Ù±ðÌý²¹Ìý»å±ð±ô¾±±¹±ð°ù²â,Ìý°ù±ð´Ú±ð°ùÌý³Ù´ÇÌý³Ù³ó¾±²õÌý²õ±ð³¦³Ù¾±´Ç²Ô.

Configure push notification channel push-notification-configuration

To send push notifications with ÃÛ¶¹ÊÓƵ Campaign, you must first configure your environment and app. Before beginning to send push notifications with ÃÛ¶¹ÊÓƵ Campaign, you need to ensure configurations and integrations are in place on the mobile app and for tags in ÃÛ¶¹ÊÓƵ Experience Platform. ÃÛ¶¹ÊÓƵ Experience Platform Mobile SDK provides client-side integration APIs for your mobiles via Android and iOS compatible SDKs. SDKs configuration is managed through the Data Collection UI for flexible configuration and extensible, rules-based integrations. Learn more in ÃÛ¶¹ÊÓƵ Campaign v8 documentation.

Data path data-path

The following schemas detail the steps that enable a mobile application to exchange data with ÃÛ¶¹ÊÓƵ Campaign. This process involves three entities:

The three main steps of the notification process are: registration of the application in ÃÛ¶¹ÊÓƵ Campaign (subscription collection), deliveries, and tracking.

Step 1: Subscription collection step-1--subscription-collection

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 ÃÛ¶¹ÊÓƵ Campaign.

Step 2: Delivery step-2--delivery

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 ÃÛ¶¹ÊÓƵ Campaign:

The ÃÛ¶¹ÊÓƵ Campaign server must be able to contact the APNs server on the 443 port for iOS HTTP/2 connector.

To check that it works correctly, use the following commands:

With the iOS HTTP/2 connector, the MTA and web server must be able to contact the APNs on port 443.

If you need to use the iOS HTTP/2 connector through a proxy, refer to this page.