The Webhook channel is an unusual channel in Engage+ in that it's not used as a contact method for reaching your consumers. Instead, it's a communication method, typically used to transfer data between Engage+ and some other client or third-party database or application.
Many clients who utilize the Webhook channel set up Event-triggered Campaigns based on some consumer action, such as an email click, a form submission, or a web event, for example. When the event is identified, the platform will deploy the Webhook Campaign, and send an HTTP request containing information about the event to the client's internal system.
For more information on the Webhook features available through the Messaging platform, please see the document Cheetah Messaging -- Webhook Capabilities.
As an example, let's say you send out order confirmation email messages to your consumers. In the event that one of these messages bounces, you want to be notified so you can follow up with the consumer through another channel, such as over the phone or by SMS text. You could set up a Webhook Campaign that uses "Email Bounce" as its trigger type. When the system identifies a bounced email, it would trigger the deployment of the Webhook Campaign to send an HTTP request message to your internal customer service system. This message could be configured to include the consumer's name, order information, and phone number.
The Webhook Campaign screen allows you to build a simple, custom HTTP request message containing whatever fields you need to include. The fields and their associated values are submitted as key-value pairs, contained within the header of the HTTP request, rather than in the body. These key-value pairs are encoded using the "form-urlencoded" format, where each key-value pair is separated by an ampersand ("&"), and each key is separated from its corresponding value by an equal sign ("="). The request messages are not authenticated, but can optionally be secured by using the HTTPS protocol.
The platform supports the following HTTP methods when sending messages through the Webhook channel:
GET: Used to read or retrieve data without directly modifying it.
POST: Used to create a new asset.
PUT: Used to update an asset (if it already exists), or create an asset (if it doesn't already exist).
PATCH: Used to partially modify an existing asset.
HEAD: Similar to GET, used to read or retrieve data, but without the response body. Instead, only the headers are returned.
DELETE: Used to delete an existing asset.
This topic describes all of the various configuration options available for Webhook Campaigns. This topic assumes that you already created the Campaign (see Campaigns for more details on how to create a Campaign).
The Campaign screen is organized into the following areas:
Triggers |
Audience |
Message |
Sending |
Responses |
Auditing |
Launching |
The Tool Ribbon at the top of the screen provides access to the following general Campaign settings.
Configure Campaign Metadata Engage+ offers the ability to tag Campaigns with custom Metadata fields and values. These Metadata fields allow you to create Filters that look for specific Metadata tags in them, or for use in reports, future Campaigns, or other tasks. You can also add Metadata fields to the Campaign content for personalization. To assign Metadata values to a Campaign
Note: Metadata tagging is not available for every channel. For more information on setting up Metadata fields, see Metadata Settings.
|
Assign Campaign Tags Optionally, you can assign one or more Tags to your Campaign. These Tags serve as an organization tool that allow you to group together items for reports and Filters. To assign a Tag to the Campaign:
|
Configure Report Settings Messaging tracks and reports various system events, such as user clicks, opens, delivery, and more. The platform allows you to configure various report options at a Campaign level. To set the Campaign's report options:
Note: Please speak with your Customer Service Representative for more information on enabling the Delivery Audit feature.
Note: Please speak with your Customer Service Representative for more information on enabling the Google Analytics feature.
|
The Campaign screen provides the following Campaign management features:
Copy a Campaign To copy an existing Campaign:
|
Delete a Campaign When you delete a Campaign, the system moves it from its current folder location into the Recycling Bin, where it can optionally be restored if needed. If the selected Campaign is stored in a folder to which you don't have the proper access privileges, you won't be able to delete that Campaign.
|
Rename a Campaign To rename a Campaign:
|
View Campaign Details To view detailed information about the Campaign:
|
Change Campaign Type From within the Campaign screen, you can switch the Campaign type between a Regular One-off Campaign and either form of triggered Campaign (Date-triggered or Event-triggered). To change the Campaign type:
Note: Depending on the Campaign channel, some of the above Campaign Types may not be available. |
Marketers often need to divide their Campaign Audience into smaller segments, or cells. You might need to do this in order to test the effectiveness of a particular marketing message, or because you need to use a different sending method, or schedule, for the different cells.
Messaging provides you with the ability to create complex, sophisticated ways of segmenting your Audience. The platform supports two different segmentation methods: "A / B Testing" and "Split Cells" (A / B Testing is available only for email Campaigns).
Split Cells allow you to divide your Campaign Audience into different receiving groups, with or without the use of a "remainder" Audience. With Split Cells, you can create a complex hierarchy of nested cells, each of which is designated with a unique code that can be used elsewhere in the platform, such as reports, exports, and Filters. You can enter these cells directly into the user interface, or import them from a spreadsheet. This segmentation method can be used for testing purposes, although that's not really its primary intent, as this method won't calculate a "winner" like A / B Testing does.
Note: Split Cells are available in all Channels, and for all Campaign types.
For more information on configuring Split Cells within your Webhook Campaign, please see Split Cells.
Topic updated: March 2021