The Setup section of the Campaign screen is used to configure many of the options and parameters for your Campaign, and to assign additional assets to the Campaign. This section is accessible by clicking the setup tab
|
The Marigold Help Center provides access to a wide range of enablement videos on many Marigold solutions that you can take as needed. Click here to browse to the video on how to use the Setup section. |
The features and options available from the Setup section are described below.
When you're finished with the Setup section, click next at the bottom of the screen to move to the Content section, or click the content tab.
The Triggers sub-section is displayed only for Event-triggered Campaigns, and is used to configure the Trigger that will cause the Campaign to deploy.
A Trigger is a specific event or mechanism that causes Messaging to create and deploy a message within an Event-triggered Campaign. Messaging supports a wide range of trigger types, such as web form submissions, API requests, link clicks, and so forth. To define a Trigger in an Event-triggered Campaign:
Note: For more details on the Trigger types supported by Messaging, as well as the configuration options and criteria available for each type, please see Event Trigger Options.
Note: If you assign more than one trigger type to a Campaign, any one of the assigned triggers will cause the Campaign to deploy. For example, let's say you assigned "Form Submission" and "Web Event" triggers to your Campaign. Either one of these actions will trigger the Campaign; you don't need both actions to occur.
|
The advanced event trigger (AET) API allows you to perform hierarchical inserts of multiple records into multiple tables via an API request message, then use that data to populate and trigger the deployment of an Event-triggered Campaign. For more details on AET, please see Advanced Event Trigger. When configuring this Event-triggered Campaign, the system displays several options that are unique to AET. These options are displayed only in an Event-triggered Campaign that uses "Advanced Event Trigger" as the trigger type. Email Ban ListWhen using advanced event trigger to deploy email Campaigns, you have the option of validating the email addresses in the API payload against the global and custom Banned Email lists (see Email Ban for more information). If you enable this validation check, the system will suppress any email addresses that are found on either the global or custom lists. If you disable this validation check, the system will automatically deploy email messages to every email address included in the API payload. By default, this feature is disabled. To enable the Email Ban List validation for an AET Campaign:
Check Unsubscribe StatusWhen using advanced event trigger to deploy email Campaigns, you have the option of validating the email addresses in the API payload against the Sender Profile Status ID field. If you enable this validation check, the system will suppress any email addresses that have an "unsubscribed" Status ID Code. If you disable this validation check, the system will automatically deploy email messages to every email address included in the API payload. By default, this feature is disabled. To enable the Sender Profile Status ID validation for an AET Campaign:
Note: If you check the "AET: Enable AET Tracking Params" option (described below), the "AET: Enable Unsubscribe" check box is hidden. If you need to suppress unsubscribed recipients from the Campaign, then you must first uncheck "AET: Enable AET Tracking Params," then check "AET: Enable Unsubscribe." See below for more details on the "AET: Enable AET Tracking Parms" option. AttachmentsThe advanced event trigger endpoint allows you to optionally send attachments along with the request message. The attachments will then be included within the email message that gets sent to the Campaign's recipients. The use of AET attachments must be enabled within your client account, and also within the AET Event-triggered Campaign. Please speak with your Client Services Representative to enable AET attachments at the client account level. By default, this feature is disabled at the Campaign level. To enable AET attachments at a Campaign level:
AET Tracking ParametersThe AET Tracking Parameters feature is designed to provide higher throughput and more consistent response times for AET messages. By default, this flag is enabled. To disable the Tracking Parameters for an AET Campaign:
Note: If you check the "AET: Enable AET Tracking Params" option, the "AET: Enable Unsubscribe" flag is removed from the screen. The platform doesn't support the use of the "Enable Unsubscribe" feature in conjunction with using AET Tracking Parameters.
|
The Audience sub-section is used to select the audience of intended recipients for this Campaign.
The Audience refers to the universe of recipients that you're targeting with this Campaign. Audiences are usually defined through the use of a Filter, but the Campaign can also be restricted through the use of other items, such as Exclusions Lists and De-duping Logic. Note: If you assign an "empty" Filter (that is, a Filter that doesn't have any logic criteria within it) to a Campaign, the Campaign will deploy to all recipients in the Campaign's source table. In most cases, this isn't desired. The system will display a warning messages if the Filter is "empty," but you should also always check that you've assigned the correct Filter to the Campaign, AND check the Filter logic to make sure it's selecting the desired recipients.
Note: If you search for and select a Filter that has a different source table than the current Campaign, the system will display an error message at the top of the Campaign screen.
For more information on setting up Filters, see the Filters topic.
|
A Seed List is a group of one or more individuals who are designated to receive a duplicate copy of a Campaign message. When the Campaign is deployed, the system will automatically send the Campaign message to each recipient in the Seed List, regardless of whether those individuals are selected by the Campaign's main audience Filter. The use of Seed Lists in a Campaign is optional. Note: Seed Lists are used only for Date-triggered Campaigns and Regular One-off Campaigns. If you use a Seed List in a Campaign that has an hourly Send Limit, the platform treats the Seed List separately. The Seed List messages will get sent in the first hour, but these Seed List messages do not count toward the hourly Send Limit. For example, let's say you have twenty recipients in your Seed List, and you configure your Campaign with an hourly Send Limit of 500 messages per hour. In the first hour after the Campaign is launched, the platform will send the first batch of 500 records AND the twenty Seed List messages. Then in the second hour, the platform will send the second batch of 500 records, and so on. Seed Lists can be built in one of two ways: either by manually entering one or more individuals, or by using a Filter to define logic that determines who should be included in the Seed List. Note: A Campaign can have only one Seed List assigned to it. Add a Seed ListTo add a Seed List:
For more information on setting up Seed Lists, see the Seed Lists topic. Use a Filter as a Seed ListTo define a Seed List by means of a Filter:
For more information on setting up Filters, see the Filters topic.
|
The primary purpose of an Alert Group is to notify a select group of individuals when some triggering event has occurred. That event could be any activity recorded by the platform, such as an email click or a Web Form submission. When the event takes place, the system sends an email message to the recipients included in the Alert Group. Note: Alert Groups are used only for Event-triggered Campaigns. Alert Groups should be assigned to their own dedicated Event-triggered Campaign whose sole purpose is to send the alert message, and not to any "live" marketing Campaign. If you want to send out messages to an Alert Group, you should create a separate Event-triggered Campaign within Messaging, define the triggering event, define the content of the alert message, and then assign the Alert Group. Please note that when you assign an Alert Group to a Campaign, the recipients in that Alert Group become the de facto Audience for that Campaign, overwriting any other Audience Filter selections you may have made. For this reason, you should keep your "alert" Campaign separate from your "marketing" Campaigns. To add an Alert Group to an Event-triggered Campaign:
For more information on setting up Alert Groups, see the Alert Groups topic.
|
An Exclusion List consists of individuals who should not be targeted in your marketing Campaign, such as individuals who work for competitors, for example. The Exclusion List automatically overrides all other criteria, including Filters, Seed Lists, and Proofing Groups. For example, if a specific individual is added to an Exclusion List, and that same person meets the Filter criteria used to defined the Campaign Audience, that person would not receive the Campaign message. Note: For Load and Send Campaigns, you're required to assign a Virtual Exclusion List to the Campaign, if you select a "promotional" Sender Profile (that is, a Sender Profile intended to be used for promotional marketing messages, rather than for operational messages like shipping notifications). When you launch the Load and Send Campaign, the system will verify that you've assigned at least one Virtual Exclusion List; if not, an error message is displayed. To add an Exclusion List to your Campaign:
For more information on setting up Exclusion Lists, see the Exclusion Lists topic. |
De-duplication (or "dedupe") refers to the process of identifying and removing duplicate records from your Campaign Audience, in order to ensure that recipients don't receive unwanted multiple copies of your message. Messaging allows you to select what field you want to use for identifying duplicate records, as well as the rules for picking the "winner" from amongst a set of duplicate records. De-duplication is conceptually similar to the "One Message Per ID" feature, but the dedupe feature allows you to define more complex logic, and you can dedupe on a field other than the Unique Identifier field. In most cases, if your Unique Identifier consists of only one field, you should use the De-Duplication Logic feature, which offers a few more options. If your Unique Identifier consists of multiple fields, you'll need to use the One Message Per ID feature instead To dedupe a Campaign:
Note: If you don't define a Filter and / or Sort option to select the "winner" from amongst a set of duplicate records, the system will sort the duplicate set by the Primary Key ID ("pk_id") field in descending order, then pick the top-most record. This default option will roughly approximate picking the "most recently added" record.
|
To set a hard limit on the total number of messages sent out in this Campaign:
|
Messaging allows you to limit the Campaign to send only one message to each unique recipient over the entire lifetime of the Campaign. The platform removes duplicates using the Unique Identifier. The Unique Identifier (also referred to as the "Alternate Key") is used to ensure that records in your table are created and updated properly. The Unique Identifier can be based on a single field, or on a combination of more than one field. The One Message Per ID feature is typically used for triggered Campaigns, where the same individual could theoretically qualify to receive a message more than once. Using this feature, the recipient will receive only one message from the Campaign. The One Message Per ID feature is conceptually similar to the De-Duplication Logic feature, but that feature allows you to dedupe on any one field, not just on the Unique Identifier, and to define the rules for how to pick the "winner" amongst a set of duplicate records. In most cases, if your Unique Identifier consists of only one field, you should use the De-Duplication Logic feature, which offers a few more options. If your Unique Identifier consists of multiple fields, you'll need to use the One Message Per ID feature instead. To restrict the Campaign to send out only one message per unique recipient:
|
Cheetah Messaging allows you to utilize custom stored procedures. These stored procedures must be defined and configured by your Cheetah Digital support team, which makes them available for selection when setting up your Campaign. To use a custom stored procedure in your Campaign:
|
A Sender Profile controls the "from" information from which your email message is sent, as well as the recipient's eligibility to be contacted. The Sender Profile sub-section allows you to select the desired Sender Profile for this Campaign.
For Campaigns that use a Messaging table as the data source, Sender Profiles can optionally be assigned a Classification (Promotional or Transactional). If this feature is enabled, the platform will automatically suppress any recipients unsubscribed from other Sender Profiles with the same Classification, on the same sending table. Please see the Sender Profiles topic for more details on this process. To select the Sender Profile for this Campaign:
Note: If you've enabled Sender Profile Classifications, and the selected Sender Profile has not been assigned a Classification, an error message is displayed. You must first assign a Classification to this Sender Profile before you can use it.
For more information on Sender Profiles, see the Sender Profiles topic. |
When setting up your Email Campaign, you may be required to select one or more "Preference" flags, depending on the configuration of your Sender Profile. A Preference is a special type of field in your database that's used to control whether or not a consumer has opted-in or opted-out of receiving email messages. Your database can optionally contain multiple Preference flags that allow your customers to manage their email subscriptions at an even more granular level. For example, let's say you deploy three main categories of email messages -- "transactional" email message (like Order Confirmations), promotional emails, and newsletters. You could set up Preference flags for each of these, allowing a consumer to opt-in or opt-out of any of those subscriptions. When you build a new Email Campaign, you would need to check the appropriate Preference flag. For example, if you were sending out a new promotion, you would want to check the "promotional" Preference flag, so that only consumers who have opted-in to those types of email messages would receive the promotion. Preference flags are defined in your database using a Data Type of "Preference." The determination of whether you MUST check a Preference flag is set by a system administrator at a Sender Profile level. Each Sender Profile can optionally be configured to require a Preference flag check. If you're using a Sender Profile that has this requirement in place, then the system will display a "Preferences" field within the "Sender Profile" section. The system will require you to select at least one Preference flag when you build the Campaign. Note: For more details on using Preferences to manage your recipient contact eligibility, please see Permission Management - Preferences. The system provides two methods for choosing a Preference flag (or flags). The first method is to manually select a Preference flag:
The second method is to have the system parse your selected Audience Filter for any Preference flags:
|
The Envelope sub-section allow you to define the header fields of the email message, and to assign other assets, such as reply handlers and attachments.
To enter the envelope information for your email messages:
|
The platform allows you to assign one or more Attachment files to an email message (up to a maximum total file size of five megabytes). To assign an Attachment to a Campaign:
For more information on setting up Attachments, see the Attachments topic. |
In some cases, recipients of an email message may attempt to respond to that message. The platform can be configured to perform an automated action with these responses. These automated actions are referred to as "Reply Handlers." The platform supports two different types of Reply Handlers -- Auto Reply Handlers and Forwarding Handlers. Auto Reply HandlersThe platform can be configured to submit an automated reply message back to the recipient. The message could contain, for example, instructions on how to contact your company, a thank you for their reply, or other information. To assign an Auto-Reply Handler profile to a Campaign:
For more information on setting up Auto Reply Handlers, see the Auto Reply Handlers topic. Forwarding HandlersThe platform can be configured to automatically forward the consumer's reply (without any images or attachments), along with a standard message and subject, to a specified person or group. For example, you could forward all consumer replies to a sales team, or a customer service representative, for follow-up. To assign a Forwarding Handler profile to a Campaign:
For more information on setting up Forwarding Handlers, see the Forwarding Handlers topic. |
Back to Configure an Email Campaign