Passing UTM values through hidden custom fields?

Hi! I’m trying to pass UTM values through hidden custom fields on my Infusionsoft order form, so that I can track lead source accurately. I’m using a tool called Segmetrics to automatically collect and store the UTM values in Infusionsoft.

This is the order form URL with test UTM values: https://fo104.infusionsoft.app/app/orderForms/-Mental-Model-Club-1-Trial-TEST-FORM?utm_source=Facebook&utm_medium=cpc&utm_campaign=MM07-TEST&utm_content=test

My custom fields are:
utm_source
utm_campaign
utm_medium
utm_content

Is anything wrong with my code, or is there anything else I’m missing?

2 Likes

did you get this to work? @Michael_Simmons

It sounds like you’ve got the custom fields set up in Infusionsoft and you’re using Segmetrics to capture the UTM data, but you’re not seeing the values come through with form submissions.

The most common issue with this setup is that UTM parameters only get captured if the person completes the form on the exact same page they initially land on. If someone clicks your Facebook ad, lands on your homepage (with the UTMs in the URL), then navigates to the order form page and submits there, the UTMs will be lost because they’re no longer in the URL.

To solve this, you need something that captures the UTMs when the visitor first arrives and stores them (usually in a cookie) so they persist as the user browses around your site. Then when they eventually submit your order form, those original UTMs get written into the hidden fields.

I’m not familiar with how Segmetrics handles this specifically, so you might want to check with them about whether their tool stores UTMs across pageviews or if it only captures what’s currently in the URL.

If you need an alternative approach, there are tools like Attributer.io that handle this automatically. They capture UTM parameters when someone first lands, store them in a first-party cookie, and then write them into hidden fields on your Infusionsoft forms when they’re submitted. As a bonus, they also capture data on leads that come from organic channels (Organic Search, Organic Social, Direct, etc.) where UTM parameters aren’t present.

You could also write some custom JavaScript to handle the cookie storage and field population yourself, but that requires ongoing maintenance as browsers update.