You put the form anywhere you want to track UTM codes. It gets submitted automatically and the user never has to deal with it. It's exactly the same as the general suggestion about mapping UTMs to Form Fields (which in turn become fields on a Lead) except the user doesn't have to interact with the form.
(In technical terms, it's an Ajax POST. It happens that that's the method Forms 2.0 uses to send to the Mkto servers.)
@Bruce J You can search on the raw query string. But as far as persisting the Lead Source(s) to the Lead you'd have to set up a flow to write out the fields. It's way more complex IMO than having the LS automatically populated (which is why the form-field-read-from-query-string-or-cookie feature exists in the first place, right?).
@Bruce J - This is the way I want to track everything. But - it doesn't seem to be working. Take a look at the below screenshot. This smart list is not returning anyone. And, I know of at least one known lead who visited that page. It doesn't work either when I use "Referrer" instead of "Querystring" as a constraint.
@Kelly -- Your 2nd screenshot shows the UTM info coming through in the Referrer URL, so that's probably why the Querystring search is coming up empty.
A couple things I'd try:
1. I can't tell from your first screenshot if you've included the UTM codes in the Web Page value. If so, try removing those. Also try shortening the whole URL value that's there. Leave enough of it so that the query still searches just for that specific page, but perhaps remove part of it (for example, contains: "making-print-your-competitive-advantage" instead of the full URL.)
2. Try adding another filter for Anonymous=true or Anonymous=false and see if that changes the results.
If neither of those work, then I may be stumped here.
But - I called Marketo Support (thanks Grant Booth, for your help!) and I believe the issue is that my subscribe form is on a landing page that is iframed into the site and it's not showing that the lead clicked on the actual story, just the iframed page.