Skip to content

Track Jotform submissions as conversions in Google Analytics without code

Google Analytics shows visits and traffic sources well, but it will not count a form submission as a conversion until you send it a custom event. This guide explains a no-code workflow for sending that event whenever a Jotform is submitted, how to verify it, how to mark it as a Key Event in GA4, and how to use the data to judge channel, Meta Ads network, and Google Ads campaign performance.

Why a no-code workflow is simpler

A standard Google Tag Manager route can work, but it requires variables, tags, triggers, and data layer knowledge. A workflow builder offers a simpler alternative: connect the form submission as the trigger and Google Analytics as the destination, without writing code.

Use this checklist before you start:

  • Confirm Google Analytics is already installed on the pages containing your Jotform embeds.
  • Decide the event name you will use, for example form_submit, and use it consistently.
  • Have access to add a small site snippet if your chosen workflow tool requires it.
  • Plan a test submission from a private or incognito window so cached sessions do not confuse verification.

Four steps to send Jotform submissions to Google Analytics

Step 1: Install the workflow tool on your website. Sign up, then add the provided code to your site, usually through the settings or header area of your website builder.

Step 2: Build the flow. Inside the tool, create a workflow, choose a Jotform submission as the trigger, and add an action to send a conversion event to Google Analytics. The builder pattern is similar to automation tools such as Zapier or HubSpot: trigger first, then one or more actions.

Step 3: Test it. Open the form page in an incognito window, submit a test entry, then check Google Analytics Realtime Overview and Recent Events. You should see the event name you chose. If it appears, the trigger and destination are connected.

Step 4: Mark it as a Key Event in GA4. Go to Admin, then Events under Data Display, open Recent Events, find your form event, and select the star icon. GA4 then treats it as a conversion for acquisition, funnel, and path reporting. New events can take a few hours to appear in Recent Events, so wait before assuming setup failed.

What this approach gives you, and how to troubleshoot

Advantages of the workflow approach:

  • Setup is visual rather than tag-manager based, with fewer technical concepts to learn.
  • The same workflow can send conversions to additional platforms by adding another action step.
  • Support is available from the workflow provider for connecting analytics and advertising tools, unlike direct support from large advertising platforms.

Failure distinction to check: if no event appears in Realtime, work backwards in order. First confirm the test submission actually completed, then confirm the site snippet is present on that page, then confirm the workflow is active and the trigger matches that specific form, and finally confirm the Google Analytics destination and event name.

Go further: capture attribution data with each submission

Counting submissions in aggregate is only the first layer. It does not tell you whether an individual lead was qualified, became a customer, or generated revenue. Capturing attribution data with each submission closes that gap.

How it works: a small site script identifies how a visitor arrived, using signals similar to those Google Analytics uses, classifies the visit into a channel such as Organic Search, Paid Search, or Paid Social, stores that information in the browser, and then populates hidden fields in the Jotform. On submission, the attribution data travels with the entry and can be viewed in the entries table, added to email notifications, passed to a CRM, or exported to a spreadsheet.

That per-lead record lets you report leads by channel, see which campaigns drive customers, and estimate revenue by advertising source, rather than relying only on aggregate conversion counts.

Three reports to run after setup

  1. Conversions by Channel: Compare form submissions across Organic Search, Paid Search, Paid Social, Organic Social, and other channels. Use it to spot which channels deliver leads and which need attention.
  1. Conversions by Meta Ads Network: If Meta campaigns run across Facebook, Instagram, Messenger, and WhatsApp, break conversions down by network to see where budget is working hardest and where to scale back.
  1. Conversions by Google Ads Campaign: Separate product, general, and branded campaigns so you can see which campaigns produce submissions and which only consume budget. Double down on the former and reduce the latter.

Decision example: if Paid Search produces many submissions but few become customers, the issue may be lead quality or landing-page fit rather than traffic volume. Per-submission attribution data helps you test that distinction.

Wrap up

Once the event is flowing and marked as a Key Event, GA4 can include form submissions in acquisition, funnel, and path analysis. Adding per-submission attribution data then connects those submissions to individual leads, customers, and revenue in downstream tools. Start with the basic event, verify it with a test submission, and expand reporting only after the event is reliably recorded.