Deliverability allows to measure the success of your campaigns reaching your recipients' inbox without bouncing, or being marked as spam.
The deliverability rate depends on numerous factors, particularly:
- Correct configuration of your instances
- Your IP address reputation
- Quality of the addresses targeted
- Low complaints and hard bounce rates
- Your message content
- Message authentication (SPF, DKIM, DMARC)
- Sender reputation
Key points to check
To optimize the deliverability of your Adobe Campaign emails, we recommend using the best practices listed below. Deliverability problems are generally linked to measures of protection against spam implemented by internet service providers and mail server administrators.
Email deliverability refers to the set of characteristics that determine a message's ability to reach its destination, via a personal e-mail address, within a short time,and with the expected quality in terms of content and format. These characteristics fall into four main categories: data quality, message and content, sending infrastructure, and reputation. Together, they form the foundation of a successful email deliverability program.
The deliverability rate is the number of sent emails that were successfully delivered to its recipients. Here is a list of the key points to check to ensure good deliverability.
First, start by consulting the documentation on the deliverability tools provided with Campaign Standard:
Checking network configuration
Spammers try to conceal their real identity and as a consequence make their servers difficult to identify. A legitimate network configuration that does not try to hide the identity of the server is essential to sending emails in large volumes.
Sending to valid addresses
Spammers often use address generators based on lists of frequent names and first names; in addition, they rarely process technical notifications sent back by mail servers. A high rate of invalid addresses is often interpreted as a sign of spam. Double opt-in mechanisms and effective handling of technical bounce messages make it possible to avoid this.
Reducing complaint rate
ISPs usually have a prominent means of reporting a received message as spam. This makes it possible to identify unreliable sources. By rapidly honoring opt-out requests, making regular use of a given list, verifying consent through a double opt-in system, and implementing feedback loops, you can reduce complaint rates.
Sending to honeypot addresses
ISPs and other organizations (refer to https://www.projecthoneypot.org/) make use of mailboxes that do not correspond to physical persons but are created simply to trick spammers. These so-called "honey pot" addresses are published on the Web in order to be collected by spambots and thus catch illegitimate senders. The use of a double opt-in mechanism precludes this sort of address being added to a list. When using a third-party list, you must be sure of the methods employed by its maintainer.
Adapting message content
To a lesser degree, the content of certain messages can lead certain filters to detect it as spam. The use of certain words, the use of exclamation points in the subject line and within the messages are read as tell-tale signs of spam. Spammers are also known to replace text with images to stop offending text from being analyzed automatically by anti-spam filters. In response to this, a message (in HTML format) with a high proportion of images, or images as attachments, may end up being blocked.
Sending on a regular basis
Spammers make programmed deliveries to maintain their reputation over time. They sometimes need to adapt their marketing plan to meet the best practices imposed by the ISPs and so, after a peak in reputation (ramp-up), they configure regular deliveries.