Hi @thisdave,

The routing approach basically uses if/else logic to check the email domain. If it’s on the ‘yes’ list, it gets routed to your events. If it’s on the ‘no’ list, it gets routed elsewhere. It’s not the fanciest solution and a persistent spammer could get around it if they absolutely wanted to. So with that being said, we are looking into better ‘abuse’ prevention features and functionality because our users definitely shouldn’t be getting harassed, spammed, etc.!

With that being said, you can’t apply the domain blocking to specific events but you could use the routing to check domains and then get people to the right event anyways.

Hopefully we’ll see some much needed new abuse/spam features soon!

Hi @jillian
I think a better solution would it be do add it directly to the events.
For example checking the email in the events if it contains a certain domain.

The routing approach also has not a great UX when user have to put in their email there first (just to check for spam) and then again on the next page. Also some sort of Captcha might be great.

Any things you want/can to implement in the near future?

This is really a big pain for our company.

I’d love to see something like this implemented on the event level, so I’ll be sure to continue passing along the feedback to our Product team.