How to Capture Google Ads Data in WordPress Forms
Google Analytics can tell you how many people visited your site, but it rarely tells you which ad click turned into a lead or a customer. The missing link is usually the form. If each WordPress form submission carries the campaign, ad group, keyword and landing page that brought the visitor in, you can connect ad spend to real sales conversations. This guide explains the four-step setup, the hidden-field map, the persistence problem and the reports that make the data useful.
The four-step setup at a glance
The workflow has four moving parts. First, tag the Google Ads destination URLs with UTM parameters. Second, add a set of hidden fields to every WordPress form that should carry attribution. Third, let an attribution script write the visitor's source data into those hidden fields. Fourth, confirm that the form tool captures the hidden values alongside the lead's name and email when the form is submitted.
A useful way to remember the order is: tag the ad, prepare the form, fill the fields, capture the submission. If any one of those steps is missing, the CRM record will look like a direct or unknown visit even when the click came from a paid campaign.
Step 1: Tag your Google Ads URLs with UTM parameters
UTM parameters are short text values appended to the end of a destination URL. They tell analytics and attribution tools where a visitor came from. For Google Ads, a common pattern is:
- utm_medium = paid search
- utm_source = google
- utm_campaign = the Google Ads campaign name
- utm_term = the ad group name
- utm_content = the specific ad or keyword
The exact values are flexible, but consistency matters more than clever naming. If one campaign uses 'brand-campaign' and another uses 'Brand Campaign', your reports will split the same campaign into two rows. Pick a naming convention before you tag the first ad and apply it across the account.
A tagged URL looks like a normal destination with the parameters added after a question mark, for example a page URL followed by utm_medium, utm_source and utm_campaign values. The important point is that the parameters travel with the click, so the landing page can read them.
Step 2: Add hidden fields to your WordPress forms
Hidden fields are form inputs that visitors do not see but that still submit values with the form. Add the following fields to each form that should carry attribution:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
Most WordPress form builders, including Gravity Forms, Contact Form 7 and WPForms, let you drag a Hidden field into the form. The field names must match exactly what the attribution script expects, because the script writes values by field name. A typo in a field label is one of the most common reasons attribution data arrives empty.
Use the same field set on every form you want to measure. If one form has Channel but another does not, your CRM will have gaps that are hard to explain later.
Step 3: Let the attribution script fill the fields
Once the hidden fields exist, the attribution code placed on the site reads the visitor's source information and writes it into those fields. When a visitor submits a form, the values are already sitting in the hidden inputs, so the form tool captures them without asking the visitor to do anything.
The script should run on every page where a form appears, not only on the landing page. That is what allows a visitor who lands on one page and converts on another to keep their original source data.
Step 4: Confirm the form submission captures the data
When the form is submitted, the form tool should store the hidden values next to the lead's name, email and message. From there you can:
- View entries in the WordPress admin area, where plugins such as Gravity Forms and WPForms show submitted values.
- Include attribution fields in new-lead notification emails so the source is visible in your inbox.
- Send the values to a CRM such as Salesforce, Zoho CRM or Pipedrive so sales can see where each lead came from.
- Use the stored data in reports that connect campaigns to leads, customers and revenue.
Before trusting the setup, submit a test form from a tagged URL and check that each hidden field contains the expected value. If the fields are empty, work backward through the four steps rather than assuming the CRM is at fault.
Hidden-field map: what each field represents
The six hidden fields are not arbitrary. They map to specific pieces of the visitor's journey:
- Channel records the broad source type, such as paid search, organic search or paid social.
- Channel Drilldown 1, 2 and 3 hold progressively finer detail, such as the campaign, ad group and ad or keyword.
- Landing Page records the first page the visitor saw.
- Landing Page Group records the section of the site that page belongs to, such as a blog directory.
Keeping this map in mind helps you design CRM fields and reports that match the data. For example, if your sales team wants to filter by campaign, Channel Drilldown 1 is the field to expose in the CRM layout.
Why page-to-page persistence matters
Some capture methods only work when the form is submitted on the same page the visitor landed on. That breaks a very common journey: a visitor clicks an ad, lands on the pricing page, then clicks 'Request a demo' and submits the form on a separate demo page. Without persistence, the submission looks unattributed.
A cookie-based approach stores the source information in the visitor's browser, so the data survives navigation and is available wherever the form is submitted. This is the difference between capturing only direct landing-page conversions and capturing the full path a visitor takes before converting.
Three reports worth building once the data is flowing
Captured attribution data becomes useful when it reaches a CRM or reporting tool. Three report patterns are a practical starting point:
- Leads by channel. Break down monthly lead volume by channel to see how Google Ads compares with organic search, organic social and paid social. This shows whether paid search is actually where the biggest growth opportunity sits.
- Opportunities by Google Ads campaign. Show how many sales opportunities each campaign generated per month. This separates campaigns that produce real sales conversations from campaigns that only produce visits.
- Customers by keyword. If the keyword is included in the UTM parameters, you can see which search terms produced customers and adjust bids toward those terms.
These reports are only as good as the field discipline behind them. Consistent UTM naming and complete hidden fields on every form are what make the numbers trustworthy.
Troubleshooting: distinguish the three common failure points
When attribution data is missing, the cause usually falls into one of three buckets:
- Missing or inconsistent UTM tags. The ad click arrives without campaign information, so there is nothing to write into the hidden fields. Check the destination URL in Google Ads.
- Missing or misnamed hidden fields. The script has data but no field to write it into, or the field name does not match. Check the form builder field labels.
- No persistence across pages. The visitor landed on one page and submitted on another, and the capture method only reads the current URL. Check whether the source data survives navigation.
Working through these in order prevents the common mistake of rebuilding the CRM integration when the real problem is an untagged ad.
A quick pre-launch checklist
Before you rely on the data, confirm each item:
- Every Google Ads destination URL carries utm_medium, utm_source and utm_campaign at minimum.
- Campaign, ad group and ad or keyword names follow one consistent convention.
- All six hidden fields are present on every form you want to measure.
- Field names match the attribution script exactly.
- A test submission from a tagged URL shows values in every hidden field.
- The CRM or reporting tool receives the hidden values alongside the lead record.
- A test submission from a second page confirms persistence across navigation.
If all seven pass, the setup is ready for real traffic.
Frequently asked questions
Do I need to add UTM parameters if I only run Google Ads?
Yes. UTM parameters are what carry the campaign, ad group and keyword information into the landing page. Without them, the form has no source data to capture, even if the visitor clearly arrived from a paid ad.
Which WordPress form plugins support hidden fields?
Gravity Forms, Contact Form 7 and WPForms all allow you to add a Hidden field by dragging it into the form. The exact menu location varies by plugin, but the concept is the same across them.
What happens if a visitor lands on one page and submits a form on another?
With a cookie-based capture method, the original source information is stored in the browser and passed through to the form on the second page. Methods that only read the current URL will lose the attribution in this scenario.
Can I see the captured data without a CRM?
Yes. Form plugins such as Gravity Forms and WPForms show submitted entries, including hidden-field values, in the WordPress admin area. You can also include the fields in new-lead notification emails.
Why are my hidden fields empty after a test submission?
Check three things in order: whether the ad URL was tagged with UTM parameters, whether the hidden field names match exactly what the script expects, and whether the visitor submitted on a different page from the landing page without cookie persistence.