Skip to content

How to capture Google Ads data in Forminator forms

A Forminator form tells you who enquired. It rarely tells you which ad brought them there. This guide walks through wiring Google Ads campaign data into every submission, so a lead record can carry its campaign, ad group, keyword, ad and original landing page alongside the name and email the visitor typed.

What you are actually building

The goal is a form submission that answers two questions at once: who is this lead, and what marketing brought them here? Forminator already handles the first. The second comes from UTM parameters attached to your ad URLs, carried into the form through hidden fields, and stored with the submission.

Four moving parts have to line up: tagged ad URLs, hidden fields on the form, a mechanism that writes visitor source data into those fields, and a destination where the combined record is useful. Skip any one and the chain breaks quietly — the form still submits, it just arrives with blanks.

Step 1: tag your Google Ads URLs with UTM parameters

UTM parameters are extra text appended to the URL you send people to. Analytics and attribution tools read them to work out where a visitor came from. Take a destination page and append medium, source, campaign, term and content values.

A worked example from the guide: if the page is https://roipaths.com/integrations/forminator, the tagged URL becomes https://roipaths.com/integrations/forminator? utm_medium=paidsearch & utm_source=google & utm_campaign=brand-campaign.

A consistent convention is what makes reports readable later. The recommended mapping is:

  • UTM Medium = Paid search
  • UTM Source = Google
  • UTM Campaign = the name of your Google Ads campaign
  • UTM Term = the name of the ad group the ad belongs to
  • UTM Content = the specific ad

You can put whatever you like in these values, but pick a scheme and keep it. Google Ads tracking templates make it quicker to apply the same pattern across many ads.

Step 2: create the hidden fields in Forminator

Hidden fields sit on the form but are invisible to visitors. They exist so a tool can write values into them without the person filling anything in. Add these six to the form:

  • Channel
  • Channel Drilldown 1
  • Channel Drilldown 2
  • Channel Drilldown 3
  • Landing Page
  • Landing Page Group

Forminator's interface makes adding hidden fields straightforward; the platform's own documentation covers the clicks. The important part is spelling the field names exactly as above, because the capture tool writes to those names.

Step 3: let the capture tool fill the fields

Once the fields exist, the capture tool identifies where each visitor came from and writes that into the hidden fields. The values depend on what you put in your UTM parameters.

Using the example campaign above, a visitor arriving from that ad would produce:

  • Channel = Paid search
  • Channel Drilldown 1 = Google
  • Channel Drilldown 2 = Brand campaign
  • Channel Drilldown 3 = Free account ad

Beyond the UTM values, the tool also records the visitor's first landing page (for example, a features/notifications page) and the first landing page group (for example, features). That second pair is what lets you report at section level rather than page by page.

Step 4: use the data where decisions get made

On submit, Forminator stores the Google Ads values together with the lead's name, email and other answers. From there you have four practical destinations:

  1. Read individual records in the Submissions area of the WordPress dashboard.
  2. Include the fields in the new-lead notification email, so the source is visible in your inbox.
  3. Push the values into a CRM such as Pipedrive, Salesforce or HubSpot, so sales sees origin on the record.
  4. Aggregate them into reports showing which campaigns produce leads, customers and revenue.

Option 1 is fine for spot checks. Options 2 and 3 are what make the data survive contact with a sales team. Option 4 is where the setup pays for itself.

Field map: what each hidden field holds and what it is for

Use this map when building the form and when designing reports. Each row pairs a field with the value it receives and the question it answers.

The failure mode that matters: same-page-only capture

Some capture methods only work when the form is completed on the exact page the visitor first landed on. Consider a visitor who clicks an ad, arrives on your pricing page, clicks a demo button, and submits the form on a separate demo request page. Because the landing page and the form page differ, the UTM parameters are gone by the time the form is filled in.

A cookie-based approach behaves differently: the UTM values are stored in the visitor's browser, so they are still available whichever page the form lives on. If your forms are not on your ad landing pages — and most are not — this distinction decides whether your reports contain data or blanks.

Why capture every channel, not just paid search

A tool that only reads Google Ads parameters gives you a partial picture. Capturing organic search, organic social and paid social as well means every lead has a source, which changes what you can conclude.

If most leads arrive from organic search while most budget goes to paid search, that gap is a budgeting signal worth acting on. A leads-by-channel view is only possible when non-ad traffic is captured too.

Three reports worth building first

Once submissions carry source data into a spreadsheet or CRM, three reports give the fastest read on performance:

  • Leads by channel — how many leads each channel produces, which shows where demand actually originates.
  • Customers by Google Ads campaign — how many customers each campaign delivers, which shows which campaigns deserve continued investment.
  • Revenue by keyword — how much revenue each bid-on keyword generates, which shows which keywords are profitable and where higher bids might win more impression share.

Start with the channel report to sanity-check that capture is working at all, then move to campaign and keyword views once volume builds.

Pre-launch checklist

Before you trust a single report, confirm each item:

  • Every Google Ads final URL or tracking template carries the same UTM naming convention.
  • All six hidden fields exist on the form and are spelled exactly as listed.
  • A test click from a real ad produces populated hidden fields on submission.
  • The fields appear in the notification email and in whatever CRM record the form creates.
  • A test submission from a non-ad channel still records a source rather than a blank.
  • Your reporting tool groups by the same field names the form uses.

If a submission arrives with empty source fields, work backwards: check the URL tag first, then the hidden field names, then whether the visitor navigated between landing and form pages.

Getting started

The setup is short: tag the ads, add six hidden fields, let the capture tool populate them, and route the results somewhere useful. Before committing to a tool, check its current trial length, free-tier limits and typical setup time directly with the provider, since these terms vary and change. Then run one test submission from a real ad click to confirm the fields populate as expected.

Forminator hidden field map
Hidden fieldValue written (example)Question it answers
ChannelPaid searchWhich broad channel produced the lead?
Channel Drilldown 1GoogleWhich source within that channel?
Channel Drilldown 2Brand campaignWhich campaign?
Channel Drilldown 3Free account adWhich ad group or ad?
Landing PageFirst page the visitor sawWhich page started the journey?
Landing Page GroupFirst page's section (e.g. features)Which site section drives leads?

Example values reflect the guide's illustrative campaign and depend entirely on the UTM parameters you set. Field names must match exactly for values to populate.

Recommended UTM parameter convention
UTM parameterRecommended valueMaps to hidden field
UTM MediumPaid searchChannel
UTM SourceGoogleChannel Drilldown 1
UTM CampaignName of your Google Ads campaignChannel Drilldown 2
UTM TermName of the ad group the ad belongs toChannel Drilldown 3
UTM ContentThe specific ad(ad-level detail)

These are recommended conventions, not enforced rules; any consistent scheme works, but changing it later fragments historical reporting.

Frequently asked questions

Why do my Forminator submissions show no campaign data?

The usual causes, in order of likelihood: the ad URL had no UTM parameters, the hidden field names on the form do not match exactly, or the capture method only works when the form sits on the same page the visitor landed on. Test with a real ad click and inspect the submission record.

Do I need all six hidden fields?

The six fields cover channel, three drilldown levels, landing page and landing page group. If you only ever want campaign-level reporting you can start narrower, but adding fields later means earlier submissions lack that dimension.

What is the difference between Channel Drilldown 3 and UTM Content?

In the recommended convention, UTM Term carries the ad group name into Channel Drilldown 3, while UTM Content identifies the specific ad. Ad-level detail is therefore not one of the six hidden fields by default.

Can I see lead source without opening the WordPress dashboard?

Yes — include the hidden fields in the new-lead notification email, or send them to a CRM such as Pipedrive, Salesforce or HubSpot so the source travels with the record.

Does this only track Google Ads traffic?

No. The same setup records organic search, organic social and paid social sources, which is what makes a leads-by-channel report meaningful.