Meta Conversions API setup for Jotform
Same shape as Typeform. fbclid prefilled in, returned on the webhook, used with the submission ID as event_id.
Free30 minutesNo obligation
Jotform + Meta CAPI · 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 + Meta CAPI · the fix
What changes — Jotform + Meta CAPI
Click IDs prefilled and returned
Via the webhook.
Conversions bound to real submission
Per embed variant.
Server-side submissions
From the webhook.
Jotform + Meta CAPI · architecture
How Meta tracking behaves on Jotform
Prefill and webhook, same as any embedded form.
- 1
fbclid prefilled
The only route into an iframe or hosted form.
- 2
Lead from the submission event
Browser-side where available.
- 3
CAPI from the webhook
Server-side, deduplicated.
- 4
Submission ID as event_id
Shared by both paths.
- 5
Customer data from the submission
Normalized before hashing.
Jotform + Meta CAPI · 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 + Meta CAPI · prove
The QA evidence — Jotform + Meta CAPI
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 + Meta CAPI · 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 + Meta CAPI · 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 + Meta CAPI · what we deliver
What gets built for Meta on Jotform
A shared event ID on both paths
The Jotform submission ID, available on the submission event and the webhook.
Standard event names, exactly cased
Meta matches on name and ID together, so a case difference alone produces two events.
Customer data normalized then hashed
Lowercase and trimmed email, phone in E.164. This is where nearly every low match quality score comes from.
fbc and fbp forwarded from the browser
fbc only exists if fbclid was captured on landing — a very common gap.
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 + Meta CAPI questions, answered
Prefilled when the form loads. An iframe or hosted form has no other route.
The Jotform submission ID.
For offline outcomes or blocker resistance, yes. The webhook makes it straightforward.
Inline on your own domain, because it avoids the cross-origin constraint entirely.
Free · 30 min
Get Pixel and CAPI counting once on Jotform
WhatsAppFree30 minutesNo obligation
