I have a form set up with a hidden field to capture the utm_campaign on the referral link and write it to the Person Source. If its not present, it defaults to Gated Content. Here's how I have it set up:
I'm trying to test it with some ads we're running. The ads point to this URL: https://www.plasticsurgery.org/cosmetic-procedures/liposuction?utm_source=Dynadmic&utm_medium=Video-...
On that page, there's a CTA that leads to a Marketo landing page at https://pages.plasticsurgery.org/LiposuctionHandbook.html
I've been trying to test it by pasting the link above into an Incognito browser, clicking on the CTA, then creating a fake account. But when I check the program member record of the fake account, it shows the Person Source set to the default, Gated Content.
I had this set up and let it run for a few days, and I did catch the UTM parameter of a completely different campaign in the list (this is the only thing currently running that sets Person Source.) So the field is capturing something, just not when I do it.
Do I need to set this up differently, or is this just something that isn't going to be captured (or maybe it is - but no one from the ads is filling out the forms)?
Solved! Go to Solution.
Decided this was worth a blog post: https://nation.marketo.com/t5/product-blogs/here-s-why-your-autofill-from-referrer-parameter-setup-s...
You can't track Referrers like that anymore unless you have specifically configured the source site (your corporate site in this case) to pass full Referrer info.
When no specific policy is set, browsers now default to the Referrer Policy "strict-origin-when-cross-origin" which means that when you go from https://example.com?utm_whatever to https://pages.example.com the passed Referrer is stripped down to only https://example.com.
So you either need to:
Decided this was worth a blog post: https://nation.marketo.com/t5/product-blogs/here-s-why-your-autofill-from-referrer-parameter-setup-s...
Ok, so this clears things up. We're not wrong, the internet is wrong.
Talked it over with my team, and we're going to attempt to pass the info in a cookie to see if that works out.