This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by
Could you be more specific?
Do you mean validation on the field that the entered data is an email address? Or do you mean checking that the email address is valid, form the standpoint of being able to send an email and not have it bounce?
If you mean verify, I like to use a webhook and pass the data to an api like; http://verify-email.org/register/levels.html Then based on the repsonse, flag is the email is valid or not valid with an Email Valid field. I don't believe Marketo has a built in validator that I know of.
3 replies
A
Anonymous
Accepted solution
October 31, 2014
Could you be more specific?
Do you mean validation on the field that the entered data is an email address? Or do you mean checking that the email address is valid, form the standpoint of being able to send an email and not have it bounce?
If you mean verify, I like to use a webhook and pass the data to an api like; http://verify-email.org/register/levels.html Then based on the repsonse, flag is the email is valid or not valid with an Email Valid field. I don't believe Marketo has a built in validator that I know of.
how do you get marketo just to validate it has the right email form, meaning
no special characters, contains an @ and ends with a dot something. It seems like the form designer has an error message for invalid email, but you can enter in something with out the doman e.g. persona@marketo
the problem with this is when it syncs with salesforce, SFDC throws an error
Technically persona@marketo is a valid email address. It may not be routable on the public internet, but it's valid (in fact most early email addresses had exactly this form, because they were relayed between hosts with simple names).
I agree that in the case of a marketing form it shouldn't be allowed, but this is just one of the myriad problems with thinking email validation is a simple test for "no special characters." There is no specification (as in Internet standard/RFC) that will parallel exactly what you expect, so you have to make up a non-standard -- either less or more stringent but at the same time somewhat arbitrary -- set of validation rules.
I recommend you start by implementing my solution at the base of this post: Re: How to correct typos in email addresses? By default, this code will check if the TLD is valid. We can go deeper with it and check to see if the domain has an MX record... which you might think would suffice, but actually you have to see if it has an A record as well. Beyond that, of course, is actual real-time email validation by attempting to connect to the remote server. But those services cost $$.