How to Track UTM Parameters in Tally Forms (Step-by-Step Guide)

<!-- Right: Before vs After Lead Payload Mockup Card -->
<div class="md:col-span-7">
  <div class="grid grid-cols-1 sm:grid-cols-2 gap-3">
    <!-- Without SourceTrack -->
    <div class="p-4 rounded-2xl bg-white/80 border border-red-200/80 shadow-2xs">
      <div class="flex items-center justify-between mb-3">
        <span class="text-[10px] font-bold text-red-600 uppercase tracking-wider">Without SourceTrack</span>
        <span class="px-2 py-0.5 rounded bg-red-100 text-red-700 text-[9px] font-black">UNTAGGED</span>
      </div>
      <div class="space-y-2 text-xs">
        <div class="flex justify-between border-b border-stone-100 pb-1">
          <span class="text-stone-400 font-medium">Source:</span>
          <span class="text-red-500 font-bold">Direct / Unknown</span>
        </div>
        <div class="flex justify-between border-b border-stone-100 pb-1">
          <span class="text-stone-400 font-medium">Medium:</span>
          <span class="text-red-500 font-bold">(none)</span>
        </div>
        <div class="flex justify-between border-b border-stone-100 pb-1">
          <span class="text-stone-400 font-medium">Campaign:</span>
          <span class="text-red-500 font-bold">Not captured</span>
        </div>
        <div class="flex justify-between">
          <span class="text-stone-400 font-medium">AI Referral:</span>
          <span class="text-red-500 font-bold">Invisible</span>
        </div>
      </div>
    </div>

    <!-- With SourceTrack -->
    <div class="p-4 rounded-2xl bg-white border-2 border-[#CCF03F] shadow-md relative overflow-hidden">
      <div class="flex items-center justify-between mb-3">
        <span class="text-[10px] font-extrabold text-stone-900 uppercase tracking-wider">With SourceTrack</span>
        <span class="px-2 py-0.5 rounded bg-[#CCF03F] text-[#111827] text-[9px] font-black">AUTO-TAGGED</span>
      </div>
      <div class="space-y-2 text-xs">
        <div class="flex justify-between border-b border-stone-100 pb-1">
          <span class="text-stone-400 font-medium">Source:</span>
          <span class="text-stone-900 font-bold">Google Ads</span>
        </div>
        <div class="flex justify-between border-b border-stone-100 pb-1">
          <span class="text-stone-400 font-medium">Medium:</span>
          <span class="text-stone-900 font-bold">cpc</span>
        </div>
        <div class="flex justify-between border-b border-stone-100 pb-1">
          <span class="text-stone-400 font-medium">Campaign:</span>
          <span class="text-stone-900 font-bold">summer_promo</span>
        </div>
        <div class="flex justify-between">
          <span class="text-stone-400 font-medium">AI Referral:</span>
          <span class="text-emerald-600 font-bold">ChatGPT Assisted</span>
        </div>
      </div>
    </div>
  </div>
</div>

Tally Forms is one of the cleanest, fastest form builders for modern startups. However, if you rely on standard hidden fields to capture UTM parameters (utm_source, utm_medium, utm_campaign), you will quickly discover severe attribution gaps:

1. iFrame Data Loss: When Tally is embedded via an iFrame, parent page URL parameters fail to pass into the form without complex custom JavaScript postMessage scripts.
2. Multi-Page Drops: If a visitor lands on a blog post or homepage from a Google Ad or LinkedIn Ad (?utm_source=linkedin), then navigates to your contact page, the URL parameters disappear.
3. Ad Blocker Interception: Third-party tracking scripts fail to capture submit events when blocked by privacy extensions.

In this guide, we will show you how SourceTrack solves Tally Forms UTM tracking in under 2 minutes — with zero hidden fields to configure.

The Solution: First-Party Session Attribution

Instead of relying on fragile URL hidden fields inside Tally, SourceTrack captures the visitor’s initial touchpoint on your domain and holds the attribution state in first-party session storage.

When the visitor submits your Tally form, SourceTrack automatically links the submission to the visitor’s complete discovery journey — including:

• UTM Parameters: utm_source, utm_medium, utm_campaign, utm_content, utm_term
• Ad Click IDs: gclid (Google Ads), fbclid (Meta Ads), msclkid (Bing Ads), li_fat_id (LinkedIn Ads)
• AI Search Engines: Organic referral discovery from ChatGPT, Claude, Perplexity, and Gemini
• Landing Page & Entry Path: First page viewed, referrer URL, and timestamp

Step-by-Step Setup Guide

Step 1: Install the SourceTrack Async Script Tag

Copy your workspace script tag from the SourceTrack dashboard and paste it into the <head> section of your website:

<script 
  src="https://api.srctk.com/tracker.min.js"
  data-site-key="YOUR_SITE_KEY" 
  async>
</script>

Note: SourceTrack uses a lightweight, first-party tracker script (< 3KB) that loads asynchronously without slowing down page rendering or LCP.

Step 2: Embed Your Tally Form

Embed your Tally form into your website using standard Tally embed code or iFrame snippet. You do not need to add any hidden fields (utm_source, etc.) inside the Tally editor!

<iframe 
  data-tally-src="https://tally.so/embed/wL5vKk?alignLeft=1&hideTitle=1" 
  loading="lazy" 
  width="100%" 
  height="400" 
  frameborder="0" 
  title="Contact Form">
</iframe>

Step 3: Test a Live Submission with UTM Parameters

Open an incognito browser window and visit your website with test UTM parameters attached:

https://yourdomain.com/contact?utm_source=google&utm_medium=cpc&utm_campaign=summer_promo&gclid=test_click_id

Fill out and submit your Tally form.

Step 4: View the Attributed Lead in SourceTrack

Comparison: Traditional Hidden Fields vs. SourceTrack

Supported Integrations & Form Builders

SourceTrack automatically detects submissions from Tally Forms as well as 25+ form builders and CRMs out of the box:

Frequently Asked Questions

Do I need to modify my existing Tally Forms?

No. SourceTrack detects submissions on your website automatically. Your existing Tally form fields and email notifications remain completely untouched.

What happens if a visitor arrives from ChatGPT or Claude without UTMs?

SourceTrack automatically inspects referrer headers and session origin patterns to classify organic AI search referrals (ChatGPT, Perplexity, Claude, Gemini) and attributes the lead to the exact AI assistant that generated the visit.

How does SourceTrack handle GDPR and CCPA obligations?

SourceTrack operates on a first-party visitor model. It never sets third-party tracking cookies and never performs browser fingerprinting, and it honours Do Not Track and Global Privacy Control. Cookieless Mode — a setting available on paid plans — writes nothing to the visitor’s device at all. Compliance itself is a property of your deployment and your agreements rather than of a tracker, so we publish a DPA and a subprocessor list instead of claiming certification on your behalf.

Start Tracking UTM Parameters on Tally Forms Today

Stop losing lead attribution data to iFrame drops and missing UTM fields.