Transactional messaging settings

As a Managed Cloud Services user, contact Adobe to install and configure Campaign Transactional messaging in your environment.

Transactional messaging capabilities are detailed in this section.

Understand transactional messaging architecture in this page.

Define permissions

To create new users for Message Center execution instances hosted on Adobe Cloud, you need to contact Adobe Customer Care. Message Center users are specific operators that require dedicated permissions to access ‘Real time events’ (nmsRtEvent) folders.

Schema extensions

All schema extensions made on the schemas used by Message Center technical workflows on either control or execution instances need to be duplicated on the other instances used by Adobe Campaign transactional messaging module.

Learn more about Message center technical workflows in Campaign Classic v7 documentation

Send transactional push notifications

When combined with Mobile app channel module, transactional messaging enables you to push transactional messages through notifications on mobile devices.

The Mobile app channel is detailed in Campaign Classic v7 documentation.

To send transactional push notifications, you need to perform the following configurations:

  1. Install the Mobile App Channel package onto the control and execution instances.


    Check your license agreement before installing a new Campaign built-in package.

  2. Replicate the Mobile application service and the associated mobile applications on the execution instances.

In order for Campaign to send transactional push notifications, the event must contain the following elements:

  • The mobile device ID: registrationId for Android and deviceToken for iOS. This ID represents the “address” that the notification will be sent to.
  • The link to the mobile application or integration key (uuid) which lets you retrieve connection information specific to the application.
  • The channel to which the notification will be sent (wishedChannel): 41 for iOS and 42 for Android.
  • Other data to leverage for personalization.

Here is an example of an event that contains this information:

<SOAP-ENV:Envelope xmlns:xsd="" xmlns:xsi="" xmlns:SOAP-ENV="">

              <rtEvent wishedChannel="41" type="DELIVERY" registrationToken="2cefnefzef758398493srefzefkzq483974">
                <mobileApp _operation=”none” uuid="com.adobe.NeoMiles"/>
                    <deliveryTime>1:30 PM</deliveryTime>


On this page