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.
You can also stipulate the specific bounce categories you wish to populate the list and the timeframe where the bounce occurred. This should increase visibility into hard bounce data for HubSpot users trying to clean up their portals of hard bounced contacts.
Side note regarding unsubscribes, to create a smart list of all unsubscribed contacts use the property Unsubscribed from all email as Compuware suggested above.
This really needs to be a dynamic list. You are adding more work for us if we have to create this list everytime we want to exclude them from a list. If you create a field for hard bounces, we obviously can add that filter to a list.
I second this concept as well as making Hard Bounces and global opt-outs fields available in workflows. Having a dymanic lists for filtering or workflows for automation. The main reason to purchase HS Marketing is to avoid manual work.
It would also be nice to have a count of hard or soft bounces by date range to unsubscribe those that bounce more that X times within a given date range
As I previously mentioned. While the hard bounce field is available it is not reliable in instances where a person may have previously been noted as a hard bounced but then the email address verified and the hard bounce removed. The bounce field is not reset to "null" "blank." The bounce is removed so you can continue to email to, however the bounce field is still populated with a "1" or "2", etc. So you can't rely on this filter to accurately pull true hard bounces because in this instance you would be including the person you just removed the bounce from.
@Compuware is right again. The Emails bounced contact property has always been just that. A count of the number of emails that bounced to the email address. It increments each time a bounce occurs and does not decrement with the contact being unbounced. It also increments for soft bounces, which is another reason it should not be used to identify contacts for deletion. It was not designed to be a yes/no answer to the question is this contact currently eligible to be sent email.
A dynamic yes/no such as this was attempted years ago and it proved to be a disaster; frankly, it caused more confusion than it solved for. It was promptly rolled back. This most recent change allows users to see a static list of their hard bounced contacts (not including contacts that are unbounced) over a certain time frame. We will not be offering this as a dynamic property at this time due to the load it weighs on available bandwidth for our users.
So, @paxton since the option to show Bounced is really not a true bounced list, but a "quasi" bounced list of people that at one time or another for some reason or another may have bounced AND may or may not - no longer be bounced, but that can really be or not be valid contacts - list?
I find it simpler to think of the Emails Bounced property as a way to see the number of bounces associated with an email address.
The static list created from the dashboard is what we advise should be used for cleanup. It is a snapshot of the contacts who are ineligible for future email due to bounces.
This is definitely an improvement but what about being able to map to your CRM? Thats why I need this to be as a contact field. If the contacts email address is currently globally or hard bounced, this should be able to be mapped to a Salesforce field so the Sales team doesn't then try to email themselves. It should be available as field so you can map it. And if the email is changed, it updates that field.
