Encatch
Welcome to Encatch Docs
Advanced Options

Source Tracking

Capture URL tracking parameters alongside feedback submissions

Source tracking records selected URL query parameters when someone views or submits a feedback form. Use it to tie responses back to marketing campaigns, ad clicks, and referral links—without adding extra questions to the form.

Typical parameters include UTM tags (utm_source, utm_medium, utm_campaign) and platform click IDs (gclid, fbclid, msclkid).

When to use

  • You run paid or email campaigns with UTM parameters on landing pages
  • You need to know which ad, channel, or campaign drove each response
  • You want to filter or export responses by utm_campaign, utm_source, or similar
  • You use custom query params (e.g. ref, affiliate_id) and want them stored with submissions

How it works

  1. Configure which parameter names to capture on the feedback form (Advanced tab).
  2. Visitor arrives on a page with query parameters in the URL, e.g. ?utm_source=google&utm_campaign=spring_sale.
  3. Form is shown — matching values from the page URL are captured for that form.
  4. Submission — only the parameters you enabled are stored on the response as key/value pairs.
  5. Reports — view, filter, and export source data in the admin UI.

Only parameters you explicitly enable for that form are saved. If a parameter is configured but missing from the URL, it appears empty (N/A) in results.

Configuration

  1. Open your feedback form and go to the Advanced tab.
  2. Find Source Tracking and switch from Disabled to Enabled.
  3. Under Suggested parameters, click the tags you want to track (UTM fields, click IDs, etc.).
  4. Optionally add custom parameters (letters, digits, underscores, hyphens only; max 25 characters per name).
  5. Save the form.

You must enable at least one parameter for source tracking to take effect. Disabling source tracking clears the parameter list when the form is saved.

Suggested parameters

ParameterPurpose
utm_sourceSite, search engine, or newsletter that sent the traffic
utm_mediumMarketing medium or channel (e.g. cpc, email, social)
utm_campaignCampaign or promotion name
utm_termPaid search keywords
utm_contentDifferentiates ads or links on the same URL
fbclidFacebook Ads click ID
gclidGoogle Ads click ID
gbraidGoogle web-to-app click ID (iOS)
wbraidGoogle app-to-web click ID (iOS)
msclkidMicrosoft (Bing) Ads click ID
ttclidTikTok Ads click ID
li_fat_idLinkedIn Ads first-party tracking ID

Viewing results

Individual responses

Open Individual Responses and select a submission. When source tracking is enabled for the form:

  • A Source Tracking tab shows configured parameters and their captured values
  • The response sidebar includes a Source Tracking section when data was captured

Filtering

On Summary Report, Audience Overview, and Individual Responses, a Source Tracking filter category appears when the form has source tracking enabled with at least one parameter. Filter by conditions such as:

  • utm_source Equals google
  • utm_campaign In spring_sale, product_launch

Supported operators for source tracking filters: Equals and In.

Export

When exporting individual responses, include the Source tracking column group to export captured parameter values.

Example

A landing page URL:

https://app.example.com/pricing?utm_source=google&utm_medium=cpc&utm_campaign=q2_promo&gclid=abc123

If the form tracks utm_source, utm_medium, utm_campaign, and gclid, a submission stores:

KeyValue
utm_sourcegoogle
utm_mediumcpc
utm_campaignq2_promo
gclidabc123

Parameters present in the URL but not configured for the form are ignored. Configured parameters missing from the URL are stored as empty for that response.

Was this page helpful?