Request Info/Demo Page & Campaign Setup using UTM Parameters/Querystrings? | Community
Skip to main content
T
Tom_Kerlin2
Level 7
May 4, 2017
Question

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

  • May 4, 2017
  • 1 reply
  • 4587 views

Hello,

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).

Thanks,

Tom

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    1 reply

    A
    Anonymous
    May 4, 2017

    If I understand your situation correctly, I suggest you have one page. For the email campaigns, you can use a tagged link that will identify that it's coming from an email campaign. Anything without a tagged link can be assumed to not be part of an email campaign.

    You can pass the tagged values through UTM parameters. Have a smart campaign that listens for that value and direct it with the appropriate flow steps. You'll just need to ensure there's a hidden field on the form to capture it.

    Are you using any UTM parameters for tracking today?

    T
    Tom_Kerlin2Author
    Level 7
    May 4, 2017

    Thanks Anna,

    Screenshot below is the smart list criteria for a test smart campaign that would track parameters specific to an email campaign:

    What's not clear to me is how to set up another smart campaign to capture only people coming to page not related to ongoing email campaign. Would the smart list contain only 'Fills Out Form'? Just concerned that the people who are related to an email campaign would also pass through the smart campaign that's supposed to only capture people not tied to email campaign given that filter criteria.

    We're not using UTM Parameters for tracking today.

    Tom Kerlin
    A
    Anonymous
    May 4, 2017

    You could have a smart list only containing 'Fills out Form' and then in the flow, remove any one ('Remove from Flow' + 'Add Choice') that qualifies for an email campaign using the appropriate criteria (say, a field that always gets filled when someone comes through that's tied to an email campaign).

    Alternatively, you can use the inverse filters on the smart list if these values are cleared out after the email campaign is done.

    Terms & ConditionsAccessibility statement

    Loading footer...