UTM params on form submission

Forum|Forum|7 years ago
November 1, 2018
17 replies
5950 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!

Marketo

Kristina_Wrigh1

New Participant

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!

Grégoire_Miche2

New Participant

+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

G

Gunpreet_Kaur1Author

New Participant

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

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.