What are the deliverability risks of setting up a sender domain on a different ESP?

Email marketer from Litmus explains that if the email list used on the previous ESP is not properly cleaned (removing invalid addresses, unsubscribed users, and unengaged recipients) before being transferred to the new ESP, it can lead to high bounce rates and spam complaints, harming deliverability.

Email marketer from Neil Patel Blog explains that using a new ESP often means using new IPs. It's crucial to warm up these IPs by gradually increasing sending volume to establish a positive reputation with ISPs. Failing to do so can lead to deliverability issues.

Email marketer from Glockapps explains that always monitor deliverability to different inboxes using a tool like Glockapps to measure the deliverability. This way if you spot issues you can respond and fix them.

Marketer from Email Geeks explains that sender reputations could affect each other if linking to the domain or using the same IP.

Email marketer from Sendinblue explains that improper or incomplete email authentication (SPF, DKIM, DMARC) setup on the new ESP can lead to deliverability problems. ISPs use these protocols to verify sender identity, and misconfiguration can flag emails as suspicious.

Email marketer from Email on Acid explains that if the custom tracking domain isn't correctly setup can cause issues and send you to spam. Using a general one might send you to spam as well.

Marketer from Email Geeks explains that if the main domain has a bad reputation, messages from a new domain mentioning or linking to it may cause problems.

Marketer from Email Geeks says that the key is to warm up the sub domain on the new IP pool.

Email marketer from Mailjet explains that a poor sender reputation, built up on a previous ESP due to bad sending practices (e.g., high bounce rates, spam complaints), can negatively impact deliverability when moving to a new ESP. ISPs might still associate the domain with negative history.

Email marketer from Reddit explains that using spam trigger words or phrases in email content can cause deliverability issues. Spam filters are sensitive to specific words and phrases often associated with spam.

Marketer from Email Geeks suggests using a subdomain of the original domain instead of a lookalike domain, as it could allow some reputation to transfer from the parent domain.

Email marketer from Gmass explains that make sure your lists are clean and up-to-date to ensure you are not sending to spam traps.

Email marketer from Validity explains that inconsistent sending practices between the old and new ESP can affect deliverability. Drastic changes in sending volume, frequency, or content can trigger spam filters.

Marketer from Email Geeks explains that using a cousin domain requires warming it up and avoiding bulk sending for at least 3 months. The existing sending reputation of both the main domain and the infrastructure also play a factor.

Expert from Email Geeks says that cousin domains are the devil.

Expert from Spamresource explains that moving to a new ESP requires building trust with the new IPs and domain reputation from scratch. This can cause deliverability issues in the short term if senders do not implement a warming strategy.

Expert from Word to the Wise explains that a lack of engagement after moving to a new ESP could cause deliverability issues. Senders should ensure their mail is relevant to their audience.

Expert from Spamresource explains that radically changing content when moving to a new ESP can trigger filters. Senders must ensure content remains recognizable and trusted by recipients.

Expert from Email Geeks mentions that domains registered recently (less than 6 months) are treated suspiciously by many filters.

Documentation from DMARC.org explains that a DMARC policy that is too strict (e.g., p=reject) without proper SPF and DKIM configuration on the new ESP can cause legitimate emails to be blocked. DMARC relies on SPF and DKIM for authentication.

Documentation from DKIM explains that not properly setting up DKIM signing with the new ESP's keys can prevent emails from being authenticated, increasing the likelihood of being marked as spam. The DKIM signature verifies the email's integrity.

Documentation from RFC explains that failing to update the SPF records to include the new ESP's sending IPs or domain can cause emails to fail SPF checks, leading to deliverability issues. The SPF record must accurately reflect all authorized sending sources.