Ability to filter emails/web addresses using endings

[Anonymous]

For example:

If email address [ends with] .uk, do not send email.

If website address [ends with] .mx send Spanish version of email.

[Anonymous]

Can you use the constraint "contains" instead of "ends with"?

[Anonymous]

That doesn't work for instances where a person/company is using a subdomain (such as www.site.archive.com – would not be accurate for .ar [Argentina]), as well as individual's email addresses (such as suzy.millison@site.com – would not be accurate for .mil [military]). Thusly why it would have to be "ends with"

[SanfordWhiteman]

But then you catch partial matches in the local part of the email address (the username), like john.ukman@example.com as well as domain matches like sandy@example.uk.net.  You can try to narrow in with other conditions but you'll never be totally accurate.

What I sometimes do is parse out the domain as a whole (using a webhook) into private domain + public domain (2LD/TLD) fields.

The addition of an [ends with] constraint would save a lot of webhook pain!

[Anonymous]

"Ends with" would not catch matches anywhere in an email address or website, but the end.

"End with" would be the most accurate in a lot of use cases.

For example (like I mentioned earlier), if you did "ends with" .ar (Argentina) > send Spanish version of email.

I am sure there are different ways to go about this, but yes, having an "ends with" option would save a lot of extra work/brain power!

[SanfordWhiteman]

(I was responding to Christina, so you'll see I agree w/you on every point.)

[Anonymous]

Oh, sorry! I confused the conversations. Thank you!!!

[Anonymous]

All good points, I'll upvote!