Skip to content

How to Capture Google Analytics Data in Jotform

Jotform collects what a lead types into a form. It does not, on its own, know whether that lead arrived from a paid search ad, an organic result, a social post, or a referral. This guide shows how to close that gap: add hidden fields to your Jotform forms, have an attribution layer populate them with channel and landing-page context, and then pass the combined record into your CRM or other connected tools so you can report on leads, opportunities, customers, and revenue by source.

Why put marketing context inside the form?

Analytics tools are good at describing the journey up to your site. They can show which entry paths produced visits and, when goals are configured, which of those paths produced form fills. The blind spot appears after the form: a lead record in a CRM rarely knows which entry path created it, so revenue and deal outcomes sit in a separate system from the source that generated them. Embedding source context in the submission itself changes that. Every lead arrives downstream already labeled with its origin, which lets you rank channels by closed revenue rather than by traffic or raw lead count. The practical benefit is a budget conversation grounded in outcomes: you can see which sources repay their cost in deals and which only add volume.

The four-step setup

The workflow has four stages. First, add hidden fields to your Jotform lead forms. Second, let an attribution layer fill those fields with the visitor's channel and landing-page data. Third, submit the form so Jotform stores the typed answers and the hidden values together. Fourth, send the record to your CRM or other connected tools and report on it. Each stage is described below with the specific field names and Jotform controls involved.

Step 1: Add the hidden fields

Create one hidden field for each piece of attribution data you want to keep. The field names used in this setup are: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. In Jotform, drag a Short Text field into the form, open its properties, and switch on Hide Field. The field remains part of the form's data structure but is not shown to the visitor, so the visible form behaves as before while providing slots for the attribution values.

Field and control map

Use this map to keep the Jotform field names aligned with the values the attribution layer writes and with the properties you set in Jotform.

Step 2: Let the hidden fields fill automatically

Once the hidden fields exist, the attribution layer populates them for each visitor based on how that visitor arrived. It uses signals such as UTM parameters and the HTTP referrer, groups the visitor into a channel category, and saves the result in the browser. When the visitor later opens and submits a form, those saved values are written into the hidden fields. Consider a paid-search example: a visitor searches for help sharing large files, clicks a paid ad, and lands on a features page. Depending on the UTM parameters used, the hidden fields might receive Channel: Paid Search; Channel Drilldown 1: Google; Channel Drilldown 2: Brand Campaign; Channel Drilldown 3: Dropbox; Landing Page: the features/share URL; and Landing Page Group: Features. The exact drilldown values depend on how the campaign URLs are tagged.

Step 3: Submit the form and store the record

On submission, Jotform captures the visitor's typed answers — name, email, phone, and any other fields — together with the values that were written into the hidden fields. The result is a single submission record that contains both the contact details and the marketing context. This is the handoff point: from here, the record can be sent to a CRM or any other tool connected to Jotform.

Step 4: Report on outcomes, not just leads

Send the submission data into your CRM — for example Salesforce, Zoho, or Pipedrive — or into other connected tools. With channel and landing-page data attached to each lead, you can review which channels drive the most leads, compare conversion rates to deal or opportunity stage by channel, count closed-won deals by channel, measure revenue by channel or campaign, and calculate the return on each marketing initiative. The value comes from connecting the top of the funnel to the bottom.

What data the hidden fields carry

Two categories of attribution data matter most here. The first is marketing channel: how the visitor arrived, such as Organic Search, Paid Search, Paid Social, or Referral. Channel data is provided for all leads, not only those from paid campaigns with UTM parameters. For paid channels, further detail can be passed through depending on how the UTM parameters are set — for example campaign, ad group, or ad. The second category is landing-page data: the first page the lead saw on your site and the category that page belongs to, such as blog or features. Grouping pages by category lets you see total leads from an entire section, then drill down to individual pages.

Three reports worth building

Each of these reports answers a different budget question, and each depends on the hidden fields being populated and the records reaching the CRM intact.

Leads by channel answers "where is volume coming from?" It counts leads per month, grouped by source channel. Read it as a starting point, not a verdict: a channel can lead on volume while lagging on revenue, so pair it with the outcome reports below before shifting spend.

Opportunities by Google Ads campaign answers "which campaigns produce leads sales actually works?" It counts opportunities per month, grouped by the campaign that produced the originating lead. A campaign that generates many leads but few opportunities is a signal to inspect targeting or qualification rather than to scale spend.

Customers by Facebook ads network answers "which placement converts?" When ads run across the Facebook family — Instagram, Messenger, and WhatsApp alongside the main feed — performance often differs by network. Counting customers per network shows where the acquisition budget earns its keep, rather than treating all Facebook placements as one channel.

Setup checklist

Before you rely on the data, confirm each of the following. The six hidden fields exist on every lead form you want to track. Each field is a Short Text field with Hide Field switched on. The attribution layer is installed on the site and can write to those field names. A test submission shows the expected channel and landing-page values in the Jotform submission record. The CRM or connected tool maps each hidden field to a matching property or field. Your reports group by the channel and landing-page fields rather than by free-text notes. If any step is missing, the submission will still arrive, but the attribution columns will be empty or inconsistent.

Two different failures to watch for

A missing value and a wrong value are not the same problem. If the hidden fields are empty on a submission, the likely cause is that the attribution layer did not write to them — perhaps the field names do not match, or the script is not present on the page where the form was submitted. If the fields contain values but the channel looks incorrect, the likely cause is the tagging: UTM parameters that do not follow your naming convention, or a referrer that the attribution layer categorizes differently than you expected. Checking a test submission against the URL you used is the quickest way to tell which failure you are looking at.

Frequently asked questions

Do I need to add hidden fields to every Jotform form?

Add them to the forms you use for lead capture — contact, quote request, demo request, and similar. Forms that do not collect leads do not need attribution fields.

Will visitors see the hidden fields?

No. A Short Text field with Hide Field switched on is not displayed to the visitor. The visible form looks and behaves as it did before.

Does channel data only arrive for paid campaigns?

No. Channel data is provided for all leads, including organic search, referral, and other non-paid sources. Paid campaigns can supply additional drilldown detail depending on how their UTM parameters are set.

What is the difference between Landing Page and Landing Page Group?

Landing Page records the first page the lead saw, such as a specific blog post URL. Landing Page Group records the category that page belongs to, such as blog or features. The group lets you report on a whole section, then drill into individual pages.

Can I send the captured data to a CRM?

Yes. Jotform submissions can be sent to connected tools, including CRMs such as Salesforce, Zoho, and Pipedrive. The hidden-field values travel with the submission, so the CRM record can carry the channel and landing-page context.