Only the delivery owner can start a delivery. In order for another operator (or operator group) to be able to start a delivery, you have to add them as reviewers in the Delivery start: field.
Refer to this section for further information.
Before sending the delivery, you can define the sending parameters in the delivery properties, via the Delivery tab.
Delivery priority: This option allows you to influence the sending order for your deliveries by stating their priority level (normal, high or low). This lets you prioritize the order for certain, more urgent deliveries over others.
Message batch quantity: This option allows you to define the number of messages grouped within the same XML delivery package. If the parameter is set to 0, the messages are automatically grouped. The package size is defined by the calculation
<delivery size>/1024, with a minimum of 8 and a maximum of 256 messages by package.
When the delivery is duplicated, the parameter is reset.
Send using multiple waves: For more on this refer to Sending using multiple waves.
Test SMTP delivery: This option allows you to test sending a delivery via SMTP. The delivery is processed up to connection to the SMTP server but is not sent.
Using this option is not advised when installing using mid-sourcing as to not call mta.
For more information on configuring an SMTP server, refer to this section.
Email BCC: This option lets you store emails on an external system through BCC by simply adding a BCC email address to your message target. For more on this, refer to this section.
Once the delivery is configured and ready to be sent, make sure you have run the Delivery analysis. Once done, click Confirm delivery to launch the delivery of messages.
You can then close the delivery wizard and track the execution of the delivery from the Delivery tab, accessible via the detail of this delivery or via the list of deliveries.
After sending messages, you can monitor and track your deliveries. For more on this, refer to these sections:
You can defer the delivery of messages in order to schedule the delivery or to manage sales pressure and avoid over-soliciting a population.
Click the Send button and select the Postpone delivery option.
Specify a start date in the Contact date field.
Once you have started the analysis, the contact date that you defined is fixed. If you modify this date, you will have to restart the analysis so that your modifications are taken into account.
In the delivery list, the delivery will appear with Pending status.
Scheduling can also be configured upstream via the Scheduling button of the delivery.
It lets you defer the delivery to a later date or save the delivery in the provisional calendar.
The Schedule delivery (no automatic execution) option lets you schedule a provisional analysis of the delivery.
When this configuration is saved, the delivery changes to Targeting pending status. The analysis will be launched on the specified date.
The Schedule delivery (automatic execution on planned date) option lets you specify the delivery date.
Click Send and select Postpone delivery then launch the analysis and confirm delivery. When the analysis is complete, the delivery target is ready and messages will automatically be sent on the specified date.
Dates and times are expressed in the time zone of the current operator. The Time zone drop-down list located below the contact date input field lets you automatically convert the entered date and time into the selected time zone.
For instance, if you schedule a delivery to be executed automatically at 8 o’clock London time, the time is automatically converted into the selected time zone:
To balance the load, you can divide deliveries into several batches. Configure the number of batches and their proportion with respect to the entire delivery.
You can only define the size and the delay between two consecutive waves. The recipient selection criteria for each wave cannot be configured.
Open the delivery properties window and click the Delivery tab.
Select the Send using multiple waves option and click the Define waves… link.
To configure waves, you can either:
Define the size for each wave. For example, if you enter 30% in the corresponding field, each wave will represent 30% of the messages included in the delivery, except the last one, which will represent 10% of the messages.
In the Period field, specify the delay between the start of two consecutive waves. For example, if you enter 2d, the first wave will start immediately, the second wave will start in two days, the third wave in four days, and so on.
Define a calendar for sending each wave.
In the Start column, specify the delay between the start of two consecutive waves. In the Size column, enter a fixed number or a percentage.
In the example below, the first wave represents 25% of the total number of messages included in the delivery and will start immediately. The next two waves complete the delivery and are set to begin at six-hour intervals.
A specific typology rule, Wave scheduling check, ensures that the last wave is planned before the delivery validity limit. Campaign typologies and their rules, configured in the Typology tab of the delivery properties, are presented in Validation process with typologies.
Make sure the last waves do not exceed the delivery deadline, which is defined in the Validity tab. Otherwise some messages might not be sent.
You must also allow enough time for retries when configuring the last waves. See this section.
To monitor your sends, go to the delivery logs. See this page.
You can see the deliveries that were already sent in the processed waves (Sent status) and the deliveries to be sent in the remaining waves (Pending status).
The two examples below are the most common use cases for using multiple waves.
During ramp-up process
When emails are sent using a new platform, Internet service providers (ISPs) are suspicious of IP addresses that are not recognized. If large volumes of emails are suddenly sent, the ISPs often mark them as spam.
To avoid being marked as spam, you can progressively increase the volume sent using waves. This should ensure smooth development of the start-up phase and enable you to reduce the overall rate of invalid addresses.
To do so, use the Schedule waves according to a calendar option. For example, set the first wave to 10%, the second to 15%, and so on.
Campaigns involving a call center
When managing a telephone loyalty campaign, your organization has a limited capacity to process the number of calls to contact subscribers.
Using waves, you can restrict the number of messages to 20 per day, which is the daily processing capacity of a call center.
To do this, select the Schedule multiple waves of the same size option. Enter 20 as the wave’s size and 1d in the Period field.
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.
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 Defining validity period).
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’s email domain.
All impacts are detailed in the Adobe Campaign Enhanced MTA document.
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 Adobe 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.
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.
For hosted or hybrid installations, if you have upgraded to the Enhanced MTA, the Delivery duration setting in your Campaign 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.
All impacts are detailed in the Adobe Campaign Enhanced MTA document.