Tracking Referral Web URLs ?ref= | Community
Skip to main content
A
Anonymous
March 2, 2013
Question

Tracking Referral Web URLs ?ref=

  • March 2, 2013
  • 1 reply
  • 8635 views
Is there a way to track the use specific URL with ?ref codes appended?

Say I have an awesome landing page (http://pages.abc.com/awesome.html). When I post it on Twitter or Facebook or blog or wherever, I append the the URL with a "?ref=" tag so:
  • http://pages.abc.com/awesome.html?ref=twitter
  • http://pages.abc.com/awesome.html?ref=fb
  • http://pages.abc.com/awesome.html?ref=blog
  • http://pages.abc.com/awesome.html?ref=newsletter
  • http://pages.abc.com/awesome.html?ref=harlemshake
  • http://pages.abc.com/awesome.html?ref=whatever
Now I'm using these URLs all over the place, and people are coming to my awesome landing page and I'm having awesome conversions. Is there a way to track the performance of the landing page as a whole, and specifically each REF URL?

And taking it a step further, say I consistently use this across various other landing pages, can I track what REFs are best? Maybe people on Twitter really like /awesome.html, but don't like /justokay.html or /lame.html.

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

    1 reply

    Josh_Hill13
    Josh_Hill13
    Level 10
    March 2, 2013
    Yes, you can put the ref code into a field using a hidden field:
    1. Create String field "RefCode"
    2. Add as hidden to form
    3. set to populate as URLparam
    4. you will need a campaign to listen for this code and then ask marketo to add the lead to a SFDC campaign or a static list or create an interesting moment or something so you can keep track of the lead. The problem is the RefCode field will be overwritten the next time the lead comes in from a different url you used. So you need a tracking method.
    5. You can also report on people who Filled Out Form on Page Awesome with Refcode=X (or use custom columns).
      Terms & ConditionsAccessibility statement

      Loading footer...