Publishing a transactional event publishing-transactional-event
Once configuration is done, the event is ready to be published. The steps to preview, publish, unpublish and delete an event are described below.
A chart illustrating the whole transactional messaging publication process, including publishing and unpublishing event configurations, is available in this section.
Once publication is done:
- The corresponding transactional message is automatically created. See Editing transactional messages.
- The API that will be used by your website developer is deployed and the transactional events can now be sent. See Integrate the event triggering.
Previewing and publishing an event 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 Integrate the event triggering.
note note NOTE The REST API varies according to the selected channel and the selected targeting dimension. For more details on the various configurations, refer to this section. -
Click Publish to start publication.
The API that will be used by your website developer is deployed and the transactional events can now be sent.
-
You can view the publication logs in the corresponding tab.
note important IMPORTANT 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.
-
You can directly access this transactional message through the link located in the left-hand side area.
note note NOTE In order for the event to trigger sending a transactional message, you must modify and publish the message that was just created. See Editing and Publishing a transactional message sections. You also have to integrate this trigger event into your website. -
Once Adobe Campaign starts receiving events related to this event configuration, you can click the Latest transactional events link under the History section to access the latest events sent by your third-party service and processed by Adobe Campaign.
The events (in JSON format) are listed from the most recent to the oldest. This list allows you to check data such as the content or the status of an event, for control and debugging purpose.
Unpublishing an event 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.
Click the Publish button to generate a new REST API.
Deleting an event deleting-an-event
Once an event has been unpublished, or if an event has not been published yet, you can delete it from the event configuration list. To do this:
-
Click the Adobe logo, in the top-left corner, then select Marketing plans > Transactional messages > Event configuration.
-
Hover the mouse over the event configuration of your choice and select the Delete element button.
note note NOTE Make sure the event configuration has the Draft status, otherwise you will not be able to delete it. The Draft status applies to an event that has not been published yet or that has been unpublished. -
Click the Confirm button.
