AnsweredAssumed Answered

Request Info/Demo Page & Campaign Setup using UTM Parameters/Querystrings?

Question asked by Thomas Kerlin on May 4, 2017
Latest reply on May 5, 2017 by Justin Norris



We just received feedback from our Sales Ops and CRM Analytics team that we'll need to associate our event-related Request Info/Demo page submissions with a CRM campaign that's completely separate from the event CRM campaign itself. The way its set up today, all of our Request Info/Demo pages are built inside the actual event program, and we have a separate yet identical Request Info/Demo page for each event.


I want to build smarter and reduce volume of these identical pages without sacrificing tracking and reporting, so I wanted to know how other people have built out these pages and the campaigns that are tracking them.


I'm thinking of creating a separate channel, then building (1) Request Info/Demo page that the team can use as a default page if lead gen. efforts aren't tied to an existing email campaign. Then, I would build a 2nd identical Request Info/Demo page that would capture specific UTM parameters so that form submits would only pass through a specific triggered smart campaign tied to that email campaign. The 2nd page would be used by all of the email campaigns.


However, after reading a couple of additional threads related to this topic (Which Value to use for utm code tracking , Tracking Web Page Visits from a Custom Built URL  ), I'm not sure if I should just be using Querystring values to capture specific form submits and page visits, since UTM parameters are only captured upon form submit and I still want to be able to track page visits. I also read something about using 'Cookie Values', since cookies will store the parameters in case that person navigates away from that page and comes back later. However, will cookies allows those stored parameters to be overwritten in case that same person engages in another email campaign? Lastly, will any of these approaches require the use of Javascript? Ideally, the approach we take isn't too technically complicated (it doesn't have to be perfect).