When the delivery is configured and ready to be sent, make sure you have run the delivery analysis. Learn more
Once done, confirm the delivery to launch the delivery of messages.
Track the execution of the delivery from the Delivery tab, accessible via the detail of this delivery or via the list of deliveries.
Once sent, check your delivery status in the Delivery Dashboard and access delivery logs and reports to confirm messages were correctly sent.
Campaign v8 Mail Transfer Agent (MTA) provides a best-in-class sending infrastructure allowing for optimal deliverability, reputation, throughput, reporting, bounce handling, IP ramp up and connection setting management.
Available for all Campaign v8 customers, it guarantees scalability, a high delivery throughput and helps send more emails faster. This is achieved with new adaptive delivery techniques that alter email sending settings in real-time based on feedback from Internet Service Providers.
Adobe Campaign uses a Mail Transfer Agent (MTA) which runs SparkPost’s commercial email MTA called Momentum.
Momentum represents innovative, high-performance MTA technology which includes smarter bounce handling and an automated deliverability optimization capability that helps senders achieve and maintain optimal inbox delivery rates.
For synchronous delivery failure error messages, the MTA determines the bounce type and qualification, and sends back that information to Campaign.
The MTA qualifies the SMTP bounce and sends that qualification back to Campaign in the form of a bounce code mapped to a Campaign bounce reason and qualification.
Currently asynchronous bounces are qualified by the inMail process through the Inbound email rules.
Learn more on delivery failures in this section.
MX rules (Mail eXchanger) are the rules that manage communication between a sending server and a receiving server.
The MTA has its own MX rules that allow it to customize your throughput by domain based on your own historical email reputation, and on the real-time feedback coming from the domains where you’re sending emails.
Domain Keys Identified Mail (DKIM) is an authentication method that is used to detect forged sender addresses (commonly called spoofing).
In Adobe Campaign, DKIM email authentication signing is performed by the MTA.
Lern more on DKIM in the Adobe Deliverability Best Practice Guide.
With the Email Feedback Service (EFS) capability, the status of each email is accurately reported, because feedback is captured directly from the MTA.
Once the delivery has started, there is no change in the Success percentage when the message is successfully relayed from Campaign to the MTA.
The delivery logs show the Taken into account by the service provider status for each targeted address.
When the message is actually delivered to the targeted profiles and once this information is reported back in real time from the MTA, the delivery logs show the Sent status for each address that successfully received the message. The Success percentage is increased accordingly with each successful delivery.
When hard-bouncing messages get reported back from the MTA, their log status changes from Taken into account by the service provider to Failed.
When soft-bouncing messages get reported back from the MTA, their log status remains unchanged (Taken into account by the service provider): only the error reason is updated. The Success percentage 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 Success percentage is increased accordingly.
Otherwise, the status changes to Failed. The Success percentage remains unchanged.
The table below shows how the KPIs and sending logs statuses are updated at each step of the sending process with the EFS capability.
|Step in the sending process||KPI summary||Sending logs status|
|Message is successfully relayed from Campaign to the MTA||Success percentage is not displayed (starts out at 0%)||Taken into account by the service provider|
|Hard-bouncing messages get reported back from the MTA||No change in Success percentage||Failed|
|Soft-bouncing messages get reported back from the MTA||No change in Success percentage||Taken into account by the service provider|
|Soft-bouncing messages retries are successful||Success percentage is increased accordingly||Sent|
|Soft-bouncing messages retries fail||No change in Success percentage||Failed|