Purpose
The purpose of this connector is to enable you to send emails using Adobe Campaign Classic by using Booxi's Webhook Event API.
Prerequisites
To create and configure a campaign connector, the following is required:
Use Adobe Campaign Classic v7 and its corresponding Desktop Client
Your Adobe Campaign account must have administrator level rights
You must provide Booxi with email template names
Request Booxi to activate the Adobe module
It is possible to manage the IP range from which messages are sent to the Adobe server.
Connector Configuration
Account Configuration
To configure an account, you must provide the following information:
Data | Description |
merchant id | The Booxi merchant ID that requires an Adobe Classic configuration. |
host name url | The host of the Adobe SOAP router. This is the endpoint where the payloads will be sent out. |
backend authorization username | The username to use when sending requests to the SOAP router. The requests must be authenticated. This data is passed on in the SOAP request. |
backend authorization password | The password to use when sending requests to the SOAP router. The requests must be authenticated. This data is passed on in the SOAP request. |
Enable staff messages | Indicates if emails directed to Staff should be sent using Adobe. |
Enable reservation messages | Indicates if emails related to a group reservations should be sent using Adobe. |
Enable appointment messages | Indicates if emails related to appointments should be sent using Adobe. |
Enable client notification messages | Indicates if emails related to client notifications should be sent using Adobe. |
The data above is used to determine where and what to send to the client’s Adobe server.
The structure of the message sent to Adobe is described here: SOAP Context.
The username and password are sent in clear text in the SOAP message.
The ONLY wishedChannel currently supported is: EMAIL
Mapping Templates (eMail Only)
You must identify what template will be assigned to the below events. Once the mapping has been provided, we (Booxi) will proceed to the event mapping.
# | Booxi Event | Client Template Name |
1 | Confirmation | Fill In |
2 | Request | Fill In |
3 | Awaiting | Fill In |
4 | Changed | Fill In |
5 | Store Cancel | Fill In |
6 | Client / Attendee Cancel | Fill In |
7 | No Show | Fill In |
8 | Completed | Fill In |
9 | Reminder | Fill In |
10 | Recall | Fill In |
11 | Client Notification | Fill In |
Mapping any event is optional. If an event isn’t mapped, NO message / payload will be sent to the client’s Adobe server.
Templates can be adapted to the country and language specified by the webhook event (e.g. booxi_ConfirmRdv_{lang}_{country})
The above values are dynamically replaced with the appropriate values, when provided in the name of the template mapping.
Language and country can be identified with a 2-letter code
(ISO 639-1 & ISO 3166) (i.e booxi_Confirm_EN_US)
Event Processing
Once you designed and published the transactional message template, if a corresponding event is triggered, the main steps below are performed on the execution instance:
When the event is generated by the external information system, the relevant data is sent to Campaign via the PushEvent and PushEvents methods. See Event collection.
The event is linked to the appropriate message template. See Routing towards a template.
Once the enrichment stage is complete, the delivery is sent. See Delivery execution. Each targeted recipient receives a personalized message.
Message payloads are sent in .XML format.
SOAP Context
For a list of all attributes found in the SOAP context, consult the following document.
Limitations
Only email notifications are currently supported.
ICS files are not supported.