Form Setup
Set up SourceTag with ClickFunnels
ClickFunnels lets you add hidden inputs to your funnel step forms. Depending on your ClickFunnels version (1.0 or 2.0), you can do this through the form editor or by adding custom HTML.
What you need
- SourceTag installed on your ClickFunnels page (added via the tracking code settings)
- A ClickFunnels funnel with a form step
Step 1: Add SourceTag to your funnel page
- In ClickFunnels, open your funnel and go to the page with the form
- Go to Settings > Tracking Code (or Head Tracking Code)
- Paste your SourceTag script tag in the Head section
- Save
[IMAGE: Screenshot of ClickFunnels tracking code settings with SourceTag script added]
Step 2: Add hidden fields to the form
ClickFunnels 2.0
- Open the page in the ClickFunnels editor
- Click on your form element
- In the form settings, click Add Field
- Set the field type to Hidden
- Set the Name to the SourceTag field name (e.g.
st_fc_channel) - Leave the value empty
- Repeat for each field
[IMAGE: Screenshot of ClickFunnels 2.0 form editor with hidden field being added]
ClickFunnels 1.0 (Classic)
ClickFunnels Classic does not have a dedicated hidden field type in the visual form editor. You need to add custom HTML:
- Open the page in the ClickFunnels editor
- Below or inside the form section, add a Custom HTML element
- Paste the hidden input elements (see code below)
- Make sure the HTML element is inside the form
<!-- SourceTag core hidden fields -->
<input type="hidden" name="st_fc_channel" value="">
<input type="hidden" name="st_fc_detail_1" value="">
<input type="hidden" name="st_fc_detail_2" value="">
<input type="hidden" name="st_fc_detail_3" value="">
<input type="hidden" name="st_fc_detail_4" value="">
<input type="hidden" name="st_lc_channel" value="">
<input type="hidden" name="st_lc_detail_1" value="">
<input type="hidden" name="st_lc_detail_2" value="">
<input type="hidden" name="st_lc_detail_3" value="">
<input type="hidden" name="st_lc_detail_4" value="">
<input type="hidden" name="st_fc_landing_page" value="">
<input type="hidden" name="st_lc_landing_page" value="">
<!-- SourceTag optional fields -->
<input type="hidden" name="st_fc_click_id" value="">
<input type="hidden" name="st_lc_click_id" value="">
<input type="hidden" name="st_visits" value="">
<input type="hidden" name="st_days_to_convert" value="">
<input type="hidden" name="st_device" value=""> [IMAGE: Screenshot of ClickFunnels Classic editor showing custom HTML element with hidden inputs]
Core fields (add these)
st_fc_channelst_fc_detail_1st_fc_detail_2st_fc_detail_3st_fc_detail_4st_lc_channelst_lc_detail_1st_lc_detail_2st_lc_detail_3st_lc_detail_4st_fc_landing_pagest_lc_landing_page
Optional extended fields
st_fc_click_idandst_lc_click_id(click IDs)st_visits(visit count)st_days_to_convert(days since first visit)st_device(device type)
Step 3: Verify the hidden inputs are inside the form
This is critical. The hidden input elements must be children of the <form> element in the rendered HTML. If they are outside the form, the data will not be submitted.
To verify:
- Preview or publish the page
- Open your browser’s dev tools (right-click > Inspect)
- Find the
<form>element and check that the hidden inputs are inside it
[IMAGE: Screenshot of browser dev tools showing hidden inputs inside the form element]
Step 4: Test
Visit the page with UTM parameters:
?utm_source=test&utm_medium=cpc&utm_campaign=clickfunnels-test Submit the form. Check where your ClickFunnels form data goes (email notification, CRM integration, webhook). The hidden field values should be included.
[IMAGE: Screenshot of ClickFunnels form submission data showing populated hidden fields]
Tips
- In ClickFunnels Classic, the custom HTML approach is the most reliable. Make sure the HTML element is placed inside the form section, not in a separate section.
- ClickFunnels 2.0 has better native support for hidden fields through the form editor.
- If you are using ClickFunnels integrations (email, webhook, Zapier), hidden field values are included in the form submission payload.
- Copy field names from the Fields page in your SourceTag dashboard to avoid typos.