Reliable tracking of opt-outs and hard-bounces

[Compuware]

Need a repeatable & reliable way to capture all opt-outs and hard-bounces. There is currently no clear filter critieria that can be used to identify those who previously may have bounced or opted-out vs. those that are currently opted-out and hard-bounced outside of exporting the bounces and unsubscribes data from the Email section to create a Static List which is not substainable. There should be a way to pull this into a smart list and/or a contact setting that can be referenced. Would like to know when sending my email I have the cleanest list possible prior to hitting send.

[#2]

@Compuware

You can create a smart list of bounced contacts. While it doesn't differentiate between soft and hard bounces, it may work for your needs. When creating a list, select the contact property filter and chose emails bounced is known.

Also, Hubspot automatically excludes contacts previously hard bounced when sending emails. 

[#3]

Thanks for the info we currently have a smart list filtering with the knowns. However, it is becoming a big unmanageable due to hard bounces that we have unbounced so now rather than known is has to filter for those that were previously known but now are labeled with "1" or "2", etc. Same applies with opt-outs. While they were previously "known" and opt back in they're opt-out field like the bounce field now has another value.

[#4]

@ndwilliams3 While it's useful Hubspot doesn't send to hard bounced, it would also be useful to have visibility over them when building lists (for example if a list has 6000 contacts but 3000 of them hard bounced) - before sending emails. Is this possible somehow? (same for opt-outs)

[#5]

We definitely need better tracking of hard bounces. Our sales people use Salesforce and we sync all of our data, but there is no Hubspot field we can use to tag contacts as BOUNCED in Salesforce so our sales people know which of their contacts may not be receiving our messages. We've currently tried sending bounce reports out to them, but the server messages can be confusing unless you know what you're looking at. And, like someone else mentioned above, the "Bounced Emails" field can't reliably be used because it doesn't reset when contacts are unbounced.

[#6]

It would be great if there was an easy way to build a smart list of only contacts who have hard-bounced and are not eligible to recieve email. Currently, it doesn't look like there is a way to use list filters to create such a list.

My company just started using SalesForce and half of the information they imported is junk. It would be very beneficial if I could supply a list of hard-bounced email addresses back to SalesForce administrators to help them clean up the mess and on the flip receive much cleaner lists to do campaigns with from them in the beginning.

[#7]

Completely agree.  With HubSpot using a pay-per-lead model, it's really frustrating to find that there isn't a robust system for handing hard-bounces.

We manage a pretty popular marketing blog with tons of content and get a fair share of "no@no.com" emails which, because there's no automated way to handle these fake contacts, we pay for montly.

Please fix this HubSpot.  This solution doesn't scale.

[#8]

Copied from a similar topic:

Completely agree.  With HubSpot using a pay-per-lead model, it's really frustrating to find that there isn't a robust system for handing hard-bounces.

We manage a pretty popular marketing blog with tons of content and get a fair share of "no@no.com" emails which, because there's no automated way to handle these fake contacts, we pay for them montly.

Please fix this HubSpot.  This solution doesn't scale.

[#9]

 Totally agree we need this

[#10]

Hi @spanishgringo, @kbento : I am just commenting to let you know that I have merged the previous idea that you had commented on ("New HubSpot property for contacts that have hard-bounced?") with this current idea, which was posted before and had more votes. This was done in order to increase the idea's visibility, and thus make its implementation more likely. Please add any additional information that you might find useful in the comments!

[#11]

I found this article on a workaround - but it really should just be a property we can use to filter smart lists!

https://knowledge.hubspot.com/articles/kcs_article/email/how-do-i-create-a-list-of-bounced-email-add...

[#12]

Thanks. I noted this article as well and while we have done this process in the past it's manual. We should not have to export and then reimport prior to every mailing we do. I also find it interesting that we have to "validate" upon import that these people are Email Opt-In.

[#13]

Hi folks, our public API is one way to get this information: https://developers.hubspot.com/docs/methods/email/get_status

if ...

"bounced":true,<code></code>

then the contact is hard bounced.

Until there is a better solution it is important to know the "Emails Bounced" property is not a representation of currently ineligible contacts (contacts in 'Not Sent') for a multitude of reasons:
* The Emails Bounced property will not increment for global bounces. However, we will put the contact in the Not Sent category if it is globally bounced. An email becomes globally bounced if we received a permanent error when emailing that address in the past. Permanent errors in this case are bounce messages that indicate if an inbox has been disabled, or if there is a typo in the address).
* The Emails Bounced property will increment for soft bounces. They increment the Emails Bounced property but they will not put a contact in the Not Sent category.
* The Emails Bounced property will not reset to 0 if a contact's email address is updated, however, we will attempt to send to that contact again if the contact's email address is updated.

* The Emails Bounced property will not reset to zero if the contact is unbounced, by Support, or in-app.
* We put contacts in the Not Sent category without ever sending them an email if there is no MX record set up at their domain. The lack of an MX record shows that the domain can not send or receive email, and therefore we do not have to attempt to send the email to know that it will not deliver. These contacts will end up in Not Sent but their Emails Bounced will be 0.

Use this workaround for creating a list of ineligible (hard bounced) contacts if the using the API is not an option:
https://knowledge.hubspot.com/articles/kcs_article/email/how-do-i-create-a-list-of-bounced-email-add...

[#14]

The most automatic, despite being technically difficult, way to get this information is by using the Email Events API to GET the status of an email address: http://developers.hubspot.com/docs/methods/email/get_status

If the bounced parameter is true, the contact is hard bounced.

The Emails Bounced property is not a representation of currently ineligible contacts (contacts in 'Not Sent') for a multitude of reasons:

• The Emails Bounced property will not increment for global bounces. However, we will put the contact in the Not Sent category if it is globally bounced.
• The Emails Bounced property will increment for soft bounces, but soft bounces will not put a contact in the Not Sent category.
• The Emails Bounced property will not reset to 0 if a contact's email address is updated, however, we will attempt to send to that contact again if the contact's email address is updated.
• The Emails Bounced property will not reset to 0 if a contact's email address is unbounced, either by Support or in-app.
• We put contacts in the Not Sent category without ever sending them an email if there is no MX record set up at their domain. The lack of an MX record shows that the domain can not send or receive email, and therefore we do not have to attempt to send the email to know that it will not deliver. These contacts will end up in Not Sent but their Emails Bounced will be 0.

Use this workaround for creating a list of ineligible (hard bounced) contacts if you can not use the API:

https://knowledge.hubspot.com/articles/kcs_article/email/how-do-i-create-a-list-of-bounced-email-add...

[#15]

Agree 100% with Compuware.

We also need a way to build smart lists in Hubspot for those who are flagged as hard bounced/global bounced, ideally from a Contact Property. For a variety of reasons. Reps in Salesforce need to see who's bounced. It would help us suppress people from workflows. It would help us flag and suppress people in SF from call campaigns.

Manually exporting/importing is an unacceptable workaround for us due to the additional overhead that places on our team to keep a bounced-list up to date, and we don't have the bandwidth for developing a solution that uses the API.

And also fully agree on Compuware's note about forcing us to validate people are opt-in when we are just trying to add a list of contacts that already exist in HS to a static list. A function that builds a list based on a csv file of emails-only, matching against emails already in SF, would be extremely useful for static-list management.

Coming from Mailchimp, I'm used to having access to both these types of features, which made our lives easier for list management.

[#16]

 Totally agree we need this II

[#17]

Completely agree that we need a reliable way to track bounced emails. We need this as a field under a contact so we can get this information over to SalesForce. I know HubSpot already has a field under the contact record called "Emails Bounced" but this is a historical field - so if an email is bounced and then we unbounce the email, this field will not reset. We try to segregate our lists the best we can by eliminating unsubscribes, etc but the manually process of exporting bounces does not work for us.

[#18]

Hi Everyone - Prior to HubSpot, we used Marketo, and Marketo had a flag for global bounces.  I don't understand why HubSpot cannot create this flag as a property for us to use in other places (for example, in smart lists, and/or as a field that can be imported into other systems).  We use SalesForce.com as our CRM, and we'd like the fact that a record has globally bounced in HubSpot to appear somewhere on that record in SalesForce.com.

We don't think this an unreasonable request, and here's why: 

• Some piece of code in HubSpot’s program triggers the status on a record to change to Contact has bounced globally (see this screenshot to see the HubSpot field I'm referencing - https://www.screencast.com/t/8R8LN8Hq ). 
• That same code should be able to trigger a property in HubSpot that we can use on smart lists, and it should be able to trigger a message to change a field in SFDC (for example, a custom field like “Email invalid in HubSpot”).

 I agree that it's very frustrating to find that HubSpot has no way to automatically manage global bounces, especially when other less sophisticated systems (like Marketo) do. 

[#19]

Wow. We are migrating from Pardot and I'm surprised at this feature doesnt come out-of-the-box in hubspot.

It's going to be a problem if we need to use APIs to know who is what (w.r.to hard bounce vs. unsubscribe status). Knowing who has opted out vs. who is bouncing is crucial for undertaking appropriate actions. This must be a high priority item.

[#20]

 This seems like such a basic thing to have inside a system. I can't believe I'm being referred here to comment and agree and upvote this.