Do you need a dedicated IP to send emails with systeme.io?

This article explains how email deliverability is managed in systeme.io. It details the function of IP reputation, the differences between shared and dedicated IPs, and the mechanics of our IP pool system.

1. Introduction to IP reputation

IP reputation is a score that Internet Service Providers (ISPs), such as Gmail and Outlook, assign to an IP address based on its historical sending behavior. This score is a primary factor in determining whether emails are delivered to the inbox, sent to the spam folder, or blocked entirely.

• A high reputation score
• A low reputation score

Maintaining a high IP reputation is essential for achieving optimal email deliverability.

2. Shared vs. dedicated IP addresses

There are two types of IP addresses used for sending emails:

• Dedicated IP: An IP address used exclusively by a single sender. The sender is solely responsible for building and maintaining its reputation from zero.
• Shared IP: An IP address used by multiple senders. By default, systeme.io sends user emails through a managed system of shared IP addresses. We actively monitor and manage the reputation of these shared IPs to ensure high deliverability for the entire user community.

For most users, our managed shared IP infrastructure is the optimal solution for deliverability, as it leverages a pre-established, positive reputation.

3. The systeme.io pools system

To manage sender reputation and protect deliverability for all users, systeme.io utilizes an automated pool system. This system categorizes senders into one of five pools based on their email performance metrics.

Pool descriptions:

• New user pool: The default starting pool for all new accounts. This allows senders to establish an initial sending history.
• Low risk pool: Contains senders with excellent email statistics and consistently high deliverability.
• Moderate risk pool: For senders with average but acceptable performance statistics.
• High risk pool: Contains senders with poor statistics. This isolates them to prevent negative impacts on other pools.
• Quarantine pool: A temporary pool for high-risk senders whose activity could harm the network's overall reputation.

This segmentation ensures that responsible senders benefit from a high-reputation environment, while senders with poor practices are isolated until they improve again.

4. Pool assignment metrics

A sender's placement within the IP Pool System is determined by three key performance metrics: Open rate, Spam rate, and Bounce rate.

The specific thresholds for each pool are as follows:

5. Rules for pool reassignment

The system automatically evaluates and updates sender pool assignments daily based on the following criteria:

• A sender must reside in a pool for a minimum of 14 days before being eligible for reassignment.

  A sender must send a minimum volume of emails for their statistics to be evaluated for a pool change. The required volumes are:

  • New user → 500 emails
  • Low risk → 5000 emails
  • Moderate risk → 5000 emails
  • High risk → 5000 emails
  • Quarantine → 1000 emails

These rules ensure that pool assignments are based on consistent, long-term sending patterns rather than short-term fluctuations.

6. Using a dedicated IP (advanced)

For users who require a dedicated IP address, systeme.io offers the ability to integrate a personal SendGrid account. This will route all emails sent from your systeme.io account through your designated SendGrid IP.

To learn how to integrate your SendGrid account with systeme.io, click here to read the full guide.

7. Conclusion

Email deliverability is directly correlated with sending practices. The systeme.io pools system is designed to reward senders who maintain clean lists and achieve high recipient engagement. By adhering to email marketing best practices, users can improve their pool assignment and, consequently, their email deliverability.