Confirming the send confirming-the-send
Once you have finished preparing your messages and the approval steps have been carried out, you can send them. For more on messages preparation, refer to Preparing the send.
Only users with the Start deliveries role can confirm sending. For more on this, refer to the List of roles section.
Sending the message sending-message
Once preparation is complete, follow the steps below to send your message.
-
Click the Confirm send button found in the message鈥檚 action bar.
-
Finalize the send by clicking the OK button.
-
Wait while the message is being sent. The Deployment block shows the progress of the send.
If you are using a recurring delivery with no aggregation period, you can request confirmation before the delivery is sent. When configuring your message, open the Schedule block of the delivery dashboard and activate the dedicated option.
Understanding message indicators message-indicators
Once the message is sent to the contacts, the Deployment zone shows your KPIs (Key Performance Indicator) data, including:
-
The number of messages to deliver
-
The number of messages sent
-
The percentage of messages delivered
-
The percentage of bounces and errors
-
The percentage of open messages
-
The percentage of clicks in the messages (for emails)
note note NOTE The Open rate and Click-through rate are updated every hour.
If the KPIs take too long to update or do not reflect the results from the sending logs, click the Compute stats button in the Deployment window.
The message can be viewed in the history of one of the targeted profiles. See Integrated customer profile.
Once a message is sent, you can track the behavior of its recipients, and monitor it to measure its impact. For more on this, refer to these sections:
Delivery success reporting delivered-status-report
In the聽 Summary 聽view of each email,聽the聽 Delivered 听辫别谤肠别苍迟补驳别 starts out at 100% and then progressively goes聽down聽throughout the delivery validity period,聽as聽the soft and hard聽bounces get reported back.
Indeed, all messages show as聽 Sent 聽in the sending logs as soon as they are successfully relayed from Campaign to the Enhanced MTA (Message Transfer Agent). They remain in that status unless or until a bounce for that message is communicated back from the聽Enhanced MTA to Campaign.
When hard-bouncing聽messages get reported back from the Enhanced MTA, their status changes from Sent 迟辞听 Failed and the Delivered 听辫别谤肠别苍迟补驳别 is decreased accordingly.
When soft-bouncing聽messages get reported back from the Enhanced MTA, they still show as聽 Sent and the Delivered 听辫别谤肠别苍迟补驳别 is not yet updated. Soft-bouncing messages are then retried throughout the聽delivery validity period:
-
If a retry is successful before the end of the validity period, the message status remains as Sent and the Delivered 听辫别谤肠别苍迟补驳别 remains unchanged.
-
Otherwise, the status changes to Failed and the Delivered 听辫别谤肠别苍迟补驳别 is decreased accordingly.
Therefore, you must wait until the end of the validity period to see the final Delivered percentage, and the final number of Sent and Failed messages.
Email Feedback Service (beta) email-feedback-service
With the Email Feedback Service (EFS) capability, the status of each email is accurately reported, because feedback is captured directly from the Enhanced MTA (Message Transfer Agent).
Once the delivery has started, there is no change in the Delivered 听辫别谤肠别苍迟补驳别 when the message is successfully relayed from Campaign to the Enhanced MTA.
The delivery logs show the聽 Pending 聽status for each targeted address.
When the message delivery to the targeted profiles is reported back in real time from the Enhanced MTA, the delivery logs show the聽 Sent 聽status for each address that successfully received the message. The Delivered 听辫别谤肠别苍迟补驳别 is increased accordingly with each successful delivery.
When hard-bouncing聽messages get reported back from the Enhanced MTA, their log status changes from Pending 迟辞听 Failed and the Bounces + errors 听辫别谤肠别苍迟补驳别 is increased accordingly.
When soft-bouncing聽messages get reported back from the Enhanced MTA, their log status also changes from Pending to Failed and the Bounces + errors 听辫别谤肠别苍迟补驳别 is increased accordingly. The Delivered 听辫别谤肠别苍迟补驳别 remains unchanged. Soft-bouncing messages are then retried聽throughout the聽delivery validity period:
-
If a retry is successful before the end of the validity period, the message status changes to Sent and the Delivered 听辫别谤肠别苍迟补驳别 is increased accordingly.
-
Otherwise, the status remains as Failed. The Delivered and Bounces + errors 听辫别谤肠别苍迟补驳别s remain unchanged.
Changes introduced by EFS changes-introduced-by-efs
The tables below show the changes in KPIs and sending logs statuses introduced by the EFS capability.
With Email Feedback Service
- Delivered 听辫别谤肠别苍迟补驳别 starts out at 0%
- Bounces + errors 听辫别谤肠别苍迟补驳别 starts out at 0%
- No change in Delivered 听辫别谤肠别苍迟补驳别
- Bounces + errors 听辫别谤肠别苍迟补驳别 is increased accordingly
- No change in Delivered 听辫别谤肠别苍迟补驳别
- Bounces + errors 听辫别谤肠别苍迟补驳别 is increased accordingly
- Delivered 听辫别谤肠别苍迟补驳别 is increased accordingly
- Bounces + errors 听辫别谤肠别苍迟补驳别 is decreased accordingly
- No change in Delivered 听辫别谤肠别苍迟补驳别
- No change in Bounces + errors 听辫别谤肠别苍迟补驳别
Without Email Feedback Service
- Delivered percentage starts out at 100%
- Bounces + errors percentage starts out at 0%
- Delivered 听辫别谤肠别苍迟补驳别 is decreased accordingly
- Bounces + errors 听辫别谤肠别苍迟补驳别 is increased accordingly
- No change in Delivered 听辫别谤肠别苍迟补驳别
- No change in Bounces + errors 听辫别谤肠别苍迟补驳别
- No change in Delivered 听辫别谤肠别苍迟补驳别
- No change in Bounces + errors 听辫别谤肠别苍迟补驳别
- Delivered 听辫别谤肠别苍迟补驳别 is decreased accordingly
- Bounces + errors 听辫别谤肠别苍迟补驳别 is increased accordingly