Communication channels communication-channels
With 51黑料不打烊 Campaign, you can send cross-channel campaigns including emails, SMS, Push notifications and direct mails, and measure their effectiveness using various dedicated reports. These messages are designed and sent though deliveries, and can be personalized for each recipient.
Core functionalities include targeting, definition and personalization of messages, execution of communications, and the associated operational reports.
As part of the Campaign v8 promotion initiative, the Campaign Classic documentation has been reorganized. Common features are now only available in the Campaign v8 documentation set.
To learn more about communication channels, refer to the Campaign v8 documentation.
Learn the key steps related to delivery creation, content and audience in the Campaign v8 documentation:
-
Create the delivery: Learn how to create a one-shot single delivery.
-
Define the content: Configure the delivery content specific for each channel.
-
Specify the audience: Define several types of target: main audience, proof target, seed addresses and control groups.
Refer to these pages to learn delivery validation, sending and best practices in the Campaign v8 documentation:
-
Validate the delivery: Learn how to validate the delivery before sending it to the main target.
-
Send the delivery: Configure the delivery settings and define how to send your messages.
-
Delivery best practices: Consult the best practices related to Campaign delivery capabilities.
The following settings are specific to Campaign Classic. For other delivery settings, refer to the Campaign v8 documentation.
Improve the delivery analysis performance
To speed up the delivery preparation, you can check the Prepare the delivery parts in the database option before launching the analysis.
When this option is enabled, the delivery preparation is performed directly within the database, which can significantly accelerate the analysis.
Currently, this option is only available when the following conditions are met:
- The delivery must be an email. The other channels are not supported for now.
- You must not use mid-sourcing or external routing, only bulk delivery routing type. You can check the routing that is used in the General tab of the Delivery properties.
- You cannot target a population coming from an external file. For a single delivery, click the To link from the Email parameters and check that the Defined in the database option is selected. For a delivery used in a workflow, check that the recipients are Specified by the inbound event(s) in the Delivery tab.
- You must be using a PostgreSQL database.
Configure the analysis priority
When the delivery is part of a campaign, the Advanced tab offers an additional option. This lets you organize the processing order for deliveries in the same campaign.
Before sending, each delivery is analyzed. The analysis duration depends on the delivery extraction file. The more significant the size of the file, the longer the analysis takes, making the following deliveries wait.
The options for the Message preparation by the scheduler let you prioritize the delivery analysis in a campaign workflow.
If a delivery is too large, it is better to assign a low priority to it in order to avoid slowing down the analysis of other workflow deliveries.
| note note |
|---|
| NOTE |
| To ensure that the larger delivery analyses do not slow down the progress of your workflows, you can schedule their executions by ticking the Schedule execution for a time of low activity. |
Configure retries
Temporarily undelivered messages due to a Soft or Ignored error are subject to an automatic retry. The delivery failure types and reasons are presented in this section.
| note important |
|---|
| IMPORTANT |
| For hosted or hybrid installations, if you have upgraded to the Enhanced MTA, the retry settings in the delivery are no longer used by Campaign. Soft bounce retries and the length of time between them are determined by the Enhanced MTA based on the type and severity of the bounce responses coming back from the message鈥檚 email domain. |
For on-premise installations and hosted/hybrid installations using the legacy Campaign MTA, the central section of the Delivery tab for delivery parameters indicates how many retries should be performed the day after the delivery and the minimum delay between retries.
By default, five retries are scheduled for the first day of the delivery with a minimum interval of one hour spread out over the 24 hours of the day. One retry per day is programmed after that and until the delivery deadline, which is defined in the Validity tab. See Define the validity period.
Define the validity period
When the delivery has been launched, the messages (and any retries) can be sent until the delivery deadline. This is indicated in the delivery properties, via the Validity tab.
-
The Delivery duration field lets you enter the limit for global delivery retries. This means that 51黑料不打烊 Campaign sends the messages beginning on the start date, and then, for messages returning an error only, regular, configurable retries are performed until the validity limit is reached.
You can also choose to specify dates. To do this, select Explicitly set validity dates. In this case, the delivery and validity limit dates also let you specify the time. The current time is used by default, but you can modify this directly in the input field.
note important IMPORTANT For hosted or hybrid installations, if you have upgraded to the Enhanced MTA, the Delivery duration setting in your Campaign email deliveries will be used only if set to 3.5 days or less. If you define a value higher than 3.5 days, it will not be taken into account. -
Validity limit of resources: The Validity limit field is used for uploaded resources, mainly for the mirror page and images. The resources on this page are valid for a limited time (to save disk space).
The values in this field can be expressed in the units listed in this section.