CRM Setup

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.

[IMAGE: Screenshot of Kit settings navigation]

Step 2: Create custom fields

Create a new custom field for each SourceTag data point:

Core fields (always create)

Field nameLabelType
st_fc_channelFirst Contact ChannelText
st_fc_detail_1First Contact SourceText
st_fc_detail_2First Contact CampaignText
st_fc_detail_3First Contact TermText
st_fc_detail_4First Contact ContentText
st_lc_channelLast Contact ChannelText
st_lc_detail_1Last Contact SourceText
st_lc_detail_2Last Contact CampaignText
st_lc_detail_3Last Contact TermText
st_lc_detail_4Last Contact ContentText
st_fc_landing_pageFirst Contact Landing PageText
st_lc_landing_pageLast Contact Landing PageText

Optional fields

Field nameLabelType
st_fc_click_idFirst Contact Click IDText
st_lc_click_idLast Contact Click IDText
st_visitsVisit CountText
st_days_to_convertDays to ConvertText
st_deviceDevice TypeText

[IMAGE: Screenshot of Kit custom field creation]

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.

[IMAGE: Screenshot of field mapping in Kit or integration tool]

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.

[IMAGE: Screenshot of Kit subscriber record showing 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.