Validate ZeroBounce with status 'Catch-all' emails before sending Marketing Emails

Hi community,

We use a third-party tool, ZeroBounce, to validate email addresses before sending marketing emails. Many of the emails are validated with the status Catch-all. ZeroBounce defines Catch-all emails as "emails impossible to validate without sending a real email and waiting for a bounce. " - see here.

There was already a one-on-one conversation from HubSpot for many of these email addresses. I can manually validate the email by going into the contact and inspecting the status of the one-on-one emails.

My question: Are there any fields in HubSpot that I can use to identify if there was any successful one-on-one communication with a mailbox?

Hi @ChristoV,

Great question - this should be a quick solution!

HubSpot has multiple properties you could rely on here, some of which are:

  • Recent sales email open date
  • Recent sales email clicked date
  • Recent sales email replied date
  • Last engagement date
  • Marketing emails delivered
  • Marketing emails opened
  • Marketing emails clicked

You could set up a workflow to check for these properties, then adequately set your Neverbounce propreties instead of manually doing this work!

I hope this information is useful to you! If you found this reply helpful, please consider marking it as a solution so others can easily find it too.


LinkedIn Banner (3).jpg

Hi @ChristoV,

There are a few HubSpot properties which jump to mind here. You want to make sure they’re reliable.

  • Association of a contact to a conversation or activity
  • Recent sales email open date
  • Recent sales email clicked date
  • Recent sales email replied date
  • Marketing emails opened
  • Marketing emails clicked
  • Marketing email confirmation status (if you’re using HubSpot’s double opt-in feature)

@MadisonMoniz I would not rely on any properties that rely on delivery status or engagement. Delivery can fall into the trap of a catch-all email address – it would look to HubSpot as if it was delivered successfully but wasn’t. Engagement also includes non-email engagements such as meeting bookings, meaning that it’s not a reliable signal for a valid email address.

Hope this helps, Christo!

Great catch! Thanks @karstenkoehler !

Hi @karstenkoehler, thank you for the assistance. I have two questions that comes to mind:

1. If I use the activities ‘last message received date’ filter, is this more acurate than using the delivery/ engagement properties?

2. If an email is send to many, how does the related Activity and Conversation updates?

@ChristoV

  1. Yes, as an incoming email means that the address must exist, coming from, for example, john.doe@acme.com. Successfully delivering an email to acme.com however, which might simply accept all incoming emails, regardless of whether john.doe@acme.com exists, doesn’t mean anything. Similarly, a meeting can be booked with a made-up or invalid address, still counting as engagement.
  2. The filters from my screenshot are from incoming emails, not outgoing. An incoming email can only come from one address / person.

Let me know if you have any follow-up questions!