Set up SourceTag with Kit

When a visitor submits a form with SourceTag data, the attribution fields need somewhere to go in Kit (formerly ConvertKit). You need to create custom fields that match the SourceTag field names.

What you need

• SourceTag installed and form hidden fields set up
• Kit account with admin access

Step 1: Go to custom fields settings

In Kit, custom fields are created automatically when you first use them, or you can manage them under Settings > Custom Fields.

Step 2: Create custom fields

Create a new custom field for each SourceTag data point:

Core fields (create these)

Field name	Label	Type
st_fc_channel	First Click Channel	Text
st_fc_detail_1	First Click Smart Field 1	Text
st_fc_detail_2	First Click Smart Field 2	Text
st_fc_detail_3	First Click Smart Field 3	Text
st_fc_detail_4	First Click Smart Field 4	Text
st_lc_channel	Last Click Channel	Text
st_lc_detail_1	Last Click Smart Field 1	Text
st_lc_detail_2	Last Click Smart Field 2	Text
st_lc_detail_3	Last Click Smart Field 3	Text
st_lc_detail_4	Last Click Smart Field 4	Text
st_fc_landing_page	First Click Landing Page	Text
st_lc_landing_page	Last Click Landing Page	Text

Optional extended fields

Field name	Label	Type
st_fc_click_id	First Click Click ID	Text
st_lc_click_id	Last Click Click ID	Text
st_visits	Visit Count	Text
st_days_to_convert	Days to Convert	Text
st_device	Device Type	Text

See Captured Fields for the full list of available fields.

Step 3: Map form fields to Kit fields

If your form builder sends data to Kit via an integration (Zapier, native feed, webhook, etc.), make sure the SourceTag form fields are mapped to the corresponding Kit custom fields.

Step 4: Test

Submit a form with UTM parameters and check the subscriber record in Kit. The custom fields should be populated with attribution data.

Tips

• Kit only supports text-type custom fields, so number fields like Visit Count and Days to Convert will be stored as text. This is fine for attribution tracking purposes.
• The field key in Kit must match the form field name in your integration mapping.
• Test with a fresh subscriber (not one that already exists) for the cleanest test.