Blog Posts

Tally Forms + SourceTrack Track UTMs & AI Referrals on Tally Forms Capture full multi-touch attribution on every Tally submission without adding hidden fields or writing custom postMessage scripts. 1-Minute Setup Zero Hidden Fields <!-- 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: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. 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. 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 timestampStep-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 T Alex Smith NEW TALLY LEAD alex.smith@example.com · Submitted via Tally Form Just now Attribution Journey Timeline 🔍 Google Ads (First Touch) → 🤖 ChatGPT Assisted → 📋 Tally Form Conversion Source / Medium google / cpc Campaign summer_promo Click ID gclid_982347 Landing Page /pricingComparison: Traditional Hidden Fields vs. SourceTrackCapability Traditional Hidden Fields SourceTrack First-Party AttributionSetup Time 30+ minutes per form 2 minutes (1 script tag)Requires Tally Hidden Fields Yes NoMulti-Page Persistence ❌ Drops UTMs on page navigation ✓ Retains full session journeyiFrame Embed Compatibility ❌ Fails without postMessage JS ✓ Native automatic captureAI Referral Tracking ❌ Fails (No UTM on AI referrers) ✓ Auto-classifies ChatGPT & PerplexityCookie Consent Dependency Depended on 3rd party cookies First-party only; Cookieless Mode optional (paid plans)Supported Integrations & Form Builders SourceTrack automatically detects submissions from Tally Forms as well as 25+ form builders and CRMs out of the box: Tally Forms Typeform Webflow Forms HubSpot Forms Jotform WPForms Gravity FormsFrequently 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. Attribute every lead back to its true source Install SourceTrack in 2 minutes with one script tag. See your first attributed Tally Form submission today. Start 28-day free trial → No credit card required · 1-line script tag install · First-party tracking

When potential customers ask ChatGPT, Claude, Perplexity, or Gemini for product recommendations, the visit that follows is easy to label and hard to value. Labelling it got easier in May 2026, when Google Analytics 4 added an AI assistant channel (medium=ai-assistant). It recognises ChatGPT, Gemini, DeepSeek, Copilot and Grok from the referrer. If you use GA4 and you have wondered whether you already have this covered: for those five, with a referrer present, you largely do. Three gaps remain, and they are the ones that decide budget. Where the Channel Label Runs Out It does not cover every engine. GA4's AI assistant channel excludes Perplexity, and it does not separate Google's own AI Overviews or AI Mode — those arrive with a google.com referrer and read as organic search. (For transparency: SourceTrack does not separate AI Overviews or AI Mode either. Nobody can, from the referrer alone.) It is forward-only. GA4 does not reclassify history. Sessions that landed before the change stay in whatever bucket they were given, permanently. It is a label on a session, not a line on a journey. This is the one that matters. GA4 is session-scoped: a visitor who finds you through ChatGPT in week one and buys in week four arrives as a new session with no memory of the first. The channel gets a label; the order does not get a source. There is no revenue-to-journey join in the product at all. Traditional analytics also relies on the HTTP Referer header, and modern LLM interfaces and mobile chat apps often strip it. That part is genuinely unrecoverable — by anyone. When a referrer is absent and no UTM is present, the visit is indistinguishable from someone typing your address in, and it belongs in Direct. No tool can recover it without inventing a source. The SourceTrack Approach to AI Attribution SourceTrack matches the referrer host and any campaign parameters against a named list of assistants, with no third-party cookies and no device fingerprinting.Named referrer matching: The referrer host and UTM source are matched against 16 named assistants and answer engines on arrival — a fixed list, not a guess. First-Touch Stitched Timeline: Preserves the originating AI discovery channel across subsequent visits before purchase. Revenue Attribution: Connects Stripe purchase webhooks and Shopify orders directly to the initial AI referral touchpoint.By filling the dark traffic gap, growth teams get clear visibility into which specific AI search platforms drive real enterprise pipeline and recurring revenue.

Privacy regulations and browser enforcement (Safari ITP, Firefox ETP, Chrome Privacy Sandbox) have rendered traditional third-party tracking scripts obsolete. For SaaS founders, relying on third-party cookies results in broken visitor timelines and double-counted conversions. The Problem with Traditional Trackers Legacy attribution platforms attempt to work around privacy restrictions using invasive browser fingerprinting or third-party cookies. These approaches create severe compliance risks under GDPR Art. 15/17 while routinely getting blocked by modern ad-blockers and privacy extensions. First-Party Architecture SourceTrack's first-party model isolates tracking within your own domain boundary:Zero Third-Party Cookies: No cross-site identifier is ever set. The standard tracker keeps its anonymous id in first-party localStorage, on your own domain. Cookieless Mode, on paid plans: A setting you switch on, off by default. With it enabled the tracker writes nothing to the visitor's device at all. No Device Fingerprinting: Never reads canvas hashes, fonts, or hardware telemetry, and never stores a raw IP address. DNT and GPC Honoured: Respects Do-Not-Track (DNT) and Global Privacy Control (GPC) headers out of the box, on every plan.This privacy-first foundation ensures reliable attribution data without sacrificing compliance or customer trust.