also, is this script to add that you are referring to:
var myForm = MktoForms2.allForms()[0];
myForm.addHiddenFields({
//These are the values which will be submitted to Marketo
"Email":"test@example.com",
"FirstName":"John",
"LastName":"Doe"
});
myForm.submit();
Well, you’ve guaranteed that the field will be empty in any case where it can't be pre-filled. And it can’t be pre-filled unless someone clicks a Marketo-tracked link and there’s no conflict with an existing session.
not sure I understand the second part of your reply. The email address does not appear on the email-sub facing version of the form; all that appears is a CTA that once clicked, will trigger an email send to the email sub.
@Khyra wrote:
not sure I understand the second part of your reply. The email address does not appear on the email-sub facing version of the form; all that appears is a CTA that once clicked, will trigger an email send to the email sub.
What is an “email-sub”? You mean a Marketo Person/Lead?
As explained above, if the hidden input for Email Address is empty at the time of submission, the form will create a new lead with an empty Email Address field. This is the expected behavior. How are you ensuring that the email address is not empty?
how does Marketo create a new lead/person/email sub(scriber) on a form that just includes a cta? What is the trigger causing this expected behavior?
The standard term for records in the Marketo database is Person (People if plural). There's no trigger (in literal Marketo terms, triggers are used in campaigns that are required to listen for a specific person activity) at play here, instead, there's a form submit (post) at play. A form submit action would either create a new person record or update an existing person record in Marketo. As you would probably know, Marketo's default de-dupe key for form fills is the Email Address. If your form post doesn't include an email value, then Marketo doesn't have anything to de-dupe against and thus creates a new person record in the database.