Server-side tracking for Jotform
The webhook is the reliable source — it fires on submission with every field, including whatever you prefilled. That's the mechanism for getting a click ID from your landing page into a server-side conversion.
Free30 minutesNo obligation
Jotform server-side · what breaks
What goes wrong on Jotform
- 01
Three embed variants with different behaviour
Iframe, inline and hosted each track differently.
- 02
Iframe and hosted can't read your URL
So the click ID must be prefilled.
- 03
Prefill fields declared but empty
Existing is not the same as populated.
- 04
Partial submissions
Jotform can save incomplete responses.
Jotform server-side · the fix
What changes — Jotform server-side
Click IDs prefilled and returned
Via the webhook.
Conversions bound to real submission
Per embed variant.
Server-side submissions
From the webhook.
Jotform server-side · architecture
What Jotform exposes to a server container
Prefill in, webhook out.
- 1
Prefill populated on load
Click IDs written into the form.
- 2
Webhook as the server-side event
Returning every field.
- 3
Submission ID as the deduplication key
Stable and unique.
- 4
Customer data from the submission
Normalized then hashed.
- 5
Browser event deduplicated
Both paths, one conversion.
Jotform server-side · diagnose
Where Jotform tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Identify the embed variant per page
Iframe, inline or hosted.
- 02
Submit a test from a tagged click
Check prefilled values in the submission.
- 03
Confirm the submission event is bound
Per variant.
- 04
Check whether the webhook is configured
Often not.
- 05
Reconcile submissions against your CRM
For a closed month.
Jotform server-side · prove
The QA evidence — Jotform server-side
Run on Jotform specifically, on a live conversion rather than in preview mode.
Source of truth
your Jotform submission records
- Click identifiers confirmed present in a live submission.
- Each embed variant in use tested with a real submission.
- Webhook confirmed delivering every field.
- Submission ID confirmed as the deduplication key.
- Submissions reconciled against CRM records for a closed month.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Jotform server-side · free audit
What we check in the free audit
- Identify the embed variant per page
- Submit a test from a tagged click
- Confirm the submission event is bound
- Check whether the webhook is configured
- Reconcile submissions against your CRM
Checked against
your Jotform submission records
Free30 minutesNo obligation
Jotform server-side · when not to buy
When you don't need this on Jotform
Worth reading before you buy anything, from us or anyone.
- If your submissions already carry click IDs, the hard part is done.
- Prefill is well documented and a developer can wire it quickly.
- If you only use the inline embed on your own domain, the iframe constraint doesn't apply to you.
- Check one live submission for prefilled values before assuming anything is broken.
Jotform server-side · what we deliver
What the server-side build gives you on Jotform
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from Jotform submissions
Jotform's webhook, firing on submission with every field including prefilled values.
Deduplicated at every destination
On a shared event ID, verified before any existing path is removed.
Consent enforced before dispatch
A denied destination receives nothing, verified by capture rather than configuration.
Written guarantee
95%+ tracking accuracy
Measured against your Jotform submission records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Jotform server-side questions, answered
Jotform's webhook, firing on submission.
No — the webhook fires the same way. It matters for the browser-side event and for prefill.
The submission ID.
Somewhere to receive the webhook.
Free · 30 min
Move Jotform events off the browser
WhatsAppFree30 minutesNo obligation
