Tech Team Won't Allow Connection of Email Sending Domain to "Protect Mail"

[CMarketing23]

Is there any hard data about the risk-reward of connecting your email sending domain to HubSpot? I have a tech team that is a roadblock here. I understand that in doing so (reward) removes the 'via HubSpot' text that appears in the sender information at the top of your marketing emails and helps reduce the chances of it being marked as spam. But what could be all the potential downsides? Perhaps I need a better understanding of their concerns, one of which may be using a HubSpot shared IP, but getting a dedicated IP is not really an option - not sending a large amount of email. The sales team is also already using connected inboxes with that same email domain (via HubSpot CRM). 

Their reason: they think they are protecting their email health by not making the connection. What am I missing here? Has anyone else dealt with this? Does anyone have any convincing advice, facts or info? Really appreciate the help.

[EmmaAtKiwi · Accepted solution]

Hey @CMarketing23! Another reward of connecting your email sending domain is that the connection not only removes the "via HubSpot," it also updates the "signed by" to YOUR company instead of HubSpot as you can see in the "unconnected" vs. "connected" examples below:

Your team's concerns are valid, BUT your HubSpot account is already on a shared server regardless of whether you connect the email sending domain! All of us small to midsize guys are sharing servers, which is why you'll end up in HubSpot jail (suspended account) if your emails get a ton of unsubbs/bounces/spam reports - because bad behavior affects all of us on that server! Connecting your email sending domain actually REDUCES the likelihood of your marketing emails ending up in your contact's spam folders.

[CMarketing23]

Yes, I agree with all of this. It seems like the risk of not connecting is worse than connecting. And the sales team is already using the same email domain with their connected inbox so...