The Audience sub-section is used to identify to whom you're sending your Campaign message. The platform offers several different options to both select and restrict your Campaign Audience.
The features and options available from the Audience sub-section are described below.
The options for defining the Campaign Audience are described below:
Select the Campaign Audience Audiences are defined using a Filter, which can often (depending on the channel) be restricted through the use of other Items, such as Exclusions Lists, De-duping Logic, etc. For more information on setting up Filters, see the Filters topic. For Regular One-off and Date-triggered Campaigns, the system requires you to select a Filter. 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. For an Event-triggered Campaign, you don't have to select a Filter, as the event itself defines who the recipients are; the default Audience for an Event-triggered Campaign is "all triggered records." Optionally, however, you can select a Filter if you need to apply additional restrictions to identify and select only a sub-set of the triggered records. For an Event-triggered Campaign:
For all Campaign types:
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.
|
Add a Seed List 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 part of the Campaign audience. The use of Seed Lists in a Campaign is optional. Note: Seed Lists are used only for Date-triggered and Regular One-off Campaigns. Currently, the user interface allows you to assign a Seed List to an Event-triggered Campaign, but the system will not actually send email messages to the Seed List recipients when the Event-triggered Campaign is deployed. For most channels, 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. Add a Seed ListTo use 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.
|
Add an Alert Group 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 a message via Email, SMS Text, or Push Notification to the recipients included in the Alert Group. 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. Note: 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. |
The options for restricting the Campaign Audience are described below:
De-duplicate Recipients De-duplication (or "dedupe") refers to the process of identifying and removing duplicate records from your Campaign Audience, in order to ensure that consumers don't receive unwanted multiple copies of your message. The De-Duplication Logic feature allows you to select what field you want to use for identifying duplicate records, as well as the rules for picking the "winner" among a set of duplicate records. The De-duplication Logic feature is conceptually similar to the "One Message Per ID" feature, but the De-duplication Logic feature allows you to define more complex logic, and you can dedupe on a field other than the Unique Identifier. 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 enable the De-duplication Logic feature:
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.
|
Define Total Number of Messages To set a hard limit on the total number of messages sent out in this Campaign:
|
Send One Message per ID 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 consumer:
|
Add a Special Processing Step 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:
|
Back to Configure a Print Campaign