2 of 2 people found this helpful
Marketo Forms can easily fill hidden fields from URL query params (?name1=value2&name2=value2) or from cookies. (When you add a hidden field, you specify the source.)
If you're talking about organic traffic hitting http://landing.example.com (with no query params) at some point after a user visited http://www.vaneck.com/?utm_medium=somethingorother, then you'll need to save the `utm_medium` value into a cookie so that it can be picked up later by the form.
If you're talking about links on http://www.vaneck.com/?utm_medium=... going directly to a Marketo LP, then in theory you could just copy the utm_medium into the query string: http://pages.vaneck.com?utm_medium=. But chances are you're not going to take users straight from one page to the other, so you would need a cookie to remember the value across pages on www.vaneck.com as well. Once it's in a cookie, use a cookie as a source.
Edward Unthank (ETU) has an expert's guide to lead source tracking that he'll probably post here if I give him a nudge.
3 of 3 people found this helpful
(Here's a lead source guide Sanford was referring to: Marketo Lead Source Guide)
Also, any internal links (aka from your home page to another page on your site with the same parent domain and same GA tracking shippet) shouldn't have UTM parameters because that fudges Google Analytics visit data pretty badly. It gets treated as a new session improperly and skews numbers and visitor paths.
You would be able to get optimization reporting metrics in GA for aggregate/anonymized, because you'll be able to see conversions based on paid traffic sources in GA. That's assuming you have goals in GA set up, but that's easy enough—I just make all the landing pages for TOFU/MOFU conversion follow-up pages start with "thank-you-" and create a goal for that, and then set up a BOFU conversion follow-up page convention of "thanks-"
Edward Unthank | Founder, Etumos
Hi Kristen -
Specifically, when setting cookies, include domain and path attributes. Setting domain and path attributes allow cookies to be read across subdomains. To have a cookie available to all subdomains, you must put a . in front of your domain in the domain attribute. Setting the path attribute as path=/ will have the cookie be available within the entire specified domain.
document.cookie = key + "=" + query[key] + ";domain=.yourdomain.com;path=/";