Push notification implementation has to be performed by expert users. If you need to be assisted, contact your Adobe Account executive or Professional services partner. Push notification is an optional feature. Please check your license agreement and contact your account executive to activate it.
Adobe Campaign allows you to send personalized and segmented push notifications to iOS and Android mobile devices.
These messages are received on mobile applications that you set up in Adobe Campaign by leveraging the Experience Platform SDK. For more information on this, refer to Configuring a mobile application using Adobe Experience Platform SDKs.
In Adobe Campaign, mobile profile attributes data sent from mobile device are stored in Subscriptions to an application (appSubscriptionRcp) resource which allows you to define the data that you want to collect from your applications’ subscribers.
This resource needs to be extended to collect data you intend to send from the mobile device to Adobe Campaign. To do so, refer to this page for the detailed steps.
Two types of push notification are available in Adobe Campaign:
Alert/Message/Badge type notifications enable you to send standard text-based messages with additional content (sound, badge, deeplink, etc.) that you can define in the Advanced options section.
This notification types allow you to add a title and a message in which you can use personalization fields. To be able to personalize your message, make sure you select the Send push on profiles template.
Silent push type notifications are used to silently notify the application without any message or content for the end user. A typical use case for this type of message would be to make the application aware that there is content available on the server to be downloaded.
Some specific configurations can be set up to define notifications behavior. For more on this, refer to this section.
Laws concerning privacy differ by country. Some countries require that you inform users of the types of data collected by mobile applications. Please check the laws pertaining to mobile applications in your country. Make sure push notifications sent to mobile applications comply with the prerequisites and conditions specified by Apple (Apple Push Notification Service) and Google (Google Cloud Messaging or Firebase Cloud Messaging).
To leverage the push notification feature from Campaign, you need to provide a valid push certificate in .pem format with no passwords.
If you have a valid p12 certificate, you can convert it easily into a .pem file using online resources.
Before sending your push notifications, you should:
In Adobe Campaign, make sure you can access the Push notification channel. If you cannot access these channels, contact your account team.
Verify that your user has the necessary permissions in Adobe Campaign Standard and tags in Adobe Experience Platform.
In the Data Collection UI , create a mobile property. For more information, see Set up a mobile property.
In the Data Collection UI , install the Adobe Campaign Standard extension.
In Adobe Campaign Standard, configure the mobile property that you created in the Data Collection UI. For more information, see Setting up your tag application in Adobe Campaign.
Add the channel-specific configuration to your mobile application set up. For more information, see Channel-specific application configuration in Adobe Campaign.
To support mobile use case implementations, see the detailed instructions about extensions, tag rules, and the SDK implementation in Mobile use cases supported in Adobe Campaign Standard by using the Adobe Experience Platform SDKs.
Check out the resources below:
Ensure that the provisioning team has completed the provisioning of Push channel in Adobe Campaign Standard. Implement setPushIdentifier API from SDK. For more on this, refer to this page.
Customers need to provide a valid Push certificate in .pem format in order to send a Push notification. You do not require a password for this certificate.
You can convert a .p12 certificate into a .pem certificate by running the below command in terminal. There are several online resources also available for conversion instructions.
openssl pkcs12 -in pushcert.p12 -out pushcert.pem -nodes -clcerts
You will see the following message.
No, apps will work in either sandbox or production mode and cannot be changed to the other (i.e. sandbox to production app) once set up. We recommend that you test your app in sandbox mode first and then transition to production mode.
To change to production mode, you will have to create another app. Also be sure to not check the sandbox checkbox and to upload a production certificate.
Yes, Campaign supports both platforms at the same time and allows you to upload credentials for both platforms.
Please make sure that your push certificates are valid by testing them here.
Please ensure that you are following the Push payload instructions provided here.
Note that for Android, Campaign only supports Data payload not notification payload
An app has to have a valid Push certificate uploaded as well before it could be made available in the delivery properties.
Please open a customer care ticket.
Mobile App developers need to handle the support for media files in the App. Sometimes network bandwidth may also prevent a media file from rendering. Refer to this page for additional pointers.
Follow the steps below:
More detailed instructions can be found in this page.
An out-of-the-box report is available in Adobe Campaign for Push channel. Refer to this documentation.
See this page to understand how each push metrics are calculated.
Yes, deeplinks are supported in Push messages. Deeplinks should include: