Skip to content

Capture Google Ads Data in Fluent Forms: A Practical Setup Guide

If you cannot tell which Google Ads campaign produced a Fluent Forms submission, you are left guessing about budget and creative. This guide shows how to connect the two: tag your ads with UTM parameters, create matching hidden fields in Fluent Forms, and let an attribution tool fill those fields at submission time so each lead carries its campaign, ad group and keyword into your CRM or reports.

The four-step setup

The workflow has four stages. Each one depends on the previous stage being correct, so it helps to treat them as a chain rather than four separate tasks.

  1. Add UTM parameters to your Google Ads URLs.
  2. Add hidden fields to your Fluent Forms.
  3. Let the attribution tool write Google Ads data into those hidden fields.
  4. Confirm the data is captured with each form submission.

Before you begin, decide what you want to measure. If you only need campaign-level reporting, campaign and source tags are enough. If you want to compare ad groups or individual ads, include term and content tags as well.

Step 1: Tag your Google Ads URLs

UTM parameters are short text snippets appended to the URL people reach after clicking an ad. Analytics and attribution platforms parse them to determine where a visit originated. A tagged destination might look like this:

https://example.com/landing-page?utm_medium=paidsearch&utm_source=google&utm_campaign=brand-campaign

For Google Ads, a common mapping is:

  • utm_medium: paid search
  • utm_source: Google
  • utm_campaign: the campaign name
  • utm_term: the ad group name
  • utm_content: the specific ad

You can choose different values, but consistency matters more than the exact wording. If one campaign uses "Google" and another uses "google.com", raw reporting will treat them as separate sources. Decide on a convention before you tag dozens of ads.

A practical tip: use Google Ads tracking templates so the parameters are added automatically rather than edited into every ad by hand.

Step 2: Add hidden fields to Fluent Forms

Fluent Forms includes a Hidden field type that you drag into a form just like any other field. Visitors never see it, so the form's appearance and completion flow stay unchanged. Add one hidden field for each value you need to store:

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

Name the fields exactly as above so the attribution tool can match them.

Step 3: Let the attribution tool fill the fields

Once tags and fields are ready, the attribution tool examines the visitor's initial landing page, reads the UTM parameters present there, and retains that result in the visitor's browser. When the form is submitted, it writes the stored values into the hidden fields.

A worked example helps here. Suppose a visitor clicks a Google Ad for a brand campaign, in an ad group called "Fluent Forms", and lands on your site. The hidden fields would receive:

  • Channel: Paid search
  • Channel Drilldown 1: Google
  • Channel Drilldown 2: Brand campaign
  • Channel Drilldown 3: Fluent Forms

This is the field map you can use to sanity-check your setup. If Channel shows "Paid search" but Drilldown 2 is empty, the campaign tag is probably missing from the ad URL.

Step 4: Confirm the data is captured

Submit a test form after clicking a tagged ad URL. In the Fluent Forms Entries section, open the new entry and check that the hidden fields contain the expected values. If they do, the chain is working.

From there you can:

  • View the values in the WordPress dashboard under Fluent Forms Entries.
  • Include the fields in lead notification emails so sales sees the source immediately.
  • Pass the values to a CRM such as Salesforce, Zoho CRM or Pipedrive.
  • Build reports that connect campaigns to leads, customers and revenue.

Why clean categorisation saves reporting time

Raw UTM data is only as consistent as the people who entered it. Over time, different team members or agencies may tag the same source as "Google.com", "google" or "adwords". If you store those strings unchanged, your reports display three distinct sources that you must reconcile manually.

A categorisation layer normalises these variations into a single channel such as "Paid search". That does not replace the raw UTM values; it gives you a stable top-level grouping so reports stay comparable month to month.

Landing page data adds a second dimension

In addition to the channel, record the first landing page path and a grouped version of that path. For instance, a visitor who lands on /blog/best-form-builder would produce:

  • Landing Page: /blog/best-form-builder
  • Landing Page Group: /blog

This lets you compare content types, such as blog versus product pages, and then drill into individual posts to see which ones generate the most leads.

Three reports worth building

Once data is flowing, the value comes from how you slice it. These three reports answer most early questions.

Leads by channel. Tally leads each month and group them by channel. This reveals how Google Ads stacks up against organic search, organic social and paid social. If most leads arrive from organic search while most budget goes to paid search, that is a signal worth investigating.

Opportunities by Google Ads campaign. Tally sales opportunities each month and break them down by campaign. Campaigns that generate visitors but no opportunities are candidates for pausing or rework.

Customers by keyword. If you pass the keyword through a UTM term parameter, you can tally customers per keyword. Keywords that produce customers are candidates for higher bids.

Pre-launch checklist

Run through this list before you rely on the data:

  • Every active Google Ads URL carries utm_source, utm_medium and utm_campaign.
  • The naming convention is documented and shared with anyone who edits ads.
  • All six hidden fields exist in each Fluent Form that should capture attribution.
  • Field labels match the expected names exactly.
  • A test submission from a tagged ad shows values in every expected field.
  • A test submission from a different page on the site still shows the original source.
  • The CRM mapping includes the hidden fields, not just name and email.
  • At least one report is built and reviewed monthly.

Frequently asked questions

Do I need all five UTM parameters?

No. Source, medium and campaign are the minimum for channel-level reporting. Term and content are needed only if you want ad group or ad-level breakdowns. Adding more parameters gives finer reporting but also more chances for inconsistent naming.

What happens if a visitor submits a form on a different page from the one they landed on?

With a cookie-based attribution tool, the original source is retained and written into the hidden fields at submission. With same-page-only methods, the source is lost. This is the main practical difference between the two approaches.

Why do my reports show several versions of Google as a source?

Raw UTM values reflect exactly what was typed into the ad URL. Variations in capitalisation or domain spelling create separate source values. A categorisation layer groups them under one channel, but you should still standardise your tagging convention to keep the underlying data clean.

Can I see the captured data without opening a CRM?

Yes. Fluent Forms stores each submission in its Entries section inside the WordPress dashboard, so you can inspect the hidden field values there. You can also include the fields in notification emails.