Documentation Campaign Campaign v8 Documentation

Configure push notification channel

Last update: March 23, 2025

Applies to:
Campaign v8 Client Console

Topics:
Push

CREATED FOR:

Intermediate
Admin
Developer

To send push notifications with Adobe Campaign, you must first configure your environment and app as detailed in this page. In Adobe Campaign, the channel for sending push notitications is the mobile app channel.

CAUTION

Some important changes to the Android Firebase Cloud Messaging (FCM) service will be released in 2024, and may impact your Adobe Campaign implementation. Your subscription services configuration for Android push messages may need to be updated to support this change. You can already check and take action. Learn more.

Before beginning to send push notifications with Adobe Campaign, you need to ensure configurations and integrations are in place on the mobile app and for tags in Adobe Experience Platform. Adobe Experience Platform Mobile SDK provides client-side integration APIs for your mobiles via Android and iOS compatible SDKs.

To set up your app with Adobe Experience Platform Mobile SDKs, follow these steps:

Check prerequisites.
Set up a mobile tag property in Adobe Experience Platform Data Collection.
Get the Adobe Experience Platform Mobile SDK as detailed in this page.
(optional) Enable logging and lifecycle metrics, as detailed in this page.
(optional) Add Adobe Experience Platform Assurance to your app to validate your implementation. Learn how to implement Adobe Experience Platform Assurance extension in this page.
Configure your iOS and Android mobile services in Adobe Campaign as detailed in this page.
Install and configure Adobe Campaign Extension in your mobile property.
Follow Adobe Experience Platform Mobile SDK documentation to get setup with Adobe Experience Platform Mobile SDKs in your app.

Prerequisites

Set up permissions

Before creating a mobile application, you first need to make sure that you have or assign the correct user permissions for tags in Adobe Experience Platform. User permissions for tags in Adobe Experience Platform are assigned to users through Adobe Admin Console. Learn more in Tags documentation.

CAUTION

Push configuration must be performed by an expert user. Depending on your implementation model and personas involved in this implementation, you might need to assign the full set of permissions to a single product profile or share permissions between the app developer and the Adobe Campaign administrator.

To assign Property and Company rights, follow the steps below:

Access the Admin Console.
From the Products tab, select the Adobe Experience Platform Data Collection card.
Select an existing Product Profile or create a new one with the New profile button. Learn how to create a new New profile in the Admin console documentation.
From the Permissions tab, select Property Rights.
Click Add all. This will add the following right to your product profile:
- Approve
- Develop
- Edit Property
- Manage Environments
- Manage Extensions
- Publish
These permissions are required to install and publish the Adobe Campaign extension, and publish the app property in Adobe Experience Platform Mobile SDK.
Then, select Company rights in the left-hand menu.
Add the following rights:
- Manage App Configurations
- Manage Properties
These permissions are required for the mobile app developer to set up push credentials in Adobe Experience Platform Data Collection.
Click Save.

To assign this Product profile to users, follow the steps below:

Access the Admin Console.
From the Products tab, select the Adobe Experience Platform Data Collection card.
Select your previously configured Product profile.
From the Users tab, click Add user.
Type in your user’s name or email address and select the user. Then, click Save.

NOTE
If the user was not previously created in the Admin console, refer to the Add users documentation.

Configure your app

The technical setup involves close collaboration between the app developer and business administrator. Before starting sending push notifications with Adobe Campaign, you need to define settings in Adobe Experience Platform Data Collection and integrate your mobile app with Adobe Experience Platform Mobile SDKs.

Follow implementation steps detailed in the links below:

For Apple iOS: Learn how to register your app with APNs in Apple Documentation
For Google Android: Learn how to setup up a Firebase Cloud Messaging client app on Android in Google Documentation

Set up a mobile tag property in Adobe Experience Platform Data Collection

Setting up a mobile property allows the mobile app developer or marketer to configure the mobile SDKs. You will typically create a mobile property for each mobile application you want to manage. Learn how to create and configure a mobile property in Adobe Experience Platform Mobile SDK documentation.

Learn more about Adobe Experience Platform Data Collection tags in Adobe Experience Platform documentation.

Once created, open the new tag property and create a library. To do this:

Browse to Publishing Flow in the left navigation and select Add Library.
Enter the name of the library and select the environment.
Select Add All Changed Resources, and Save and Build to development.
Finally, set this library as your working library from the Select a working library button.

Configure your mobile services in Campaign

Once your mobile app has been set up in in Adobe Experience Platform Data Collection, you need to create two services (one for iOS devices, one for Android devices) to be able to send push notifications from Adobe Campaign.

Push notifications are sent to your app users through a dedicated service. When users install your app, they subscribe to this service: Adobe Campaign relies on this service to target only the subscribers of your app. In this service, you need to add your iOS and Android apps to send on iOS and Android devices.

To create a service to send push notifications, follow the steps below:

Browse to Profiles and Targets > Services and Subscriptions tab, and click Create.
Enter a Label and an Internal name, and select a Mobile application type.

NOTE
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. Learn more about target mappings in this page.
Then use the Add icon on the right to define the mobile applications that use this service.

iOS

To create an app for iOS devices, follow these steps:

Select Create an iOS application and click Next.
Enter the name of your app in the Label field.
(optional) You can enrich a push message content with some Application variables. These are fully customizable and a part of the message payload sent to the mobile device.

In the example below, the mediaURl and mediaExt variables are added to create rich push notification and then provides the application with the image to display within the notification.
Browse to the Subscription parameters tab to define the mapping with an extension of the Subscriber applications (nms:appsubscriptionRcp) schema.
Browse to the Sounds tab to define 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.
The integration key is specific to each application. It links the mobile application to Adobe Campaign.

Make sure that the same Integration key is defined in Adobe Campaign and in the application code via the SDK.

Learn more in the Developer documentation

NOTE
The Integration key is fully customizable with string value but needs to be exactly the same as the one specified in the SDK.
You cannot use the same certificate for the development version (sandbox) and the production version of the application.
Select the icon from the Application icon field to personalize mobile application in your service.
Select the Authentication mode. Two modes are available:
- (Recommended) Token-based authentication: Fill in the APNs connection settings Key Id, Team Id and Bundle Id then select your p8 certificate by clicking Enter the private key…. For more on Token-based authentication, refer to Apple documentation.
- Certificate-based authentication: Click Enter the certificate… then select your p12 key and enter the password that was provided by the mobile application developer. Note that this certificate comes with an expiration date and must be renewed on a yearly basis. To avoid a disruption in service for your users, update your certificates before they expire. Certificates are valid for a year and you must update them to continue communicating with APNs.
Use the Test the connection button to validate your configuration.
Click Next to start configuring the production application and follow the same steps as detailed above.
Click Finish.

Your iOS application is now ready to be used in Campaign.

Android

To create an app for Android devices, follow these steps:

Select Create an Android application and click Next.
Enter the name of your app in the Label field.
The integration key is specific to each application. It links the mobile application to Adobe Campaign.

Make sure that the same Integration key is defined in Adobe Campaign and in the application code via the SDK.

Learn more in the Developer documentation

NOTE
The Integration key is fully customizable with string value but needs to be exactly the same as the one specified in the SDK.
Select the icon from the Application icon field to personalize mobile application in your service.
Select HTTP v1 in API version drop-down list.
Click Load project json file to extract project details… link to load your JSON key file. For more information on how to extract your JSON file, refer to Google Firebase documentation.

You can also enter manually the following details:
- Project Id
- Private Key
- Client Email
Use the Test the connection button to validate your configuration.

CAUTION
The Test connection button does not check if the mid-sourcing (MID) server has access to the FCM server.
(optional) 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.
Click Finish then Save. Your Android application is now ready to be used in Campaign.

Below are the FCM payload names to further personalize your push notification:

Message type

Configurable message element (FCM payload name)

Configurable options (FCM payload name)

data message

N/A

validate_only

notification message

title, body, android_channel_id, icon, sound, tag, color, click_action, image, ticker, sticky, visibility, notification_priority, notification_count

validate_only

Configure Adobe Campaign Extension in your mobile property

The Adobe Campaign Classic extension for Adobe Experience Platform Mobile SDKs powers push notifications for your mobile apps and helps you collects user push tokens and manages interaction measurement with Adobe Experience Platform services.

This extension, which applies to both Campaign Classic v7 and Campaign v8, is pre-installed on your environment and must be configured. To configure the extension for your mobile tag property, follow these steps:

Open the tag property you created before.
From the left navigation, browse to Extensions, and open the Catalog tab. Use the search field to find the Adobe Campaign Classic extension.
From the Campaign Classic card, click the Install button.
Enter settings as described in Adobe Experience Platform Mobile SDK documentation.

You can now add Campaign to your app, as detailed in Adobe Experience Platform Mobile SDK documentation.

recommendation-more-help