If you want to create a multilingual transactional message, define an additional event attribute with the
AC_language
ID. This only applies to event transactional messages.
After the event is published, the steps for editing the content of a multilingual transactional message are the same as for a multilingual standard email. See
Creating a multilingual email.

Defining data collections

You can add to the event content a collection of elements, each element itself including several attributes.

This collection can be used in a transactional email to add product listings to the content of the message, for example a list of products - with the price, reference number, quantity, etc. for each product of the list.

In the
Collections
section, click the
Create element
button.

Add a label and an ID for your collection.

Add all the fields you want to display in the transactional message for each product of the list.

In this example, we added the following fields:

Once the event and the message are published, you will be able to use this collection in your transactional message.

Enriching the transactional message content

Enriching the transactional message content with information from the Adobe Campaign database enables you to personalize your messages. From the last name or CRM ID of each of your recipients, for example, you can recover data such as their address or date of birth or any other custom field added in the Profile table, in order to personalize the information that is sent to them.

It is possible to enrich the transactional message content with information from extended
Profile
or
Service
resources.

This information can also be stored in new resources. In that case, the resource must be linked to the
Profile
or
Service
resources either directly, or via another table. For example, in the configuration below, it is possible to enrich the transactional message content with information from the
Product
resource like the product category or ID, if the
Product
resource is linked to the
Profile
resource.

Select the resource with which you want to link your message. In this case, choose the
Profile
resource.

Use the
Create element
button to link a field from the selected resource to one of the fields you previously added to the event (see
Defining the event attributes).

In this example, we reconcile the
Last name
and the
First name
fields with the corresponding fields in the
Profile
resource.

In the
Targeting enrichment
section, select the enrichment that will be used as the message target during the delivery execution. In this example, select
Profile
.
Selecting a targeting enrichment is mandatory for profile-based events.

Once the event and the message are published, the link with the
Profile
resource will allow you to enrich the content of the transactional message.

Previewing and publishing the event

Before being able to use the event, you must preview and publish it.

Click the
API preview
button to see a simulation of the REST API that will be used by your website developer before it is published. Once the event is published, this button also allows you to see a preview of the API in production. See
Integrating the triggering of the event in a website.

Each time you modify the event, you must click
Publish
again to generate the updated REST API that will be used by your website developer.

Once the event has been published, a transactional message linked to the new event is automatically created. In order for this event to trigger sending a transactional message, you must modify and publish the message that was just created. See
Event transactional messages.

You can access the transactional message that was created directly from the link in the left-hand side area.

Unpublishing an event

The
Unpublish
button lets you cancel the publication of the event, which deletes from the REST API the resource corresponding to the event that you previously created. Now, even if the event is triggered through your website, the corresponding messages are not sent anymore and they are not stored in the database.

Integrating the triggering of the event in a website

Once you have created an event, you will have to integrate the triggering of this event into your website.

In the example described in the
Transactional messaging operating principle section, you want a "Cart abandonment" event to be triggered whenever one of your clients leaves your website before purchasing the products in their cart. To do this, your website web developer must use the Adobe Campaign Standard REST API.

Event-based transactional messaging is supposed to use only the data that are in the sent event to define the recipient and the message content personalization. However, you can enrich the content of your transactional message using information from the Adobe Campaign database.

When previewing the event, the REST API contains an attribute specifying the email address or mobile phone according to the selected channel.

Once the event has been published, a transactional message linked to the new event is automatically created. In order for the event to trigger sending a transactional message, you must modify and publish the message that was just created, see
Event transactional messages.

Add fields to the event, in order to be able to personalize the transactional message (see
Defining the event attributes).
You must add at least one field to create an enrichment. You do not need to create other fields such as First name and Last name as you will be able to use personalization fields from the Adobe Campaign database.

When previewing the event, the REST API does not contain an attribute specifying the email address or the mobile phone as it will be retrieved from the
Profile
resource.

Once the event has been published, a transactional message linked to the new event is automatically created. In order for the event to trigger sending a transactional message, you must modify and publish the message that was just created, see
Sending a profile transactional message.

Event-based transactional push notifications

To be able to send transactional push notifications, you need to configure Adobe Campaign accordingly. See
Push configuration.

To send an anonymous transactional push notification to all users who have opted in to receive notifications from your mobile application, you first need to create and configure an event targeting the data contained in the event itself. The corresponding steps are presented below.

The event must contain the three following elements:

A registration token, which is the user ID for one mobile application and one device. It may not correspond to any profile from the Adobe Campaign database.

A mobile application name (one for all devices - Android and iOS). This is the ID of the mobile application configured in Adobe Campaign that will be used to receive push notifications on the users' devices. For more on this, refer to this
page

A push platform ("gcm" for Android or "apns" for iOS).

When creating the event configuration, select the
Mobile application
channel and the
Real-time event
targeting dimension (see
Creating an event).

Event-based transactional messaging is supposed to use only the data that are in the sent event to define the recipient and the message content personalization. However, you can enrich the content of your transactional message using information from the Adobe Campaign database.

Profile-based transactional push notifications

To send a transactional push notification to the Adobe Campaign profiles who have subscribed to your mobile application, you first need to create and configure an event targeting the Adobe Campaign database.

When creating the event configuration, select the
Mobile application
channel and the
Profile
targeting dimension (see
Creating an event).

By default, the transactional push notification will be sent to all mobile applications to which the recipients subscribed. To send the push notification to a specific mobile application, select it in the list. The other mobile applications will be targeted by the message but will be excluded from the sending.

You must add at least one field to create an enrichment. You do not need to create other fields such as First name and Last name as you will be able to use personalization fields from the Adobe Campaign database.

Configuring an event to send a follow-up message

A follow-up message is a predefined marketing delivery template that can be used in a workflow to send messages to the recipients of a specific transactional message. For more on this, see
Follow-up messages.

Once the event has been published, a transactional message and a follow-up delivery template linked to the new event are automatically created. For more on using follow-up messages, see
Sending a follow-up message.

Use case: configuring an event to send a transactional message

In this example, we want to configure an event in order to send confirmation messages after each purchase on our website with the following prerequisites:

As we want to identify our client via his CRM ID, first make sure that the
Profile
resource has been extended with this new field.

In the same way, a custom resource corresponding to purchases must have been created and published, and must be linked to the
Profile
resource. This way, you will be able to retrieve information from this resource to enrich the message content.