When is it advisable to share a pooled IP address in Salesforce Marketing Cloud (SFMC)?

Email marketer from Email on Acid shares that using a shared IP can be a good option for companies with a low sending volume, or who don't want to manage their own dedicated IP address. It can save time and money, but your reputation can be impacted by other senders using that shared IP.

Email marketer from Quora explains that it can make sense to use a shared IP address when first starting out, as they may not have enough traffic yet to get a dedicated IP address. You can still build your email reputation while you warm up the IP and your domain and then move onto a dedicated IP when needed.

Email marketer from Litmus shares that if you send 50,000+ emails a month and you can follow email marketing best practices, you should use a dedicated IP. If you're not sending that many emails, you will benefit more from using a shared IP.

Email marketer from Validity shares their opinion on dedicated vs shared IPs, and it's mostly dependent on the company and the mailing strategy. If you are just starting or send emails irregularly, using shared IP addresses is the best choice. If you don't follow email best practices, you will suffer the consequences on either shared or dedicated IP addresses.

Email marketer from Reddit shares that using a shared IP can be beneficial for smaller senders who are just starting out or don't have the volume to maintain a dedicated IP's reputation. However, they caution that deliverability can be impacted by the sending practices of other users on the same IP pool.

Email marketer from Salesforce StackExchange responds that sharing a pooled IP is a good starting point, especially for new businesses or departments with low email volume. This avoids IP warming and allows senders to benefit from the IP's existing reputation. However, it is crucial to monitor deliverability and be prepared to move to a dedicated IP once the volume increases.

Email marketer from Email Geeks suggests starting on a shared IP to see if SFMC places the sender in a pool of good customers. If not, they recommend transitioning to a dedicated IP.

Email marketer from Email Geeks shares a past experience where they were required to either use an existing dedicated IP or start a new one for a new business unit, and were not allowed to use a shared IP. They advise staying away from SFMC shared IP pools due to typically poor quality.

Email marketer from SendGrid shares tips on how to warm an IP address. Using a shared IP address can help avoid this all together, but has some risks if other senders aren't following best practices.

Expert from Spam Resource explains that if other senders on the IP address are having deliverability issues, it can effect your deliverability. They explain that if you're using a reputable shared IP address this shouldn't be an issue.

Expert from Email Geeks explains that the policy was designed to prevent shared IP pools from becoming 'hot garbage' by preventing low quality mail from being sent on them. They talk about managing multi-tiered reputation based shared IP pools, including assigning clients based on engagement metrics and removing high-volume senders. They suspect that this system ceased after they left.

Expert from Email Geeks shares that shared IPs at SFMC can have issues due to the low reputation of other clients. They recommend sharing the existing dedicated IP instead of using the general SFMC shared pool. They suggest that sending more than 2.5 million emails a day is possible, depending on campaign speed. They also propose using two dedicated IPs shared between divisions as a safer alternative.

Expert from Email Geeks explains that you still need to warm up the domain on a shared IP, questioning the initial reason for considering it. They mention a client sending 20M/day per IP, suggesting adding the new division to the dedicated IP is viable. They also recommend considering a second dedicated IP for redundancy.

Expert from Word to the Wise explains that the choice between shared and dedicated IPs depends on factors such as sending volume, reputation management capabilities, and budget. If you have low sending volumes, limited resources for reputation monitoring, or are just starting, a shared IP is fine to start with.

Documentation from SparkPost explains that shared IP pools are suitable for transactional emails with good sending practices and low complaint rates. This reduces infrastructure costs and simplifies management. They emphasize the importance of monitoring reputation to maintain high deliverability.

Documentation from Mailjet answers the question about shared versus dedicated IPs. It explains the benefits of shared IPs and when to use them. If you are new to email marketing or have a smaller list, a shared IP can be a better option as you build your sending reputation. It also highlights the risk if others are sending poor mail on the same IP.

Documentation from Google shares the IP addresses for Google Workspace for the purpose of whitelisting. If you're getting mail from Google Workspace it's likely being sent via a shared IP address.

Documentation from Salesforce Help explains that sharing a pooled IP address in Marketing Cloud is advisable for new accounts or those with low sending volumes, as it avoids the need for IP warming and allows for leveraging the reputation of established IPs. It's suitable until sending volume justifies a dedicated IP.