Lead source tracking in Jotform.
Find which campaigns and pages actually drive the leads you receive through Jotform.
Works with every Jotform format
Jotform has the pieces. Assembling them is the work.
Jotform has all the right ingredients available. Widgets that grab the page URL, widgets that grab the referrer, prefill via URL parameters, webhooks that POST submissions onward. The catch is that every piece is opt-in, configured per form individually, and tied to Jotform’s own field IDs and payload shape.
Widgets and webhooks, à la carte
- “Get Form Page URL” widget
- “Referrer URL” widget
- URL-parameter prefill (per field)
- Webhooks with rawRequest payload
- 100+ direct integrations to CRMs & tools
Per form, per integration
- Add the URL widget. Add the referrer widget. Per form.
- Persist UTMs across navigation before they hit the form
- Map the widget output into your CRM’s schema
- Parse Jotform’s rawRequest payload to extract values
- Turn raw URLs & UTMs into actual campaign names
The widget-per-form approach, and what it actually involves.
The standard Jotform attribution recipe involves four things. A Get Form Page URL widget. A Referrer URL widget. Per-field URL prefill for UTMs. And either a CSV export at month-end or a custom webhook receiver to interpret the output. It works, but it asks for ongoing maintenance from whoever owns the forms.
The manual way
- 01Open each form in the Jotform builder. Search the widget library for Get Form Page URL and Referrer URL. Add both. Set them to hidden. Repeat for every form.
- 02Add hidden short-text fields for
utm_source,utm_medium,utm_campaign. Name each to match the URL parameter that’ll prefill it. - 03Build a UTM-persistence solution outside Jotform. Jotform prefill only reads the URL when the form page loads. If the visitor clicks an ad to your homepage and navigates to the contact page before submitting, the URL is clean.
- 04To get this into your CRM: configure a webhook, point it somewhere that can parse Jotform’s
rawRequestpayload, and map each field onto your CRM’s schema.
With Lead Source
- 01Paste one webhook URL into Settings → Integrations → Webhooks. Once per form.
- 02We receive every Jotform submission, attach source & campaign & full page journey, and surface it in your dashboard and inbox.
- 03Source captured at submission with cross-page UTM persistence already handled. Written out: “Google Ads · Local Services Sydney”, not raw UTM strings.
- 04No widgets to add. No fields to map. No
rawRequestparser to maintain.
Most Jotform attribution work involves adding Get Form Page URL widgets to every form, then debugging why values don’t show up where you expected. The webhook path skips that.
One webhook URL. That’s the whole thing.
Sign up, copy your unique webhook URL from the dashboard, paste it into Jotform’s webhook settings. We receive every submission and attach the source automatically. The block below shows what the URL looks like, with placeholder text where your account ID will be.
# illustrative. Paste your real webhook URL from app.leadsource.co https://hooks.leadsource.co/[your-account-id]
The real webhook URL is generated for your account when you sign up. Copy it from the integrations page in your dashboard. Async delivery, retries on failure, signed payloads.
Three steps. Done in five minutes.
Sign up and get your webhook URL
Create your free Lead Source account. You’ll see a webhook URL on the integrations page with your unique account ID already in it. Copy it.
Add the webhook in Jotform settings
Open your form in the Jotform builder. Go to Settings → Integrations → Webhooks → Add Webhook. Paste your Lead Source webhook URL. Save. That’s the whole setup.
Submit a test through your Jotform form
Open your form. Fill it in. Submit. Within a minute or two, the lead appears in your Lead Source dashboard with the source, campaign, and page journey attached. Email notification arrives alongside.
?utm_source=test appended to the URL before submitting. That’ll be the source on the lead.Questions, answered.
Will this conflict with my existing Jotform integrations?
No. Jotform supports multiple webhooks per form. Add the Lead Source webhook URL and your existing integrations (Mailchimp, HubSpot, Salesforce, Zapier, Google Sheets, etc.) keep working exactly as configured. We don't modify the submission. We receive a copy of it.
Does it work with both hosted Jotform forms and embedded Jotform forms?
Yes. The webhook fires at the Jotform-server level when a submission is received, so it doesn't matter whether the form was filled on jotform.com or embedded on your own site. Both paths reach us. Hosted forms are actually where webhook install shines: the page-on-your-site is jotform.com's, so a script tag can't see the submission.
Do I need a paid Jotform plan?
No. Webhooks are available on Jotform's free tier and on every paid tier. The Jotform-side limit you might encounter is the monthly form-submission cap on lower tiers, which is set by Jotform's own pricing and is separate from Lead Source.
Does the webhook slow down my form submission?
No. Jotform fires webhooks asynchronously after returning the success response to your form visitor. From the submitter's perspective, nothing changes. From your perspective, the Lead Source notification typically arrives within 1–3 seconds of the submission.
What about Jotform's Card forms. The one-question-at-a-time UI?
Works the same way. Card forms still emit a single submission webhook at the end of the flow. We receive it with all the fields the visitor filled in across all the cards, plus the source data we've been building up.
Track your Jotform leads. Free to start.
One webhook URL is configured once, in Jotform’s integration settings on each form (or applied across all forms via the API). Source, campaign, and page journey arrive on every submission. No widgets to add, no rawRequest payload to parse on your side.
Start freeFree to start · no card