Thank you Sanford for looking at this. Am I missing something or am I just not getting this. I understand now, I think, what the problems are, but each time I think I have a solution it ends up not being correct.
No, I have not changed anything in terms of query param's on this form, but if I understand what you are saying, is the Lead Source and Source Detail are not populating on the alert email due to mismatching fields on the form and I need to change the utm_Source LT to utm_Lead Source and do the same for the Source Detail. Or even need to add a hidden query param of Lead_Source_Detail.
The test url is: app-sj20.marketo.com/m#FOP1720
Detail pop-up:
I do see the query param's on this are missing, which I might ascertain as being the problem. If this is one of the problems, then I have this same problem with other forms with other incorrect query param's or just completely empty query param's.
You're not organizing and controlling your test environment. This is not going to help.
The Filled Out Form activity in this screenshot is from a URL that didn't have any UTM parameters in the query string. Hence it doesn't matter what fields you're mapping the params to: you will never get any new values posted in this scenario.
Beyond that, you don't have the Lead Source and Lead Source Detail as hidden fields on the form. You have other fields on the form! So your intended fields will not be populated from a form post, even if the page has UTM parameters in the query string.
Well, as I have mentioned previously, this was all done prior to me and this is what I have walked in to and now need to fix. Me, I would never pushed something live without testing it.
So how do I fix this. Based on your assessment I need to:
Add the query string to the url
Add Lead Source and Lead Source Detail as hidden fields on the form
Will implementing these 2 changes get me closer to resolving our alert email fields not populating correctly?
Add the query string to the url
Your form is config'd to read values from the current query string into hidden fields. So, yes: you must have not only a query string in general but specifically a query string with parameter names matching the params in your form configuration.
Add Lead Source and Lead Source Detail as hidden fields on the form
Yes, if you want these fields to be populated upon a form submission, naturally they need to be on the form, as opposed to other fields that appear to have similar names.
Will implementing these 2 changes get me closer to resolving our alert email fields not populating correctly?
Yes, but I don't like the term "correctly" since that makes it seem like there's a bug. There isn't a bug, you're including blank fields in your alerts. Their remaining blank is correct behavior given your config.
Thank you Sanford! I can't thank you enough for your support and hopefully patience in helping me solve these issues. I figured these were the issues, if only I had more adequately explained what I was trying accomplish and the problems this could have been resolved in half the length.
Hi James,
Autofill field value from URL parameters option works on both Marketo and Non-Marketo landing pages(i.e Wordpress). However, this configuration only works if the user lands directly on contact us Wordpress page and fills out Marketo form. If the user goes on another page after landing on Contact Us and comes back to contact us page and fills out Marketo form then UTM fields will not have any value(Missing URL parameters). To capture this behavior you need to set cookies with URL parameters values and use Auto fill option with cookie.
If this configuration is set up correctly then there is no need to set up any Smart Campaign to get UTM fields values into the lead. Please observe if you want these UTM fields values into other fields(i.e Lead Source) then it requires SmartCampaignn setup.
Best Regards,
Avtar Singh
Adding onto the SC setup from Avtar for Lead Source if you go this route vs adding hidden form fields for these, this is handled at the program level- My Tokens tab, create Lead Source and Lead Source Detail tokens, {{my.LS}} {{my.LSD}} and their corresponding values you want to track for each. In the form trigger SC workflow drag in Change Data Value filters for your Lead Source and Lead Source Detail field attributes and use the tokens you created and those token values will be recorded on the lead record that's submitted the form.