Before sending the delivery, you can define the sending parameters in the delivery properties, via the Delivery tab.
Delivery priority: use this option to change the sending order for your deliveries by setting their priority level, from Very low to Very high (the default value being Normal).
Message batch quantity: use this option 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 created by duplicating an existing one, this parameter is reset.
Send using multiple waves: use this option to send your messages in batches rather than to your whole audience at once. Learn more.
Test SMTP delivery: use this option to test sending via SMTP. The delivery is processed up to connection to the SMTP server but is not sent: for every recipient of the delivery, Campaign connects to the SMTP provider server, executes the SMTP RCPT TO command, and closes the connection before the SMTP DATA command.
This option must not be set in mid-sourcing.
Learn more about SMTP server configuration in Campaign Classic v7 documentation.
Email BCC: use this option to store emails on an external system through BCC by simply adding a BCC email address to your message target. Learn more.
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 this section.
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.
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.
When the delivery is configured and ready to be sent, make sure you have run the delivery analysis before confirming the sending.
To do this, follow the steps below.
Click Send, select the desired action.
Click Analyze. For more on this, see this section.
Once done, click Confirm delivery to launch the delivery of messages.
You can 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.
For more on this, refer to the sections below:
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.
Start the delivery analysis and confirm the delivery sending. However, the delivery sending will not start until the date given 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 the 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: