Email Deliverability

Email deliverability is extremely dynamic and can vary from one outgoing email to another.  Because of this, there is no way to guarantee email deliverability. When sending out a bulk of emails in this context, we do not have a limit to the number of emails that can be sent at one time. However, note that:

• Alida is responsible for ensuring that its email infrastructure is in accordance with the email industry’s best practices.  This includes hosting communities on their own dedicated IPs and ensuring that we support domain authentication, such as DKIM and SPF.
• From a technology viewpoint, no vendor or market research company can guarantee inbox deliverability because this is solely based on the client's mailing practices.

Examples of how clients influence their own delivery results: 

• If clients upload old lists as external sample imports, this will probably result in delivery issues as old lists typically have invalid email addresses; mailing to these types of addresses is viewed as spammy behavior by ISPs.  
• Old lists also typically have subscribers who may have forgotten that they subscribed to messages from the client, which would therefore likely result in high abuse complaints ("mark as spam"), which would then push subsequent messages to the Junk folder or get the client blocked.
• If a client uses poorly designed message templates or is mailing to their subscribers too frequently, this could also result in high abuse complaints, which could also get them blocked.

That said, we have also developed a number of Knowledge Base articles specifically related to email deliverability and how to keep it optimal. There are many factors that you can control, from picking good subject lines, to designing good content, to ensuring the list that is being emailed is clean, up-to-date, and free of invalid email addresses.

Additionally, our IT team is monitoring overall email deliverability for our clients. If deliverability levels suddenly drop substantially, the incident is reviewed and corrective actions are taken if necessary. Sometimes these actions will be coordinated by an Account Representative or the Technical Support team in order to review the best practices that we have developed.