Skip to main content
Level 3
November 1, 2018
Question

UTM params on form submission

  • November 1, 2018
  • 4 replies
  • 5980 views

Is there a way to submit utm param values as hidden values on form submission from original referral url, without using javascript? I'm doing below(image) but not catching anything on form submission.

Thank you for your help!

4 replies

Josh_Hill13
Level 10
November 1, 2018

did you structure your utm and url correctly?

I think Get Value has a diff option there.

Level 3
November 1, 2018

URL is structured like: xyz.com/test/marketo/?utm_source=bing&utm_medium=cpc and renders like that

Dan_Stevens_
Level 10
November 1, 2018

"Get Value" should be "URL Parameter" - not "Referral Parameter".

Dan_Stevens_
Level 10
November 1, 2018

Sorry, read your question too fast.  I don't think this is possible without JS.  Seems like most are turning to this code here: MarTech/UTM-Tracking at master · yanirclsr/MarTech · GitHub​ or https://romanoffconsultants.com/solutions/

Level 3
November 1, 2018

Thank you Dan, looks like we will have to implement that js.

Grégoire_Miche2
Level 10
November 1, 2018

+1 on Dan on this. The original UTMs when the person lands on your web site can only be captured without JS if the Marketo form is on that same first navigation page.

If you want to get the UTM values to persist through the web session and be captured on the second or following page, you will need to store them in cookies or local storage and capture the values from there.

-Greg

Level 3
November 1, 2018

Thanks Greg.

The munchkin code does not track that in the original referral? I thought it would capture the first touch url there.

Our developer is not aboard with using js(citing newer browser policies around tracking) and says Marketo is storing and we should use that than dropping our own cookie.

SanfordWhiteman
Level 10
November 1, 2018

The munchkin code does not track that in the original referral? I thought it would capture the first touch url there.

The Original Referrer is stored on the lead. It isn't stored in the browser (for the obvious reason that the current session may still be anonymous and couldn't possibly know what the value might be once the anonymous session is merged with an already-known lead).

Our developer is not aboard with using js(citing newer browser policies around tracking)

This objection makes no sense. Munchkin already uses JS + cookies for tracking. Adding a persistence layer (and often many such libraries) is normal behavior for a modern website and if the developer doesn't understand that, they should get out of the way.

Kristina_Wrigh1
Level 1
November 8, 2018

We had the same problem recently when we moved to using a universal form structure (i.e., using the same form ID across multiple pieces of content), but we were able to successfully use hidden fields for URL Parameter on our forms (we do not use JS)

Here's how we have the smart campaign set up to listen for the form fill, and determine which program to assign success based on the UTM data captured from the hidden fields.

Hope this helps!