Thanks Jason. Sorry for all the questions regarding utm’s and embedded forms. I’ve inherited this Marketo instance and am coming across things like this that need to be fixed.
Basically, this form is not in any programs or SC, but according to Sanford that should not be a problem. The form was basically created just to be embedded on our site. An example of a value I would expect to see for Lead Source would be “Website” and Source Detail would be “Organic”. Since this form, I believe, was created specifically to be used as a contact form on our website, I think entering a default value for these fields would solve our problem, that is as long as this form is only being used on our website.
Although your other option of a SC with “Fills out form” would be just as useful. I’m trying to better understand the best ways for embedded forms to be tracked in the future to avoid these types of issues.
My initial question of where to place utm’s, comes from the idea that if the utm’s are not part of the form embed code on the website, the fields would not populate, example
My thought process is that by including the utm’s in the form embed code, when the form is submitted, it would caputre the lead source and source detail. But now I am thinking that is wrong based on what I have read.
Thanks for all the help and advice!
Hi James,
you ou do not technically need a program to handlr that form, but the best practice is that you at least host the SC in a program, so that each person filling out the form would become a progrMa member and get the program as acquisition program when they are a new lead. This will preserve your reporting capabilities.there is also a virtue to handling things always through programs: consistency reduces the risks of errors.
the form itself canbe hosted in the same program or shared I the design studio. The lattter is better if the form is to be reused. And you never know in advance if you might need to reuse a form in the future.
Greg