The Mobile Push Application Groups screen is used to register your mobile app (or apps) within Engage+. You must register your mobile app if you intend to use the Push Notification channel to contact your customers. This step is part of the larger process of setting up the Push Notification channel (see Push Notification Channel Setup for more details on this process).
Apps can be organized into "Application Groups," which simplifies the process of sending out notifications. When you create a Push Notification Campaign, the notifications are sent out to an entire Application Group at once. For example, if you have an iOS version and a Google Android version of an app, you could add both versions to the same Application Group, and send out notifications to both versions of the app at the same time.
Separate Application Groups must be created for use with EDP and non-EDP Push Notifications. There are slight differences between EDP Application Groups and non-EDP Application Groups, the main one being that it is not possible to create a separate iOS and Google Android version of an Application Group for EDP.
For more information on the Push Notification features available through the Messaging platform, please see the document Engage+ -- Push Notification Capabilities.
The Mobile Push Application Groups screen is accessible by the following method:
From the System Tray, select Web > Management > Mobile Push Application Groups
Create a New Application Group To create a new Application Group:
|
Add New Application (only applicable to Messaging Application Groups) For Messaging Application Groups, follow these steps to add an application to the group:
|
Define Push Payload Push Notifications are delivered to mobile devices as JSON messages. This message contains the basic text of the notification, but it can be used for more advanced features as well. For example, the JSON message can define the portion of the message that appears within the "Alert" section of the user's device, or a "deep link" to open the app to a specific page, or play a video, or show order information. The Push Payload section of this screen provides a JSON editor that can be used to define a JSON form schema. This form schema is a set of instructions that determines the appearance and options that are available when building the content of a Push Notification Campaign. Sample code is included by default, and this is what you will see in the Payload section of a Push Notification Campaign. For EDP Application Groups, this Push Payload JSON editor will show two tabs for the two operating systems: iOS and Android. To make changes:
|
View or Edit an Application Group To view or edit an existing Application Group:
|
Assign an Application Group to a Campaign Source Table Note: This section does not apply to EDP Application Groups. When you define a Campaign in Messaging, you must define the source table (usually something like "Customers" or "Recipients") that the Campaign will use to get its recipients, and to update the Status ID field that controls recipient eligibility to be contacted. For Campaigns in the Push Notification channel, the source table must be linked to the Application Group that you want to use for your Campaign. Note: Once you assign an Application Group to a table, you can't remove that assignment. To assign an Application Group to a table:
The system automatically creates a new "Application Group Status ID" field for each selected Application Group. The Status ID field uses Status ID Codes to indicate the eligibility of this consumer to be included in a campaign. You'll see this new Status ID field listed on the Table screen with the default name of: "<Field name> <Application Group name> Status ID."
|