This content has been marked as final. Show 7 replies
The solution is simple: add the noscript tag, redirectling to an invalid URL, discouraging users (mostly spammers) trying again.
I would suggest adding noscript to Landing Page Options - Edit Page Meta Tags - Custom Head HTML
Do you have progressive profiling enabled on this form? I have run into issues where a lead may have been using a public computer and entered in their data. And then a new person comes to the same form, and it is showing the additional progressive profiling fields and whatever required fields you have. This will allow the new lead to submit the form and not ever see the original form fields. I hope that makes sense.
I think the first answer may be the ticket... I'm gonna look into applying that approach first.
Kenny, your idea does make sense but, alas, this specific form doesn't have progressive profiling enabled, so I don't think that's the dilemma in this specific case. Good thought though!
Appreciate you jumping in with thoughts! - Jen
Breno - Quick follow-up question:
Clearing cache and cookies or using a different browser can eliminate an obscure caching problem.
Please let me know the landing page name if the problem persists.
Based on the below alert sent out earlier today, I'm guessing I'm not the only person that this is happening to... unless this is an isolated event that's occuring for a different reason that the spam issues Marketo is seeing?:
"We are experiencing a high volume of spam-submissions through forms. Our engineering team is aware of this issue and is currently working to resolve. Following the resolution of this issue we will publish instructions on how best to scrub these false leads from your database. We are experiencing a high volume of spam-submissions through forms. Our engineering team is aware of this issue and is currently working to resolve. Following the resolution of this issue we will publish instructions on how best to scrub these false leads from your database...."
Jen, you are right regarding today's occurrence. Last week's might be an early symptom. Hopefully the freshly solved P1 posted as alert will solve the problem you are facing otherwise I will be glad to investigate the problem if the instance was deliberately targeted by spmabots.