We have created one landing page to be used in multiple Pay Per Click campaigns. We also created a form in the design studio with hidden fields that we enabled to pull source data from the URL.
One thing we are trying to do is track URL web page visitors to two seperate MKTO programs and change their program status by source code in the custom URL to understand the effectiveness of each PPC campaign provider. Can this be accomplished by utilizing the Referrer or Querystring constraints in the "visits web page" trigger?
URL Examples:
The funneling of leads to MKTO program is based off the value after source-code-detail.
Thank you!
Querystring
But I would use the value from the Hidden field rather than rely on the querystring.
Thank you, Josh!
So just to be sure I understand, when I set up the smart list I will use:
Visits Web Page ... use LP
Constraint - Querystring "contains" "multiview"
Thanks again!
Actually what Josh is saying is that you should use the hidden form field (which you have set up to parse the URL and pull in specific form data) rather than trying to constrain by query string in the smart list.
Marketo does not contain an actual query string parser on the server side, so it can't be as precise as the Forms 2.0 URL parser.
I agree with Josh, but this requires that you trigger on the Filled Out Form activity, since that's when the hidden fields are posted to Marketo. If you're triggering only on Visit Web Page, you're saying you don't care whether people convert or not from that page, you still want to change their program status (which of course won't show leads that are not yet known to the system). If you're triggering on VWP alone you can't use the form fields as they will not be sent to you. In this case you'd have to scan the query string in the SL.
Hi Sanford -
Thank you for your reply. I'm not sure I follow though. We are working with two different PPC companies and want to measure the success of the program against the investment. Meaning we want to assign membership to two different programs based upon which URL the lead clicks on then fills out the form to capture the hidden value.
From what you say above it sounds like it is not possible to assign program membership based only on the URL. I understand the limitations of capturing the actual hidden field value on a page with a MKTO form only.
Any insight on how to achieve the above would be greatly appreciated.
Thank you!
Thank you for your reply. I'm not sure I follow though. We are working with two different PPC companies and want to measure the success of the program against the investment. Meaning we want to assign membership to two different programs based upon which URL the lead clicks on then fills out the form to capture the hidden value.
From what you say above it sounds like it is not possible to assign program membership based only on the URL. I understand the limitations of capturing the actual hidden field value on a page with a MKTO form only.
You can certainly assign program membership based on a visited URL, without a lead filling out a form! The issue is that you should not be attempting to put anonymous leads into a program because their program membership will not be formally processed until they become known (the process known as "promotion" in Munchkin 2.0). So you will have pending memberships -- and some arcane rules surrounding promotion to deal with -- and this is only going to bring confusion. Like Jennifer DiMaria says, this sounds more like a job for GA, if all you want are inbound pageviews for both anonymous and known leads.
It's possible I'm misunderstanding, but if you're tracking only clicks, I feel like this is something you'd want to do in Google Analytics as opposed to Marketo so you can see incoming traffic to the landing page based on campaign. You can set up goals in GA to track the flow, as well, but Marketo would be best used to then track who converted in each Program.
Also be skeptical about the number of webpage visitors Marketo states for each landing page, as last I knew, it doesn't filter out bots the way GA does.
Also be skeptical about the number of webpage visitors Marketo states for each landing page, as last I knew, it doesn't filter out bots the way GA does.
I think this is true for LP reports (which do not rely on Munchkin to count pure HTTP hits) but not so much for SLs that rely on Munchkin Visit Web Page being run by the visitor.
Ah, yes! Thanks for clarifying!