If email address [ends with] .uk, do not send email.
If website address [ends with] .mx send Spanish version of email.
Can you use the constraint "contains" instead of "ends with"?
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 firstname.lastname@example.org – would not be accurate for .mil [military]). Thusly why it would have to be "ends with"
But then you catch partial matches in the local part of the email address (the username), like email@example.com as well as domain matches like firstname.lastname@example.org. 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!
"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!
(I was responding to Christina, so you'll see I agree w/you on every point.)
Oh, sorry! I confused the conversations. Thank you!!!
All good points, I'll upvote!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.